spec-plan

Transform feature specifications into implementation plans with research, data models, and contracts.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill spec-plan-chaimt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-plan
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/spec-plan
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill spec-plan-chaimt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-Plan helps teams convert feature specifications into an actionable, implementation-focused plan by outlining research, data models, contracts, and setup steps.

Core Features & Use Cases

  • Transforms a product spec into a full implementation plan including research, data models, and contracts.
  • Generates artifact outputs such as research.md, data-model.md, contracts/, quickstart.md, and updated agent context.
  • Supports extension hooks and architecture validation workflows to maintain governance.

Quick Start

Run the spec-plan skill to generate a complete implementation plan from your feature specification.

Frequently Asked Questions about spec-plan

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

FAQPage Schema
How do I generate data models and contracts from a feature specification?

To generate data models and contracts from a feature specification, you can use a planning tool that transforms specs into executable implementation plans, scoping tasks and outputting structured artifacts like data-model.md and contracts/.

What is the best way to create an implementation plan from a product spec?

Creating an implementation plan from a product spec involves scoping tasks and research needs while enforcing governance and constitutional checks, resulting in a structured plan with quickstart guides and updated agent context.

Do I need a specific directory structure to generate implementation artifacts?

Yes, generating implementation artifacts requires a spec-kit project structure with a .specify directory to enforce governance and properly output files like research.md and contracts.

Can I enforce architecture validation workflows when planning from a specification?

Yes, architecture validation workflows can be enforced during the specification planning process to maintain governance and constitutional checks while generating data models and contracts.

What outputs should I expect when transforming a feature spec into an implementation plan?

Transforming a feature spec into an implementation plan produces structured outputs including research.md, data-model.md, contracts/, quickstart.md, and an updated agent-context for project setup.