plan

Transform feature descriptions and bug reports into structured markdown implementation plans.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/beratcelik1/compound-claude --skill plan-beratcelik1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/beratcelik1/compound-claude/tree/main/skills/plan
Command: npx skills add https://github.com/beratcelik1/compound-claude --skill plan-beratcelik1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many feature requests, bug reports, and improvement ideas arrive as informal descriptions that lack scope, acceptance criteria, and a clear implementation path, causing rework and delays. This Skill formalizes those inputs into structured, trackable plans so teams can move from intent to execution with fewer iterations.

Core Features & Use Cases

  • Parallel research: Searches the codebase, past solutions, and project conventions to ground the plan in real context.
  • Requirements refinement: Asks clarifying questions to define purpose, constraints, success criteria, and scope.
  • Plan structuring and authoring: Produces a dated markdown plan file with YAML frontmatter, problem statement, acceptance criteria, technical considerations, implementation steps, and checklists.
  • Use Case: Turn a high-level request like "add social login" into a standard implementation plan with dependencies, risks, and next-step actions for engineers and reviewers.

Quick Start

Use the plan skill to create a standard implementation plan for adding OAuth login support with acceptance criteria and implementation steps.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a feature request into an implementation plan with acceptance criteria?

To create an implementation plan, provide a feature description or bug report. The system refines requirements through clarifying questions and generates a markdown file with YAML frontmatter, acceptance criteria, technical considerations, and step-by-step actions.

What is the best way to structure project planning for a new software feature?

Structuring project planning involves transforming informal ideas into a standard plan. This process defines scope, success criteria, and dependencies, producing a dated markdown document with checklists to guide engineering and review phases.

Can I generate a comprehensive implementation plan from a high-level bug report?

Yes, you can generate a comprehensive implementation plan from a bug report. The system analyzes the informal input, performs parallel codebase research to gather context, and outputs a structured plan with risks and next-step actions.

Does this project planning approach work for both minimal and comprehensive software scopes?

Yes, this project planning approach supports minimal, standard, and comprehensive scopes. It adapts to various software development workflows by grounding the plan in real project conventions and generating tailored implementation steps.

How do I ensure my implementation plan includes relevant code patterns and technical considerations?

To ensure your implementation plan includes relevant code patterns, the system searches past solutions and project conventions during parallel research. It then links these technical considerations directly within the generated markdown plan file.