plan-review

Decomposes approved design specs into executable implementation plans with tasks and review gates.

10|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Zhijiang-Li1111/ironflow --skill plan-review-zhijiang-li1111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/Zhijiang-Li1111/ironflow/tree/main/skills/plan-review
Command: npx skills add https://github.com/Zhijiang-Li1111/ironflow --skill plan-review-zhijiang-li1111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a design into a precise implementation plan that prevents scope creep and missed requirements.

Core Features & Use Cases

  • Breaks approved specs into fine-grained tasks.
  • Requires human confirmation before execution.
  • Guides end-to-end planning from design to coding.

Quick Start

Submit an approved design spec and let this skill produce a task-by-task execution plan for implementation.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I turn a design spec into an executable implementation plan?

To turn a design spec into an implementation plan, you submit the approved specification for decomposition into fine-grained, task-by-task execution steps with tests and review gates. This prevents scope creep by ensuring actionable handoff directly into coding.

What is the best way to break down software features into coding tasks?

Breaking down software features into coding tasks requires decomposing approved specs into fine-grained units with associated tests. This approach ensures precise execution planning and includes human review gates before development begins, preventing missed requirements during refactors.

Does implementation planning require human review before execution?

Implementation planning requires human review and confirmation before execution to ensure accuracy. This human-in-the-loop gate validates the decomposed task breakdown, preventing scope creep and verifying that the plan aligns with the approved design specification.

How does task decomposition work with TDD for software refactoring?

Task decomposition with TDD creates fine-grained tasks that include associated tests within the implementation plan. This structured breakdown applies to software refactoring by defining specific review gates and actionable execution steps before coding begins.

Can I use this for both new features and software refactoring plans?

You can use this implementation planning process for both new features and software refactoring. It guides end-to-end planning from design to coding by breaking approved specifications into precise, executable tasks with human review across various software projects.

When do I need a detailed implementation plan for my software project?

You need a detailed implementation plan when moving from design to coding to prevent scope creep and missed requirements. It decomposes approved specs into actionable, task-level execution steps with tests and review gates for a structured handoff.