sdd-generate-plan

Generates plan.md architectural plans from spec.md in an SDD feature pipeline.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-generate-plan-phm-aguiar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-generate-plan
Source: https://github.com/phm-aguiar/test_documentacao/tree/main/.claude/skills/sdd-generate-plan
Command: npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-generate-plan-phm-aguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

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.

Frequently Asked Questions about sdd-generate-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an architectural plan from a feature spec?▼

Provide the feature directory path such as specs/features/003-forge-skill containing a filled spec.md. The Skill reads the spec plus tech.md and constitution.md, then writes plan.md with metadata, contracts, ADRs, and a constitution audit after your approval.

What sections does the generated plan.md contain?▼

The plan.md contains four canonical sections: Plan Metadata with stack and scope, Contracts and Boundaries for APIs or schemas, at least one ADR with decision, justification, and rejected alternative, and a Constitution Audit checklist against constitution.md rules.

What files are required before generating a plan?▼

A filled spec.md in the feature directory is required, plus .github/memory/tech.md and constitution.md. The memory files may be empty; in that case the plan uses {{...}} placeholders and notes that no constitution rules exist to audit.

Does the plan generator invent a tech stack if tech.md is empty?▼

No. The Skill never invents a stack; it uses only what tech.md documents. If tech.md is empty, stack fields are written as {{...}} placeholders for the team to fill in later.

What happens if plan.md already exists for the feature?▼

The Skill is idempotent: when plan.md already exists, it asks whether to overwrite or merge before writing. It also always asks for user approval before saving any new plan.

When should I not use this SDD plan generator?▼

Do not use it before the brainstorm stage, since it requires an existing spec.md. It is also unsuitable for projects not following the SDD pipeline with specs/features directories and .github/memory files.