How do I install the Speckit Plan skill?

Run npx skillmds add majiayu000/speckit-plan-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Speckit Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Speckit Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Speckit Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Speckit Plan?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Speckit Plan by majiayu000 — Agent Skill

Name: Speckit Plan
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Spec-Kit Plan

Generate comprehensive technical implementation plan from feature specification. Second step in spec-kit workflow.

When to Use

After creating spec.md with speckit-specify
Need technical architecture and design
Ready to plan implementation details

Execution Workflow

Setup: Run .specify/scripts/bash/setup-plan.sh --json to get FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH paths
Load context: Read FEATURE_SPEC and .specify/memory/constitution.md, load IMPL_PLAN template
Execute plan workflow:
- Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
- Fill Constitution Check section from constitution
- Evaluate gates (ERROR if violations unjustified)
- Phase 0: Research - Resolve all NEEDS CLARIFICATION before design
  - Extract unknowns from Technical Context
  - Research best practices for each unknown (web search, documentation)
  - Generate research.md with decision rationale and alternatives considered
  - MUST complete Phase 0 before Phase 1
- Phase 1: Design - Generate technical artifacts
  - data-model.md: Extract entities from spec, define fields/relationships/validation
  - contracts/: Generate API contracts (OpenAPI/GraphQL) from functional requirements
  - quickstart.md: Create test scenarios and setup instructions
  - Update agent context: Run .specify/scripts/bash/update-agent-context.sh claude
    - Adds new technology from plan to agent-specific context
    - Preserves manual additions between markers
- Re-evaluate Constitution Check post-design (verify no violations introduced)
Report: Command ends after planning. Report branch, IMPL_PLAN path, and generated artifacts

Key Points

Research unknowns thoroughly before design
Document decision rationale (why chosen, alternatives considered)
Design for testability following project conventions
Avoid over-engineering - only what's needed
Follow semantic versioning and architecture patterns
Constitution check is non-negotiable - must align with principles
Update agent-specific context files with new technology

Next Steps

After creating plan.md:

Generate tasks with speckit-tasks
Analyze for consistency with speckit-analyze
Create checklist for quality validation

---name: speckit-plan-2description: Execute the implementation planning workflow using the plan template to generate design artifacts.--- # Spec-Kit Plan Generate comprehensive technical implementation plan from feature specification. Second step in spec-kit workflow. ## When to Use - After creating spec.md with `speckit-specify` - Need technical architecture and design - Ready to plan implementation details ## Execution Workflow 1. **Setup**: Run `.specify/scripts/bash/setup-plan.sh --json` to get FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH paths 2. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`, load IMPL_PLAN template 3. **Execute plan workflow**: - Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION") - Fill Constitution Check section from constitution - Evaluate gates (ERROR if violations unjustified) - **Phase 0: Research** - Resolve all NEEDS CLARIFICATION before design - Extract unknowns from Technical Context - Research best practices for each unknown (web search, documentation) - Generate research.md with decision rationale and alternatives considered - **MUST complete Phase 0 before Phase 1** - **Phase 1: Design** - Generate technical artifacts - data-model.md: Extract entities from spec, define fields/relationships/validation - contracts/: Generate API contracts (OpenAPI/GraphQL) from functional requirements - quickstart.md: Create test scenarios and setup instructions - **Update agent context**: Run `.specify/scripts/bash/update-agent-context.sh claude` - Adds new technology from plan to agent-specific context - Preserves manual additions between markers - Re-evaluate Constitution Check post-design (verify no violations introduced) 4. **Report**: Command ends after planning. Report branch, IMPL_PLAN path, and generated artifacts ## Key Points - Research unknowns thoroughly before design - Document decision rationale (why chosen, alternatives considered) - Design for testability following project conventions - Avoid over-engineering - only what's needed - Follow semantic versioning and architecture patterns - Constitution check is non-negotiable - must align with principles - Update agent-specific context files with new technology ## Next Steps After creating plan.md: - **Generate tasks** with `speckit-tasks` - **Analyze** for consistency with `speckit-analyze` - **Create checklist** for quality validation ## See Also - `speckit-specify` - Create feature specifications - `speckit-tasks` - Break plan into actionable tasks - `speckit-analyze` - Validate cross-artifact consistency - `speckit-checklist` - Generate custom validation checklists

Frequently asked questions