ce-plan

Convert feature descriptions into structured Markdown plan documents.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill ce-plan-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-plan
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/ce-plan
Command: npx skills add https://github.com/drhazemibclc/plate --skill ce-plan-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform feature descriptions into well-structured project plans that follow conventions to accelerate planning and alignment.

Core Features & Use Cases

  • Generate comprehensive plan documents from user-provided feature descriptions, bug reports, or improvement ideas.
  • Support brainstorming integration, research preparation, risk assessment, and milestone definition.
  • Provide a ready-to-review plan structure with sections for overview, assumptions, implementation phases, acceptance criteria, and references.

Quick Start

Describe your feature idea in a sentence, and I will generate a structured plan following project conventions.

Frequently Asked Questions about ce-plan

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

FAQPage Schema
How do I turn a feature description into a structured project plan?

To turn a feature description into a structured project plan, provide a brief idea or bug report, and the tool generates a Markdown document with overview, implementation phases, assumptions, and acceptance criteria.

What sections are included in a generated feature plan document?

A generated feature plan document includes sections for overview, assumptions, implementation phases, acceptance criteria, and references, ensuring cross-reference support and task-scoping details align with project conventions.

Can I use this for bug reports and improvement ideas, or only new features?

You can use this for bug reports and improvement ideas as well as new features. It translates all these inputs into reusable plan formats with origin tracking, risk assessment, and milestone definition.

What's the best way to plan phased implementations for stakeholders?

The best way to plan phased implementations for stakeholders is generating a ready-to-review Markdown plan that defines milestones, captures requirements, and assesses risks to accelerate team alignment.

Do I need a specific format to start brainstorming and requirement capture?

You do not need a specific format to start brainstorming and requirement capture. Describing your feature idea in a single sentence is enough to generate a structured plan following project conventions.