domains / families / software-engineering / architect

architect

separate

Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.

When to use

• choosing between approaches
• designing a feature or page
• picking a tech stack
• resolving unmade load bearing technical decisions
• standardising a pattern across the codebase
• ratifying an assumed decision

When not to use

• writing code
• updating AGENTS.md or CLAUDE.md

Skill page

Source