do-plan

Generates implementation plans and dependency-ordered task checklists from requirement and design documents.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/khoavu882/do-flow --skill do-plan-khoavu882
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-plan
Source: https://github.com/khoavu882/do-flow/tree/main/core/shared/skills/do-plan
Command: npx skills add https://github.com/khoavu882/do-flow --skill do-plan-khoavu882

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning approved requirements and design documents into an actionable, dependency-ordered implementation plan is error-prone manual work. This Skill automates Phase 3 of the DoFlow chain, producing a plan.md with a Constitution Check, task breakdown, and branch plan so implementation can start with clear ownership and file scoping. ## Core Features & Use Cases - Plan Generation: Converts requirement.md and design.md (plus specs.md IC-### interface contracts when present) into a structured plan.md with approach, research decisions, risks, and validation strategy. - Task Decomposition: Produces dependency-ordered tasks traced to user stories, with named owners, concrete file paths, and [P] parallel markers enabling write-set isolation during execution. - Constitution Check & Validation: Runs an advisory constitution gate and consistency validation, then records evidence, claims, and a workflow handoff for downstream stages. - Use Case: After finishing /do-design for a new feature, run /do-plan to get a task checklist that /do-execute-plan can execute with parallel-safe task scheduling. ## Quick Start Ask the AI to run /do-plan to create an implementation plan and task breakdown from the existing requirement.md and design.md for the current feature.

Frequently Asked Questions about do-plan

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

FAQPage Schema
How do I create an implementation plan from requirements and design docs?▼

Run /do-plan after requirement.md and design.md exist. It resolves the feature context, validates a task class, reads the design contracts, and writes plan.md with an approach, research decisions, and a dependency-ordered task checklist.

What inputs does do-plan require before it can run?▼

It expects requirement.md and design.md from earlier DoFlow phases, and reads specs.md interface contracts when the resolver reports has_specs. Missing requirement or design files trigger an advisory warning suggesting /do-brainstorm or /do-design first.

How does do-plan mark tasks for parallel execution?▼

Tasks whose files sets are disjoint from their phase siblings get a [P] marker by default, enabling /do-execute-plan to run them concurrently with write-set isolation. Tasks sharing file paths stay unmarked and execute sequentially.

Does do-plan create git branches or write code?▼

No. It only derives a branch plan (feat/<ticket>-<slug> naming and a per-repo Repo Branch Plan table) without creating branches. Code writing and execution are handled by /do-execute-plan, and design artifacts belong to /do-design.

What happens when the runtime rejects a proposed task class?▼

The skill stops, prints the rejection message listing valid classes, and asks the user to choose one before re-validating. It never substitutes the feature class silently, and non-feature classes like bug or refactor skip plan.md entirely.