About w-architecture
w-architecture is a development skill for planning implementation structure in response to a question. It directs durable system-boundary decisions to existing ADRs and architecture docs, and returns plans with assumptions, trade-offs, and references.
Key features
- 01Plan implementation structure
- 02Consult existing ADRs and architecture docs
- 03Separate goals from optional work
- 04Identify constraints, trade-offs, and risks
- 05State assumptions and references
Use cases
- 01Plan a change within an existing architecture
- 02Assess whether a change needs durable documentation
- 03Compare implementation alternatives and risks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/w-architecturein Claude Code to confirm it loaded.
Details
From the project READMEProduce an implementation-structure plan for the user's question. Durable system decomposition belongs in existing ADRs and architecture MDX. Do not mint a second ADR tree. Do not create a branch.
- If this turn has no reconciled exploration for the area, follow council steps 1–3, then continue.
- Read the matching architecture MDX and ADRs. If the change is a durable boundary, stop and document it in the existing ADR/docs system.
- State implementation goals vs nice-to-haves. Stay inside the existing architecture unless the user already authorized a durable architecture decision.
- List constraints, trade-offs, and alternatives that affect this change. Flag high-risk items for a human. State 3–5 assumptions.
- Add Mermaid only when structure or flow is otherwise unclear.
- Save only if the user gave a path; otherwise return in chat. Include Assumptions and References (plain paths). Commands and generated-source owners come from inspected docs.
Comments
Markdown supported