sp-plan

Generates implementation planning artifacts from a planning-ready spec contract in spec-kit projects.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-plan-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-plan
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-plan
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-plan-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns an approved specification package into explicit, machine-readable implementation design artifacts so that task generation and coding never start from implicit or scattered planning decisions. ## Core Features & Use Cases - Plan Contract Generation: Produces canonical plan-contract.json plus a project-facing plan.md, with conditional research.md, data-model.md, contracts/, and quickstart.md only when their triggers are present. - Consequence Analysis Gate: Runs a senior consequence analysis producing affected-object maps, state-behavior matrices, dependency impact tables, and tracked CA-### obligations that must survive downstream handoffs. - Adaptive Lane Dispatch: Selects light, standard, or heavy execution modes and delegates isolated research, data-model, contract, or quickstart lanes to writable native subagents with structured handoffs. - Use Case: After /sp-specify marks a feature spec planning-ready, invoke this Skill to produce the validated plan package, then hand off to /sp-tasks for decomposition without rediscovering design decisions. ## Quick Start Invoke /sp-plan with optional planning guidance once your spec contract reports status planning-ready, and it will generate the plan contract and design artifacts for the active feature.

Frequently Asked Questions about sp-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 specification?▼

Invoke /sp-plan after the spec contract reaches planning-ready status. The skill validates spec-contract.json, runs the deterministic workflow transition into the plan stage, then writes plan-contract.json and plan.md plus any triggered conditional artifacts.

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

It always produces plan-contract.json and plan.md. research.md, data-model.md, contracts/, and quickstart.md are generated only when their documented triggers are present, such as unresolved implementation-shaping unknowns or new external interfaces.

Can sp-plan write code or modify tests during planning?▼

No. The skill is design-only and explicitly forbids editing production source, tests, migrations, or runtime configuration. It also never creates tasks.md or task-index.json, which belong to the separate /sp-tasks workflow.

What happens when the spec contract is not planning-ready?▼

The skill stops instead of guessing. It follows the blocked exit contract, persists a structured blocker through the specify workflow block command with recovery and resume details, and never claims completion while blockers remain.

Does sp-plan require the project-cognition runtime to work?▼

No. Project cognition compass intake is advisory navigation only. When the runtime is unavailable, stale, or unsupported, the skill continues with live repository evidence and records the degraded routing state.

When does the senior consequence analysis gate trigger?▼

It triggers whenever the planned change can affect lifecycle operations, running state, concurrency, destructive behavior, shared state, downstream consumers, compatibility, or security. Docs-only wording changes and trivial isolated fixes may stand down with a recorded reason.