plan

Convert phase requirements into a PLAN.md with tasks and verification criteria.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill plan-hoang604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill plan-hoang604

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap phases often lack a reproducible structure for turning goals into actionable tasks; this Skill creates a formal PLAN.md that codifies phase objectives, tasks, and verification criteria.

Core Features & Use Cases

  • Produces a PLAN.md that enumerates 2-3 atomic tasks with explicit done criteria.
  • Supports integration with SPEC.md and ROADMAP.md to align outputs with governance.
  • Applies optional TDD-style checks when requested to ensure testable interfaces.

Quick Start

Provide a phase number (and optional flags) to generate a PLAN.md that decomposes the phase into executable tasks.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert roadmap phases into executable tasks with verification criteria?

To convert roadmap phases into executable tasks, you provide a phase number to generate a PLAN.md that scopes 2-3 atomic tasks with explicit done criteria. This formalizes phase objectives into a structured format for automated execution.

What is the best way to structure a phase plan for automated execution and future auditing?

The best way to structure a phase plan for automated execution is generating a PLAN.md that embeds constraints, references, and success criteria directly into the task definitions. This ensures future auditing can trace executed work back to phase requirements.

Does the plan generation process support TDD-style checks for testable interfaces?

Yes, the phase plan generation process applies optional TDD-style checks when requested to ensure testable interfaces. This integrates verification criteria directly into the PLAN.md task definitions.

How do I handle high-complexity work when scoping roadmap phases into atomic tasks?

To handle high-complexity work when scoping roadmap phases, the plan generation process automatically includes a checkpoint task within the 2-3 atomic tasks. This checkpoint ensures complex requirements are verified before moving to the next phase.

Can I integrate PLAN.md outputs with existing SPEC.md and ROADMAP.md governance files?

Yes, you can integrate PLAN.md outputs with existing SPEC.md and ROADMAP.md files to align generated tasks with project governance. This ensures the decomposed phase requirements remain consistent with broader roadmap objectives.