skills.rest
jrmatherly
jrmatherlyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shipit-kit:plan

Generate TDD implementation plans and tasks.yaml from feature specs and research.yaml.

1|Updated Apr 3, 2026
Search Tags:#tdd#research#tasks#feature-spec#implementation-plan#shipit
One-click install
npx skills add https://github.com/jrmatherly/shipit --skill shipit-kit-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipit-kit:plan
Source: https://github.com/jrmatherly/shipit/tree/main/.claude/skills/shipit-kit-plan
Command: npx skills add https://github.com/jrmatherly/shipit --skill shipit-kit-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts feature specifications and research into a concrete, test-driven implementation plan so teams can move from discovery to implementation without unresolved questions or missing tests. It enforces a gate check on open research questions and ensures planning follows a mandatory RED-GREEN-REFACTOR workflow so work is incremental, test-first, and traceable.

Core Features & Use Cases

  • Gate Enforcement: Reads research.yaml and stops planning if any openQuestions have resolved: false to prevent premature implementation.
  • Architecture & TDD Plans: Produces a high-level architecture overview and breaks work into TDD-aligned phases (Foundational, RED, GREEN, REFACTOR) for Domain, Application, and Infrastructure layers.
  • YAML Sources of Truth: Generates plan.yaml and tasks.yaml with clear rules about content separation, writes data-model.md when needed, updates status fields and feature.yaml, and provides an actionable tasks[] array for tracking.
  • Developer Workflow Integration: Lists files to create/modify, identifies parallelizable tasks, prescribes testing strategy, documents risks and rollback steps, and prescribes commit and CI-watch steps for each phase.
  • Use Case: Ideal for engineering teams using ShipIT to convert a completed spec and research into an implementation backlog that enforces tests-first development.

Quick Start

Use shipit-kit:plan to generate a TDD implementation plan and tasks.yaml from the spec and research in specs/NNN-feature-name so the feature is ready for implementation.

Frequently Asked Questions about shipit-kit:plan

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

FAQPage Schema
How do I generate a TDD implementation plan from feature specs and research?▼

To generate a TDD implementation plan, use a tool that reads spec.yaml and research.yaml to produce plan.yaml and tasks.yaml. It breaks work into RED-GREEN-REFACTOR phases, ensuring test-first development across Domain, Application, and Infrastructure layers.

What happens if my research has unresolved open questions before planning?▼

If research.yaml contains openQuestions with resolved: false, the planning process halts via a gate check. This stops premature implementation by ensuring all unresolved research questions are addressed before generating a plan.

How does the RED-GREEN-REFACTOR cycle apply to implementation tasks?▼

The RED-GREEN-REFACTOR cycle structures tasks sequentially: write failing tests first (RED), implement code to pass tests (GREEN), then optimize code without changing behavior (REFACTOR). This enforces incremental, test-first development.

Can I track implementation progress using YAML files?▼

Yes, the process generates tasks.yaml with an actionable tasks array for tracking and plan.yaml for the overall architecture. It also updates status fields in feature.yaml to monitor progress through the implementation phases.

Does the generated plan include developer workflow steps like commits and CI?▼

Yes, the generated plan prescribes commit and CI-watch steps for each phase. It identifies files to create or modify, flags parallelizable tasks, documents risks, and outlines rollback procedures for the development team.

When do I need to create a data model for my feature implementation?▼

A data-model.md file is generated when the feature requires it. The planning process evaluates the spec and research documents to determine if a separate data model definition is necessary for the implementation plan.

Related Skills

Explore More Software Engineering Skills→
shep-aishep-ai
241

shep-kit:research

Generate research.yaml and Markdown documentation for feature implementation decisions.

Official
Advanced
jrmatherlyjrmatherly
1

shipit-kit:implement

Validate YAML feature specs and execute TDD implementation tasks.

Community
Advanced
jrmatherlyjrmatherly
1

shipit-kit:status

Report progress and next actions for a ShipIT feature branch.

Community
Intermediate
bychrisrbychrisr

aiox-po

Manage product backlogs and user story lifecycles with automated validation and prioritization.

Community
Advanced