planning

Generates PLAN.md and TASKS.md session artifacts through a four-step gated planning workflow.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/truongnat/Restly --skill planning-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/truongnat/Restly/tree/main/.agents/skills/planning
Command: npx skills add https://github.com/truongnat/Restly --skill planning-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns design documents and discussion notes into concrete, executable implementation plans, preventing vague task lists, skipped clarifications, and premature coding by enforcing a strict step-by-step planning contract. ## Core Features & Use Cases - Template-seeded artifacts: Copies PLAN.md and TASKS.md templates into the session folder, then fills strategy first and micro-task cards second. - Decision gate and spec quality review: Stops to ask focused questions on Critical or blocking issues and validates feasibility, correctness, and capability gaps before any task breakdown. - Work inventory and micro-task cards: Splits design into one card per implementable unit with Trace references, checkbox work items, falsifiable acceptance criteria, and cited Dev context. - Use Case: Given a DETAIL_DESIGN.md for a new API feature, run this Skill to produce a PLAN.md with goal, scope, risks, and task index plus a TASKS.md with ordered, verifiable micro-tasks ready for execution. ## Quick Start Use the planning skill to create PLAN.md and TASKS.md from my DETAIL_DESIGN.md in the current session folder.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create an implementation plan from a design document?▼

Run the planning workflow, which seeds PLAN.md and TASKS.md from templates, then fills strategy in PLAN.md before deriving micro-task cards in TASKS.md. It reads DETAIL_DESIGN.md first, falling back to BASIC_DESIGN.md or DISCUSSION.md when absent.

What is the difference between PLAN.md and TASKS.md?▼

PLAN.md holds strategy only: goal, scope, assumptions, approach phases, risks, and a task index of IDs and titles. TASKS.md holds the work inventory and detailed micro-task cards with work items, acceptance criteria, verification steps, and Dev context.

When does the planning workflow stop and ask questions?▼

It stops when a Critical issue, blocking unknown, blocking spec quality finding, or unconfirmed html-recommended visual decision is open. It asks at most three focused questions at a time and records answers before filling strategy or tasks.

Can the planning skill write or implement code?▼

No, the skill explicitly does not implement code. It only produces planning artifacts, and its contract forbids coding, skipping steps, or silently choosing defaults for omitted feature policy.

Why does planning fail its self-check with Ready=No?▼

Ready stays No when checks fail, such as missing work inventory, vague layer-only task titles, cards without Trace references or Dev context, unresolved blockers, or high-impact assumptions still unconfirmed. Fix the listed failures and re-run the self-check step.