ce-plan

Generate structured implementation plans with dependencies and testing criteria.

2|Updated Aug 20, 2024
One-click install
npx skills add https://github.com/theZMC/dotfiles --skill ce-plan-thezmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-plan
Source: https://github.com/theZMC/dotfiles/tree/main/.agents/skills/ce-plan
Command: npx skills add https://github.com/theZMC/dotfiles --skill ce-plan-thezmc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ce-plan creates structured, implementation-ready plans for multi-step tasks such as software features, research workflows, events, or study plans, and supports deepening existing plans with interactive reviews of sub-agent findings.

Core Features & Use Cases

  • Generate durable, implementation-ready plans from user goals, requirements, bug reports, or briefs.
  • Break work into implementation units with clear dependencies, testing needs, and risk notes.
  • Deepen plans interactively by reviewing sub-agent findings and refining scope and decisions.
  • Use bootstrap planning for ambiguous inputs and adapt plans as requirements evolve.
  • Preserve origin decisions and traceability when origin documents are provided.

Quick Start

Provide a complete, implementation-ready plan for a multi-step goal from a user brief or requirements, outputting ordered implementation units with dependencies and test scenarios.

Frequently Asked Questions about ce-plan

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

FAQPage Schema
How do I create a structured project plan from a brief?

Structured project planning breaks multi-step goals into ordered implementation units with dependencies, testing criteria, and risk notes. It applies to software features, research workflows, or events, transforming briefs into actionable, implementation-ready plans.

What is the best way to break work into implementation units with dependencies?

Breaking work into implementation units involves decomposing user goals or requirements into discrete, ordered tasks. Each unit is mapped with clear dependencies, testing needs, and risk notes, ensuring a portable and revisable plan structure.

Can I use requirements traceability to preserve origin decisions in a plan?

Yes, requirements traceability preserves origin decisions when origin documents are provided during planning. The system retains these source decisions within the generated plan artifacts, keeping them portable and revisable as requirements evolve.

Does project planning work for ambiguous inputs or evolving requirements?

Yes, project planning handles ambiguous inputs through bootstrap planning, which initiates structure from rough ideas. It also adapts existing plans interactively as requirements evolve, refining scope and decisions without losing traceability.

How do I deepen existing plans with sub-agent findings?

Deepening existing plans involves interactively reviewing sub-agent findings within the planning workflow. This process refines the scope and updates decisions, allowing the plan to absorb new research or technical details while remaining portable.

What are the limitations of using structured plans for research workflows?

A limitation of structured plans for research workflows is the need for defined inputs to generate actionable implementation units. Highly unstructured research without clear goals may yield less effective units, though bootstrap planning can mitigate this.