create-plan

Create detailed implementation plans from feature specs or bug reports.

1|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/yangsi7/skill-builder --skill create-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/yangsi7/skill-builder/tree/main/.claude/skills/create-plan
Command: npx skills add https://github.com/yangsi7/skill-builder --skill create-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires project-intel.mjs, Read, Write, Edit, and includes examples (resource) and references (resource) and workflows (resource) components.

What problem does it solve?

This Skill eliminates the tedious, manual work of project planning, which often leads to vague tasks and untestable requirements. It ensures every task has clear, verifiable acceptance criteria, saving you hours of rework and confusion.

Core Features & Use Cases

  • Intelligent Task Breakdown: Automatically breaks down feature specifications or bug reports into manageable, estimated tasks.
  • Test-First Acceptance Criteria: Generates at least two testable acceptance criteria for every task, ensuring clarity and quality from the start.
  • Dependency Mapping: Identifies task and file dependencies, revealing critical paths and parallelization opportunities for efficient execution.
  • Use Case: You have a new feature specification. Instead of spending days manually breaking it down, use this Skill to instantly generate a detailed plan.md with tasks, testable ACs, and a dependency graph, ready for implementation.

Quick Start

To create a plan from an existing feature specification:

Ensure your spec.md is in specs/<feature-id>/spec.md

Then, simply invoke the skill:

/plan specs/my-new-feature/spec.md

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I break down a feature specification into testable tasks automatically?

Task breakdown converts feature specs or bug reports into granular, estimated tasks with dependencies. This Skill generates detailed plans with at least two testable acceptance criteria per task, dependency graphs, and critical-path analysis—eliminating manual decomposition and vague requirements.

What are acceptance criteria and why does every task need them?

Acceptance criteria define measurable, verifiable conditions that confirm a task is complete. This Skill generates at least two testable criteria per task to ensure clarity, prevent rework, and enable quality gates before implementation begins.

Can this create project plans from bug reports and refactoring work?

Yes. This Skill applies to feature planning, refactors, migrations, and bug fixes. It intelligently decomposes any input specification into structured tasks with acceptance criteria, dependencies, and post-analysis validation across all project phases.

How does dependency mapping help with project execution?

Dependency mapping identifies task and file relationships, revealing critical paths and parallelization opportunities. This reduces bottlenecks, enables concurrent work, and produces a reproducible dependency graph for efficient scheduling.

What input format does this Skill expect?

The Skill accepts feature specifications or bug reports as input. Place your spec in `specs/<feature-id>/spec.md`, then invoke the Skill to generate a detailed `plan.md` with tasks, acceptance criteria, and dependency visualization.

Does this Skill produce artifacts I can share with my team?

Yes. The Skill generates reproducible, traceable artifacts including `plan.md` with tasks, acceptance criteria, dependency graphs, and constitutional compliance validation—ready for handoff, review, and implementation tracking.