plan

Convert spec.md into a phase-based plan.md with milestones and verification steps.

3|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill plan-sirius-cc-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/sirius-cc-wu/sirius-skills/tree/main/plan
Command: npx skills add https://github.com/sirius-cc-wu/sirius-skills --skill plan-sirius-cc-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a software specification (spec.md) into a concrete, step-by-step implementation plan (plan.md), reducing ambiguity and accelerating development.

Core Features & Use Cases

  • Phase-based planning with Phase 0 (Environment & Baseline), Phase 1 (Core Implementation), and Phase 2 (Refinement, Documentation, and Edge Cases).
  • Outputs a plan.md that contains discrete, verifiable steps and milestones aligned to the spec.
  • Supports activation by guiding the implement skill to track progress and update plan milestones as steps are completed.

Quick Start

Generate a plan.md from spec.md by outlining Phase 0 to Phase 2 milestones with discrete, verifiable tasks.

Frequently Asked Questions about plan

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

FAQPage Schema
What is the best way to track progress against software milestones after planning?

The best way to track progress against software milestones is to use the generated plan.md alongside an implement skill. The plan guides the implement skill to update milestones and track progress as verifiable steps are completed.

How do I turn a software specification into a step-by-step implementation plan?

To turn a software specification into an implementation plan, you provide a spec.md file to generate a structured plan.md. This plan translates the specification into phase-based milestones and concrete, test-driven steps for module development.

What is test-driven planning for software module development?

Test-driven planning for software module development structures your implementation into discrete, verifiable test steps. It transforms a specification into a plan.md that defines milestones and verification checkpoints across distinct development phases.

How do I structure development milestones using phase-based planning?

Phase-based planning structures development milestones by dividing work into Phase 0 for environment setup, Phase 1 for core implementation, and Phase 2 for refinement. This outputs a plan.md with discrete, verifiable steps aligned to your spec.

Do I need a spec.md file to generate a test-driven implementation plan?

Yes, you need a spec.md file present in the target module to generate a test-driven implementation plan. The process parses the contents of this specification file to output a structured plan.md with phase prompts and milestones.

What is the best way to track progress against software milestones after planning?

The best way to track progress against software milestones is to use the generated plan.md alongside an implement skill. The plan guides the implement skill to update milestones and track progress as verifiable steps are completed.