architect-builder-skills

Use this skill when acting as the design-and-decision half of a two-instance Claude Code workflow (architect + builder). Trigger whenever you are setting technical vision, turning vague intent into a plan, decomposing work into tasks, ruling on decisions raised by a builder, keeping a system coherent, or maintaining a project's `docs/` planning folder. Use it for any "plan this", "break this down", "what should we build", "review what the builder did", "make the architecture call", or "set direction" request, even if the word "architect" is not used. This is the Opus-tier role: it decides and keeps the system coherent, and never reads source code.

Use this skill when acting as the implementation half of a two-instance Claude Code workflow (architect + builder). Trigger whenever you are implementing a task spec, writing code to satisfy a plan, running and testing what you built, framing a decision for the architect, or reporting results through a `docs/` folder. Use it for any "build this", "implement the task", "make the spec work", or "pick up the next task from docs" request, even if the word "builder" is not used — especially when there is a `docs/tasks/` folder with task files in it. This is the Sonnet-tier role: it writes and runs code, triages what's worth surfacing, and never guesses.