What problem does it solve? Writing an architectural plan from a feature specification is repetitive and error-prone: teams forget ADRs, skip constitution audits, or invent tech stacks not documented anywhere. This Skill turns an existing spec.md into a structured plan.md with four canonical sections, ensuring every plan follows the same SDD standard. ## Core Features & Use Cases - Canonical plan generation: Produces plan.md with four mandatory sections — Metadata, Contracts and Boundaries, ADRs (minimum 1), and Constitution Audit. - Grounded in project memory: Reads .github/memory/tech.md and constitution.md so the stack and quality gates come from real project documents, never invented. - Architecture decision support: Ships an assets/architecture-patterns.md reference with a decision tree, Go-specific pattern tables, and anti-patterns to inform ADRs. - Use Case: After running sdd-brainstorm to create specs/features/003-forge-skill/spec.md, invoke this Skill to produce the architectural plan with at least one ADR and a constitution compliance checklist before implementation begins. ## Quick Start Ask the assistant to generate the architectural plan for the feature at specs/features/<id>-<slug> using its existing spec.md.