speckit-plan

Generate implementation plans and design artifacts for Spec Kit projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nShieldSolo/ArcticFactory.Preset --skill speckit-plan-nshieldsolo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/nShieldSolo/ArcticFactory.Preset/tree/main/.agent/skills/speckit-plan
Command: npx skills add https://github.com/nShieldSolo/ArcticFactory.Preset --skill speckit-plan-nshieldsolo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of implementation plans and design artifacts for Spec Kit projects, removing manual steps to assemble research, data models, contracts, and quickstarts required for feature implementation.

Core Features & Use Cases

  • Structured multi-phase workflow: Runs setup scripts, loads feature spec and constitution, evaluates gates, and follows the IMPL_PLAN template through research and design phases.
  • Artifact generation: Produces research.md, data-model.md, contracts/, quickstart.md, and updates agent-specific context files.
  • Extension hook handling: Detects and reports optional or automatic pre-plan and post-plan hooks declared in .specify/extensions.yml so integrators can execute or review them.
  • Use case: Prepare a branch-specific implementation plan for a new feature, resolve ambiguities, generate design contracts, and produce a quickstart for implementers.

Quick Start

Generate an implementation plan from the current feature spec and produce research.md, data-model.md, contracts, data-model.md, and quickstart.md.

Frequently Asked Questions about speckit-plan

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

FAQPage Schema
How do I generate implementation plans and design docs for software features?

Generate implementation plans and design artifacts by running setup scripts, loading feature specs, and following the IMPL_PLAN template through research and design phases. This structured workflow produces research.md, data-model.md, contracts, and quickstart.md files required for feature implementation.

What is a Spec Kit project and how does it structure feature planning?

A Spec Kit project uses a .specify directory to manage feature planning through constitution files, spec templates, and bash scripts. It structures planning into phases that evaluate gates, resolve ambiguities, and generate design contracts for implementers.

How do I automate research and data model creation for a new feature branch?

Automate research and data model creation by executing setup-plan.sh to prepare a branch-specific implementation plan. The workflow evaluates feature specs and generates research.md and data-model.md artifacts during the Phase 0 and Phase 1 planning stages.

Do I need a .specify directory to produce design contracts and quickstart guides?

Yes, a .specify directory is required. The planning process depends on .specify/scripts/bash/setup-plan.sh and update-agent-context.sh to produce contracts, quickstart.md, and update agent-specific context files for implementers.

Can I run custom pre-plan and post-plan hooks during implementation planning?

Yes, you can declare optional or automatic pre-plan and post-plan hooks in .specify/extensions.yml. The planning workflow detects and reports these extension hooks so integrators can execute or review them during the process.

What are the limitations of automated design artifact generation?

Automated design artifact generation is limited to Spec Kit projects containing the required .specify directory and specific bash scripts. It cannot produce plans for projects lacking this structure or without the necessary setup and context update scripts.