planner

Convert user requirements into a task breakdown in PLAN.md.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill planner-hoonzinope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/hoonzinope/skills/tree/main/planner
Command: npx skills add https://github.com/hoonzinope/skills --skill planner-hoonzinope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The planner converts user requirements into a concrete implementation plan and task breakdown, writing the result to .documents/plan/PLAN.md to standardize execution.

Core Features & Use Cases

  • Generate a plan from requirements including milestones, tasks, owners, and effort estimates.
  • Scaffold a fresh PLAN.md or append updates to an existing PLAN.md while preserving structure.
  • Enforce guardrails to ensure planning documents live under .documents/ and reference the provided templates.

Quick Start

Turn your requirements into an actionable plan and task list by asking the planner to create or update .documents/plan/PLAN.md.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I turn project requirements into an actionable task list?

You can break down requirements by generating a plan that maps milestones, tasks, owners, effort estimates, and dependencies, writing the structured task list directly to a PLAN.md file.

What is the best way to scaffold a project planning document?

The best way to scaffold a planning document is to use a provided template to render a PLAN.md file under the .documents directory, enforcing structural guardrails for your milestones and tasks.

Can I append task updates to an existing PLAN.md without losing structure?

Yes, you can append updates to an existing PLAN.md. The planner modifies the existing planning document while preserving its original structure, milestones, and task hierarchy.

Does the planner enforce where planning documents are stored?

Yes, the planner enforces guardrails that require all planning documents to be written under the .documents directory, specifically scoping output to .documents/plan/PLAN.md.

What details are included in the task breakdown for workflow planning?

The task breakdown includes milestones, specific tasks, assigned owners, effort estimates, task dependencies, and completion status to provide a comprehensive workflow planning document.