speckit-plan

Generate data-model.md, contracts/, and quickstart.md from plan templates.

Updated Jun 8, 2025
One-click install
npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-plan-cicero78m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-plan
Source: https://github.com/cicero78M/Cicero_Web/tree/main/.agents/skills/speckit-plan
Command: npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-plan-cicero78m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-plan automates the creation of implementation planning artifacts by applying a standardized plan template, accelerating project setup and ensuring consistency across artifacts.

Core Features & Use Cases

  • Generate data-models, contracts, and quickstart documentation from a plan template.
  • Trace requirements from the spec-kit structure to concrete design outputs and ensure alignment.
  • Seamlessly integrate with .specify/ directories to drive end-to-end planning workflows in software projects.

Quick Start

Run speckit-plan at the project root to generate the implementation plan artifacts using the plan template.

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 planning artifacts for software projects?

To generate implementation planning artifacts, you can execute a standardized plan template against your repository root to automatically produce data models, contracts, and quickstart documentation.

What is the best way to automate data-model and contract generation from project specs?

Automating data-model and contract generation is best handled by executing planning workflows that trace requirements from a spec-kit structure directly into concrete design outputs like data-model.md and contracts/.

Does speckit-plan require a specific directory structure to run?

Yes, speckit-plan requires a .specify/ directory structure at the repository root to support hooks, memory constitution, and IMPL_PLAN templates for end-to-end planning workflows.

How do I ensure unknowns are resolved before generating project planning artifacts?

To ensure unknowns are resolved before generating artifacts, the planning workflow applies validation gates and updates agent context, verifying that all uncertainties are addressed during template execution.

Can I use plan templates to drive end-to-end planning workflows in existing repositories?

Yes, you can use plan templates to drive planning workflows in existing repositories by applying them at the project root, which generates quickstart.md and updates agent context seamlessly.