solution

name	solution
description	Use when the user wants to write or review system architecture at .agency/architecture/solution.md (stub or full arc42-lite). Triggers on "write the architecture", "solution design", "arc42", "review the architecture", "does solution.md match what we built". Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in .agency/work/{epic}/tasks.md.
license	MIT
allowed-tools	["Read","Write","Glob","Grep"]
argument-hint	<mode: write|review> [--stage stub|full] [--context <notes>]
metadata	{"author":"Carinya Parc","version":"1.0","owner":"architecture","work_shape":"generate-draft","output_class":"draft-for-review","review_cadence":"as-needed"}

Solution

Conventions

Read delivery-conventions.md for artefact boundaries.

Artefact

Default path: .agency/architecture/solution.md — arc42-lite architecture (stub or full).

Path resolution

If the user names a different file path in their request, read and write that path instead of the default.

Stage (write mode)

Stage	When	Sections
stub	Phase 0	§1–§2 only; §3–11 scaffolded
full	Phase 2+	All eleven sections

Gotchas

• Per-epic files/APIs → cite from .agency/work/{epic}/design.md, don't duplicate full specs.
• Story-level Gherkin → tasks.md, not solution.
• Closed ADRs → ADR-NNNN-*.md; proposals stay in register only.

Supporting files

• assets/solution.template.md

Related skills

• product, tasks, design, adr

Router

1. Mode: write or review.
2. Resolve target path (default or user override).
3. One prompt under prompts/.

write — --stage stub|full.