create-plan

Generate a task-oriented implementation plan with file changes, tests, and commits.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/momingse/paceforge --skill create-plan-momingse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/momingse/paceforge/tree/main/.claude/skills/create-plan
Command: npx skills add https://github.com/momingse/paceforge --skill create-plan-momingse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams rapidly produce a structured, step-by-step implementation plan for a requested feature or task, reducing planning overhead and ensuring consistency across plans.

Core Features & Use Cases

  • Structured planning: Generates a comprehensive plan with sections for files touched, tasks, tests, and commits.
  • Reproducible outputs: Saves the plan to a deterministic location based on the feature name and current date.
  • Use Case: When handed a feature brief, generate a plan that can be handed to engineers to implement the feature with clear milestones.

Quick Start

Generate a complete implementation plan for the requested feature and save it to the designated plans directory.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I auto-generate a detailed implementation plan for a feature request?

An implementation plan organizes feature development into step-by-step tasks, explicitly scaffolding required file changes, tests, and commit sequences across a codebase to reduce planning overhead and ensure consistency.

How do I create reproducible implementation plans with clear task decomposition?

Reproducible implementation plans are generated by saving the structured task decomposition to a deterministic Markdown path named ./plans/YYYY-MM-DD-<feature-name>.md, ensuring consistent retrieval and tracking for engineering teams.

Does this implementation plan generator require specific dependencies or component setups?

No specific dependencies or component setups are required to use this implementation plan generator, allowing teams to immediately generate structured engineering plans from a feature brief without prior environment configuration.

What is the best way to scaffold codebase changes and commit sequences for a new feature?

The best way to scaffold codebase changes is to generate a comprehensive plan that explicitly defines file modifications, test scaffolding, and commit sequences, providing engineers with clear milestones for feature implementation.

When should I avoid using an automated tool for engineering documentation and planning?

You should avoid automated engineering documentation when a feature requires exploratory coding without explicit file changes or commit sequences, as this tool outputs structured, task-oriented plans designed for reproducible implementation.