Agent skill · writing content · aiskillstore
plan-directory
Create or update a structured plan directory with a master PLAN.md index and numbered task files (001-*.md). Each task file includes goal, dependencies, scope, checklist, tests, and completion criteria. Use when scaffolding a repeatable project plan in markdown, especially when the user wants a master index plus per-task files with checkboxes that are checked off as work completes.
Why this skill is useful
Provides a structured template for project planning in markdown, including specific formatting and content requirements that the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Plan Directory Skill When to Use This Skill Scaffolding a new project, feature, or migration that benefits from a structured, step-by-step plan. Creating a repeatable plan that an LLM or engineer can execute with explicit, verifiable checkboxes. Maintaining an existing plan directory: adding tasks, updating progress, or archiving completed plans. When the user says "create a plan", "scaffold a plan", "plan this feature", or similar intent implying structured task breakdown. Do not use this skill for ad-hoc todo lists, single-file notes, or when the user explicitly wants a different format. LLM Intake (Required Inputs) Before writing any files, gather these inputs. If any are missing, ask the user for them explicitly. Input Required Description ------- ---------- ------------- Plan title Yes Human-readable name (e.g., "User Authentication Overhaul") Plan slug Yes Hyphenated directory/file slug (e.g., user-auth-overhaul) Target location No Directory path; defaults to docs/plans/<slug>/ or plans/<slug>/ Task list Yes List of tasks with short names and scopes Locked decisions No Key constraints or choices that must not change Testing expectations No Commands, subsets, or manual QA requirements When updating an existing plan, read the current PLAN.md first to understand context before modifying. Invariants (Do Not Violate) 1. PLAN.md is the index, not the content. It contains only the purpose, usage instructions, locked decisions, and a task index with checkboxes. Detailed steps live in individual task files. 2. Task files use 3-digit numbering. Format: NNN-<slug>.md where NNN is zero-padded (001, 002, ..., 999) and <slug> is hyphenated lowercase. 3. Every task file has six sections. Goal, Scope, Checklist, Tests, Completion Criteria, and Dependencies. All are required (use "None" for Dependencies if truly independent, "N/A" for Tests only with justification). 4. Checkboxes are the only status markers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/plan-directory