create

Create a structured project planning directory and plan.md template.

13|1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill create-serbanghita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create
Source: https://github.com/serbanghita/claude-code-plan-critique/tree/main/skills/create
Command: npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill create-serbanghita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent project planning by enforcing a structured, template-driven approach to creating new task plans, ensuring all necessary context is captured before execution begins.

Core Features & Use Cases

  • Standardized Templates: Automatically generates a structured plan.md file with required sections for affected files and verification steps.
  • Session Linking: Automatically tracks the plan lifecycle by linking the current process ID to the specific plan directory.
  • Use Case: When starting a new feature, use this skill to generate a consistent planning folder and template, ensuring you define success criteria and affected files before writing any code.

Quick Start

Use the create skill to initialize a new project plan named user-authentication.

Frequently Asked Questions about create

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

FAQPage Schema
How do I standardize project planning and initialization for new features?

To standardize project planning, you can use a template-driven approach that automatically generates a structured plan.md file with required sections for affected files and verification steps before execution begins.

How do I create a consistent planning folder for iterative development workflows?

You can create a consistent planning folder by initializing a structured project planning directory that manages filesystem-safe plan slugs and links active process IDs to specific planning tasks.

What is the best way to document affected files and verification criteria before writing code?

The best way to document affected files and verification criteria is to enforce mandatory documentation within a standardized template file during project initialization, ensuring project consistency.

Can I track the plan lifecycle by linking active sessions to specific planning tasks?

Yes, you can track the plan lifecycle by linking the current process ID to the specific plan directory, which automatically manages the session linking for iterative development workflows.

Does template-driven project planning work without external dependencies?

Template-driven project planning works without external dependencies, as it initializes a structured project planning directory and template file directly to enforce documentation of affected files and verification criteria.