plan-create

Create structured .context/plans/ Markdown files with validated YAML frontmatter and phased task decomposition.

Updated Apr 9, 2014
One-click install
npx skills add https://github.com/thoroc/thoroc.github.io --skill plan-create-thoroc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-create
Source: https://github.com/thoroc/thoroc.github.io/tree/main/.agents/skills/plan-create
Command: npx skills add https://github.com/thoroc/thoroc.github.io --skill plan-create-thoroc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Drafting implementation plans by hand often produces inconsistent structures, missing frontmatter, and oversized phases that cannot be reviewed or indexed. This Skill scaffolds plans that match the repository's existing conventions and pass frontmatter validation on the first attempt. ## Core Features & Use Cases - Convention Inference: Scans existing .context/plans/ files to classify sections as core, common, or rare, and follows the majority file-naming convention instead of hardcoding a template. - Graded Frontmatter: Requires effort (S/M/L/TBD), value (HIGH/MEDIUM/LOW), and ordered themes from a closed vocabulary, graded against a rubric rather than guessed. - Phased Decomposition: Splits work into 2-5 phases of 2-5 tasks each, with exit criteria and explicit wave annotations for parallel work. - Use Case: A developer asks to plan an SQS DLQ redrive feature. The Skill gathers goal and scope, drafts a plan with effort: M and value: HIGH, validates the frontmatter with a shell script, and offers to hand off to the plan-review skill. ## Quick Start Ask the agent to create a plan for your next piece of work, describing the goal, scope, and rough implementation steps.

Frequently Asked Questions about plan-create

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

FAQPage Schema
How do I create a structured implementation plan for a software project?▼

Describe the goal, scope, phases, and tasks to the agent, which drafts a .context/plans/ Markdown file with YAML frontmatter, phased tasks, and open questions. The plan is then validated with a frontmatter script before being finalized.

What frontmatter fields are required for a plan file?▼

A plan requires title, type: PLAN, status: DRAFT, date, effort (S/M/L/TBD), value (HIGH/MEDIUM/LOW), and an ordered themes list from a closed vocabulary. Missing fields make the plan invisible to the context index.

How does the skill decide which sections a plan should include?▼

It runs a grep frequency scan over existing .context/plans/ files and classifies sections as core (>=40%), common (20-39%), or rare (<20%). Goal, Phases, and Open Questions are always included; optional sections follow the scan evidence.

What should I do when a plan's effort cannot be estimated yet?▼

Set effort: TBD and add an Open Questions entry naming the specific blocker, such as a pending vendor answer. Guessing a size just to pass validation is explicitly discouraged because it misleads triage.

When should I not use this plan scaffolding approach?▼

Do not use it for the main project SKILL.md, agent skill files, one-off scratch notes, or trivially small single-step work. Those cases use the skill template or inline notes instead.