Transform feature descriptions into structured implementation plans with repo-relative file paths.
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-plan-bradliebs
Please help me install this Agent Skill. Skill: ce-plan Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/ce-plan Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-plan-bradliebs
Transform feature descriptions into structured implementation plans grounded in repo patterns and research. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce-brainstorm first.
Provide a well-defined feature description or requirements and ask ce-plan to generate a structured implementation plan.
High-intent search queries and answers about installing and using this skill.
To turn feature requirements into an implementation plan, you provide a feature description to generate a structured plan. This process frames the problem, defines scope, captures dependencies, and outlines implementation units with repo-relative file paths.
Structuring technical plans for team collaboration involves creating executable, repo-relative implementation units and specifying test scenarios. This approach ensures portability and traceability across repositories during planning workflows.
You deepen an existing technical plan by applying an interactive review of sub-agent findings. This refines the existing scope, dependencies, and decisions to make your implementation strategy more durable and actionable.
You do not need fully defined requirements before creating an implementation plan, but they should be at least roughly defined. For exploratory or ambiguous requests, it is recommended to brainstorm requirements first before technical planning.
An actionable implementation plan should include framed problems, defined scope, captured decisions and dependencies, outlined implementation units with repo-relative file paths, and specified test scenarios for traceability.
You should use a plan deepening pass when you already have an existing plan that needs refinement through interactive findings. Use plan creation instead when starting from a fresh feature description or requirements document.
wangrenzhu-olaCreate structured implementation plans with scope, risks, dependencies, and test guidance.
JetaofgakCreate implementation plans with exact file paths, code examples, and verification steps.
FrkAkTrack tasks, dependencies, decisions, and implementation records for software projects.
bennybennisonClarify rough product ideas into structured IdeaBriefs for evaluation.
