Generate Implementation Steps

Generate ordered implementation steps with paired test and documentation tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of breaking down a software feature into detailed, ordered implementation steps, including paired testing and documentation tasks, ensuring a clear and manageable development workflow.

Core Features & Use Cases

  • Task Decomposition: Divides complex features into granular, sequential implementation tasks.
  • Paired Testing & Documentation: Automatically generates corresponding test and documentation tasks for each implementation step.
  • Milestone Tracking: Organizes tasks into logical phases with milestone markers for progress verification.
  • Use Case: After a feature's technical design is approved, use this Skill to generate a Steps.md file that outlines every coding, testing, and documentation task required for completion, complete with parallelization hints and review checkpoints.

Quick Start

Use the plan steps skill to break down the feature described in Context/Features/NNN-FeatureName/Tech.md into implementation steps.

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 software feature into actionable implementation steps?

To break down a software feature, this Skill generates a phased workflow of implementation steps with paired testing and documentation tasks from approved specifications, outputting an ordered task list in a `Steps.md` file.

What is the best way to generate paired testing and documentation tasks for project planning?

Generating paired testing and documentation tasks is achieved by decomposing complex features into sequential milestones, automatically creating corresponding verifiable test and documentation actions for each coding phase.

Do I need approved technical design files before generating implementation tasks?

Yes, you need prerequisite `Spec.md` and `Tech.md` files containing approved feature specifications and technical designs to provide the required context for generating the implementation workflow.

How does task decomposition handle parallelization and milestone tracking?

Task decomposition handles parallelization by organizing granular tasks into logical phases with milestone markers and parallelization hints, facilitating project planning and progress verification.

Can I use this for workflow automation if my feature lacks a technical design document?

No, you cannot use this for workflow automation without a technical design document, as the Skill requires prerequisite `Spec.md` and `Tech.md` files to generate the verifiable development workflow.

Why include documentation tasks directly in the development workflow breakdown?

Including documentation tasks directly in the development workflow breakdown ensures that every implementation step has paired documentation, creating a clear, manageable, and verifiable task sequence for project completion.