architect
Installation
SKILL.md
Architect
Design the smallest repo-grounded solution before planning or building. Return an inline architecture memo the user can keep, discard, or turn into a plan.
Rules
- Stay read-only. Do not edit files, write artifacts, stage, commit, or create plans.
- Treat outcome decomposition as architecture, not implementation planning. Define coherent solution units for an umbrella, but do not produce phases, file-edit checklists, command gates, executor skills tables, or task breakdowns.
- Ask the user only when ambiguity materially changes the architecture. Include a recommended answer and the real tradeoff.
- Route bugs, symptoms, and code-truth questions to
diagnose-issuefirst: read../diagnose-issue/SKILL.mdcompletely and follow it instead of diagnosing inline. Use theshape-requirementsgate when unclear product intent prevents a choice.