skills.rest
ybbms777
ybbms777COMMUNITY
Explore all skills by this author →
GitHub

ce:plan

Transform feature descriptions into repo-aligned implementation plans with file paths and test scenarios.

1|Updated Apr 4, 2026
Search Tags:#software engineering#implementation plan#technical planning#test scenarios#requirements breakdown#plan deepening#repo patterns
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill ce-plan-ybbms777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:plan
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/ce-plan
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill ce-plan-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and misalignment that come with turning vague feature ideas or raw requirements documents into actionable technical implementation plans, ensuring plans follow existing codebase patterns and include all necessary details for developers to execute confidently without rework.

Core Features & Use Cases

  • New Plan Generation: Creates structured implementation plans from feature descriptions or requirements documents, grounded in existing repo patterns, research, and institutional learnings.
  • Plan Deepening: Strengthens existing plans via interactive review of sub-agent findings to fill confidence gaps in technical decisions, test scenarios, and risk assessments.
  • Use Case: After a ce:brainstorm session produces a requirements document for a new comment summarization feature, use this Skill to generate a plan with explicit file paths, test scenarios, and dependency sequencing that the development team can execute immediately.

Quick Start

Use the ce:plan skill to generate a structured implementation plan for the new comment summarization feature described in docs/brainstorms/2026-03-10-comment-summary-requirements.md.

Frequently Asked Questions about ce:plan

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

FAQPage Schema
How do I turn product requirements into a technical implementation plan?▼

To turn product requirements into a technical implementation plan, use a structured planning approach that analyzes feature descriptions and grounds the output in existing repository patterns to ensure alignment.

What is the best way to break down feature requirements into executable steps?▼

Breaking down feature requirements into executable steps involves mapping the needs to specific file paths, defining explicit test scenarios, and sequencing dependencies to guide the development team.

Can I deepen an existing technical plan to fill confidence gaps?▼

Yes, you can deepen an existing technical plan through an interactive review process that addresses confidence gaps in technical decisions, test scenarios, and risk assessments.

Does implementation plan generation write the actual code for the feature?▼

No, implementation plan generation provides clear guidance and structured steps without writing the actual implementation code, leaving the coding execution to the developers.

How do I ensure my technical plans follow existing codebase patterns?▼

To ensure technical plans follow existing codebase patterns, the planning process must analyze and incorporate repository patterns, research, and institutional learnings into the structured output.

What should a software engineering implementation plan include?▼

A software engineering implementation plan should include explicit file paths, test coverage requirements, dependency sequencing, and risk assessments to enable confident execution.

Related Skills

Explore More Software Engineering Skills→
apollostreetcompanyapollostreetcompany

ce:plan-beta

Create structured implementation plans from feature descriptions or requirements documents.

Community
Advanced
alysonhoweralysonhower
1

clavix-verify

Audit code and documentation against PRD and plan requirements.

Community
Advanced
deandumdeandum
3

discovery

Grep the repository to identify related code and write a discovery.md handoff plan.

Community
Intermediate
wachawowachawo

to-issues

Decompose project specifications into vertical slices with dependency mapping.

Community
Advanced