ce-plan

Creates structured implementation plans for software features and non-software tasks.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-plan-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-plan
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-plan
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-plan-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a feature idea, requirements document, or vague goal into an actionable plan requires research, scoping, and sequencing that is easy to get wrong. This Skill produces durable, repo-grounded implementation plans with traced requirements, ordered implementation units, and explicit test scenarios. ## Core Features & Use Cases - Structured Plan Generation: Breaks work into dependency-ordered implementation units with stable U-IDs, repo-relative file paths, and enumerated test scenarios. - Research-Driven Planning: Dispatches parallel research agents for codebase patterns, institutional learnings, framework docs, and best practices before structuring the plan. - Plan Deepening: Runs a confidence-gap scoring pass on existing plans and strengthens weak sections via targeted sub-agent research with interactive review. - Universal Planning: Routes non-software tasks (trips, study plans, events) to a domain-agnostic workflow with curated options and research. - Use Case: After brainstorming a new authentication feature, invoke this Skill to produce a dated plan file in docs/plans/ with requirements traceability, key technical decisions, and per-unit test scenarios ready for execution. ## Quick Start Ask the agent to create a plan for your feature by saying "plan the user authentication flow" and it will research the codebase and write a structured plan document.

Frequently Asked Questions about ce-plan

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

FAQPage Schema
How do I create an implementation plan for a new feature?

Invoke the planning skill with a feature description or path to a requirements document. It researches the codebase, classifies plan depth, breaks work into ordered implementation units, and writes a dated plan file to docs/plans/ with test scenarios.

What is the difference between brainstorming and planning a feature?

Brainstorming defines what to build through requirements discovery, while planning defines how to build it through technical decisions and implementation units. A brainstorm document is useful input but never required for planning.

Can I deepen or strengthen an existing plan document?

Yes, saying "deepen the plan" triggers a confidence-gap scoring pass that identifies weak sections, dispatches targeted research agents, and lets you accept or reject each finding interactively before updating the plan.

Does the planning skill work for non-software tasks?

Yes, non-software requests route to a universal planning workflow that handles trips, events, study plans, and research tasks. It asks focused questions, optionally researches current facts, and produces domain-appropriate structured plans.

When should I skip planning and go straight to implementation?

Skip planning when the task has a known root cause, an obvious fix, and no architectural decisions. The skill itself suggests the execution workflow as a faster alternative for clear, ready-to-execute tasks.