spec-plan

Generates technical implementation plans with Mermaid sequence, state, and ER diagrams from feature specs.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-plan-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-plan
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-plan
Command: npx skills add https://github.com/julien-m/livespec --skill spec-plan-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written feature specification into an actionable technical plan is slow and inconsistent: diagrams get skipped, requirements lose traceability, and testing strategy is an afterthought. This Skill reads a feature's spec.md and produces a complete plan.md with diagrams, file-by-file steps, and a resolved testing strategy. ## Core Features & Use Cases - Diagram generation: Creates Mermaid sequence, state, and ER diagrams based on API interactions, stateful entities, and new database tables detected in the spec. - File-by-file implementation plan: Maps every functional requirement to concrete files across infrastructure, database, business logic, API, UI, and test layers, with FR sub-task numbering for traceability. - Constitution and scope checks: Validates the plan against project architectural principles and classifies feature size (S/M/L) to budget diagram output. - Use Case: After writing a spec for a notifications feature, run the plan step to get 7 implementation steps across 9 files, an ER diagram for two new tables, an OpenAPI contract, and a resolved test command table. ## Quick Start Ask the AI to run /spec-plan for your feature name to generate plan.md with diagrams and an implementation strategy from the existing spec.

Frequently Asked Questions about spec-plan

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

FAQPage Schema
How do I generate a technical plan from a feature spec?

Run /spec-plan with a feature name after creating its spec.md. The command reads the spec, constitution, and stack files, then writes plan.md with diagrams, implementation steps, and a testing strategy.

What diagrams should a technical implementation plan include?

Include a sequence diagram when the feature has API interactions, a state diagram when entities have lifecycles, and an ER diagram when new database tables are introduced. Small features may need only one sequence diagram.

Can I skip the LLM plan review step?

Yes, pass the --no-review flag to skip the default LLM review of the generated plan. You can also use --all-reviewers to run every configured reviewer model instead of just the first.

Why does plan generation fail structural validation?

Validation fails when plan.md misses required sections like Technical Context, Constitution Check, or Implementation Plan. The command retries generation up to two times with the validator errors injected, then aborts with the remaining errors.

What happens if spec.md does not exist for the feature?

The command prompts you to run the specify step first, since the plan is generated from the spec content. Without a spec, there are no functional requirements or acceptance criteria to map into implementation steps.