speckit-companion-plan

Generates implementation plans with research and design artifacts for spec-kit projects.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-plan-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-plan
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-companion-plan
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-plan-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification into a concrete, right-sized implementation plan is slow and inconsistent when done by hand. This Skill automates the plan phase of a spec-kit pipeline, producing plan.md, research notes, data models, and interface contracts that follow the project's constitution and conventions. ## Core Features & Use Cases - Phased Plan Generation: Loads the feature spec and constitution, investigates the codebase, then writes plan.md with Summary, Project Structure, and a Constitution Check gate. - Size-Aware Budgeting: Reads the recorded change size from .spec-context.json and produces a lean plan for simple changes or the full artifact set (research.md, data-model.md, contracts/) for normal or oversized ones. - Pipeline Integration: Fires spec-kit extension hooks and project node hooks, records timing and design decisions via write-context.py, and self-advances to the next workflow step while pausing at review gates. - Use Case: After running the specify step on a new feature, invoke this Skill to produce a constitution-checked implementation plan with Phase 0 research decisions and Phase 1 design artifacts, ready for the tasks step. ## Quick Start Run the speckit companion plan command for the current feature to generate its implementation plan and design artifacts.

Frequently Asked Questions about speckit-companion-plan

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

FAQPage Schema
How do I generate an implementation plan from a spec-kit feature spec?▼

Run the companion plan command after the specify step. It reads .specify/feature.json and the feature's spec.md, investigates the codebase, then writes plan.md plus research.md, data-model.md, and contracts/ when the change size warrants them.

What artifacts does the spec-kit plan phase produce?▼

The plan phase produces plan.md with a Summary, Project Structure, and Constitution Check, plus Phase 0 research.md and Phase 1 data-model.md and contracts/. For changes sized simple, it keeps only the Summary and folds decisions into plan.md.

Does the companion plan command require a spec-kit project structure?▼

Yes, it requires a spec-kit project with a .specify/ directory containing feature.json and the companion extension scripts. Missing optional files like constitution.md or living specs are skipped silently and never block the plan.

How does the plan command handle small or simple changes?▼

It reads the size field from .spec-context.json and right-sizes the output. For simple changes it skips the Project Structure section, data-model.md, and separate research.md, folding key decisions directly into plan.md.

Why does the plan step pause instead of continuing to tasks?▼

The workflow defines review gates such as review-plan where the run must stop and wait for approval. The command only advances to the next pipeline step once the gate is approved, and on one-shot environments it stops cleanly for manual resumption.