superpowers-architecture

Use when starting a new project from scratch or establishing project operating contracts, root CONTEXT.md, stack decisions, architecture summary, domain language, and a high-level roadmap before feature brainstorming

Use when executing implementation plans with mostly independent tasks in a fresh or same session after written plan approval

Use when an approved local design spec exists and an exact implementation plan is needed before code changes

Use when starting a conversation to route new-project setup requests to project-setup and make/build/create/implement app, site, tool, component, UI, API, workflow, or behavior requests to brainstorming before frontend, design, framework, or implementation skills

Use before make/build/create/implement requests for apps, sites, tools, components, UI, APIs, workflows, feature work, architecture changes, behavior changes, or unclear requirements; writes a local design spec before planning or coding

Use when executing written implementation plans linearly after written plan approval

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Use when implementation tasks are complete and final verification, commit summary, changed-file summary, and residual risk summary are needed

Use when scanning a codebase for shallow modules, unclear interfaces, weak seams, poor adapters, poor locality, low leverage, or weak test surfaces

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback