ce-plan

Transform vague prompts into structured plans with requirements and traceable decisions.

10|Updated Dec 13, 2016

Search Tags:#workflow #planning #requirements #project-management #decision-log #implementation-units

Ready to run

npx skills add https://github.com/vitallium/dotfiles --skill ce-plan-vitallium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-plan
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-plan
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-plan-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan writing transforms vague prompts into a structured, decision-ready plan with requirements, units, and traceable decisions.

Core Features & Use Cases

Create durable implementation plans for software features, research workflows, events, or study plans.
Deepen existing plans through interactive sub-agent review to strengthen rationale and risk handling.
Surface origin context and enforce repo-relative references so plans remain portable across teams and machines.
Route outputs to docs/plans/ and align with ce-work for execution or ce-brainstorm for scoping when needed.

Quick Start

Describe your task in a sentence and I will generate a structured plan you can review or execute.

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 implementation plan from a vague prompt?▼

Plan writing transforms a vague prompt into a structured, decision-ready plan by generating requirements, implementation units, and a traceable decision log. You simply describe your task in a sentence to get a reviewable plan.

Can I use this planning workflow for research and study plans, not just software features?▼

Yes, this planning workflow applies to software features, research workflows, events, and study plans. It creates durable implementation plans with clear origin context and explicit tests to guide execution across these varied use cases.

What is the best way to deepen an existing project plan and strengthen its rationale?▼

Deepening an existing plan is done through an interactive sub-agent review that strengthens rationale and risk handling. This process surfaces origin context and enforces repo-relative references so plans remain portable across teams.

How do I ensure my multi-step task plans remain portable across different machines?▼

Plans remain portable across machines by surfacing origin context and enforcing repo-relative references within the plan structure. The outputs are routed to a specific directory to maintain consistency for team execution.

Does this planning approach require explicit tests to guide execution?▼

Yes, explicit tests are required to guide execution and validation of the generated plan. This ensures the structured plan is decision-ready and can be validated effectively upon implementation.

What should I do when I need to scope a task before generating a full implementation plan?▼

When a task needs scoping before generating a full implementation plan, you should align with a brainstorming tool to define the boundaries. This ensures the subsequent plan writing receives clear origin context to produce accurate requirements.