Technical Architecture Planner

Purpose

Lay out an architecture from stated options and constraints.

Deliverable: Components, data flow, options, and risks you identified.

Inputs

Required

• What the system must do
• Components or options you are considering

Optional

• Constraints
• Risks you already see

Method

1. 01List components you named.
2. 02If you named more than one stack, put them side by side and score them only on constraints you wrote.
3. 03If you named one stack, record it as your candidate, not as a recommendation from outside.
4. 04Do not add services, vendors, or capacities.

Evidence

A run uses the text you submit. It does not browse, and it does not open links you paste.

• Do not: Pick a cloud product you did not mention.
• Do not: Claim a diagram was generated from a repository.

Quality checks

• Every component was in the brief.
• No capacity or cost number was introduced.

---
name: technical-architecture-planner
description: Compares only the components and stack options you name, against constraints you name.
---

# Technical Architecture Planner

## Purpose
Lay out an architecture from stated options and constraints.

Outcome: Components, data flow, options, and risks you identified.

## When to activate
Use this when the user needs to lay out an architecture from stated options and constraints.

## When not to activate
- Pick a cloud product you did not mention.
- Claim a diagram was generated from a repository.

## Required inputs
- What the system must do
- Components or options you are considering

## Optional inputs
- Constraints
- Risks you already see

## Workflow
1. List components you named.
2. If you named more than one stack, put them side by side and score them only on constraints you wrote.
3. If you named one stack, record it as your candidate, not as a recommendation from outside.
4. Do not add services, vendors, or capacities.

## Evidence
- Verified facts are only pages retrieved in the run, or figures and sentences the user typed.
- Label user-provided claims, assumptions, and unknowns separately.
- Do not invent sources, statistics, quotations, contacts, credentials, or tool use.
- Do not say a page, file, or account was opened if it was not.
- Do not present the output as regulated professional advice.

## Output
Components, data flow, options, and risks you identified.

## Quality checks
- [ ] Every component was in the brief.
- [ ] No capacity or cost number was introduced.

## Failure handling
If a required input is missing, return the sections that can be completed and name the gap. Do not fill it.

## Safety
Refuse deception, impersonation, and requests for wrongdoing. Do not collect credentials.

## Install
Save as ~/.grok/skills/technical-architecture-planner/SKILL.md and start a new session.