Generate Implementation Steps

Break approved Spec.md and Tech.md into numbered implementation tasks with paired tests and documentation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rghamilton3/mission-control-rack --skill generate-implementation-steps-rghamilton3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Generate Implementation Steps
Source: https://github.com/rghamilton3/mission-control-rack/tree/main/.claude/skills/plan-steps
Command: npx skills add https://github.com/rghamilton3/mission-control-rack --skill generate-implementation-steps-rghamilton3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many feature specs are too large or vague for teams to implement directly; this Skill converts an approved Spec.md and Tech.md into a concrete, ordered set of small implementation tasks with paired tests and documentation so work can be executed, tracked, and validated across multiple agents and domains.

Core Features & Use Cases

  • Structured Task Generation: Breaks a feature into numbered implementation tasks (S001-S999), produces paired test (S###-T) and documentation (S###-D) tasks, and groups work into milestone waves.
  • Team Orchestration & Contracts: Suggests team composition based on stacks touched, assigns owners, declares dependencies, marks milestones, and lists contract file paths for downstream consumers.
  • Review & Iteration: Produces Steps.md in Context/Features/NNN-FeatureName/Steps.md, provides milestone verification criteria, and supports user-driven adjustments to assignments and dependencies.

Quick Start

Generate a Steps.md for Context/Features/123-NewFeature by breaking the approved Spec.md and Tech.md into numbered implementation tasks with paired test and documentation tasks and listing milestone contracts.

Frequently Asked Questions about Generate Implementation Steps

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

FAQPage Schema
How do I break down a feature spec into executable implementation tasks?

To break down a feature spec into executable implementation tasks, this Skill reads approved Spec.md and Tech.md files to generate a numbered, ordered list of tasks (S001-S999) with paired test and documentation requirements saved directly into Steps.md.

What is the best way to generate paired test and documentation tasks for a new feature?

Generating paired test and documentation tasks requires scanning approved architectural records and specs to structure work into milestone waves, assigning specific test (S###-T) and documentation (S###-D) tasks for every implementation step.

Does generating implementation steps require approved Tech.md and Spec.md files?

Yes, generating implementation steps requires approved Tech.md and Spec.md files. The Skill operates during phase three of a planning workflow and relies on these documents to identify domains, scan active rules, and declare team composition.

How do I organize feature milestones and assign tasks across multiple agents?

To organize feature milestones and assign tasks across multiple agents, the Skill identifies available agents, suggests team composition based on touched stacks, declares dependencies, and marks milestone waves with verification criteria in the output.

Can I adjust team orchestration and task assignments after generating Steps.md?

Yes, you can adjust team orchestration and task assignments after generating Steps.md. The Skill supports user-driven modifications to assignments, dependencies, and milestone contracts to accommodate evolving project requirements.

When do I need to use milestone contracts for task breakdown?

You need milestone contracts for task breakdown when a feature touches multiple domains like backend, frontend, or database, ensuring downstream consumers have defined file paths and verification criteria for each milestone wave.