skills.rest
kimprobably
kimprobablyCOMMUNITY
Explore all skills by this author →
GitHub

spec-kitty.plan

Generate planning artifacts from a validated spec-kitty mission specification.

Updated May 13, 2026
Search Tags:#implementation planning#spec-driven development#project governance#contract generation#branch strategy#mission automation
One-click install
npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-plan-kimprobably
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kitty.plan
Source: https://github.com/kimprobably/maestro-os/tree/main/.agents/skills/spec-kitty.plan
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-plan-kimprobably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn an existing spec and mission into a concrete implementation plan, including the required planning artifacts, without creating worktrees or guessing the correct branch context.

Core Features & Use Cases

  • Mission-aware planning: Selects and validates the correct mission using a handle such as mission_id, mid8, or mission_slug, reducing risk of planning for the wrong feature.
  • Deterministic branch contract: Resolves current and target branch strategy using JSON from the setup workflow and prepares outputs committed to the intended target branch.
  • Phase 0/1 planning artifacts: Stops after generating planning outputs like research.md, data-model.md, contracts/, and quickstart.md, so you can explicitly run work-package generation later.

Quick Start

Run /spec-kitty.plan for your selected mission and follow the prompts until the planning artifacts are generated and the next step shows /spec-kitty.tasks.

Frequently Asked Questions about spec-kitty.plan

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

FAQPage Schema
How do I generate an implementation plan from a mission specification?▼

Implementation plan generation from a mission specification requires loading charter context, resolving branch strategy, and producing planning artifacts like research.md, data-model.md, contracts, and quickstart.md in the project root checkout.

What planning artifacts are needed before generating work packages?▼

Planning artifacts needed before work package generation include research.md for clarifications, data-model.md for structure, contracts/ for interfaces, and quickstart.md for setup, ensuring deterministic project governance prior to task creation.

How does branch strategy validation work for spec-driven development planning?▼

Branch strategy validation for spec-driven development resolves current and target branches using setup workflow JSON, ensuring planning artifacts are committed to the intended target branch without guessing the correct context.

Can I use a mission slug to select a specific feature for planning?▼

Mission selection supports using a mission slug, mission_id, or mid8 handle to validate and select the correct feature, reducing the risk of generating an implementation plan for the wrong mission.

When should I stop planning before creating task work packages?▼

You should stop planning after generating Phase 0/1 artifacts like research.md, data-model.md, contracts/, and quickstart.md, allowing you to explicitly run work-package generation as a separate downstream step.

Do I need optional research-driven clarification to resolve mission specifications?▼

Optional research-driven clarification resolves open questions in mission specifications by generating research.md, which feeds into the subsequent data model and contract generation phases of the implementation plan.

Related Skills

Explore More Software Engineering Skills→
stijn-dejonghstijn-dejongh
1

spec-kitty.plan

Automate repository implementation planning with Spec Kitty workflows.

Community
Advanced
ImaginerLabsImaginerLabs

bmad-retrospective

Facilitate post-epic retrospectives to extract lessons and generate actionable items.

Official
Advanced
otahontasotahontas
1

branch-review

Review local code diffs against the default branch and write a markdown report.

Community
Intermediate
kimprobablykimprobably

spec-kitty.specify

Creates mission specifications from user intent via guided discovery and branch checks.

Community
Advanced