Transform feature descriptions into structured implementation plans grounded in repository patterns.
npx skills add https://github.com/vib795/copilot-anatomy --skill ce-plan-vib795
Please help me install this Agent Skill. Skill: ce-plan Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/ce-plan Command: npx skills add https://github.com/vib795/copilot-anatomy --skill ce-plan-vib795
Transforms feature descriptions or requirements into structured implementation plans grounded in repository patterns and research, enabling teams to plan with clarity and consistency.
Provide a feature description or requirements to start a new plan, or specify an existing plan to deepen.
High-intent search queries and answers about installing and using this skill.
To convert feature requirements into an implementation plan, provide your feature descriptions or brainstorm documents to generate structured, repeatable plans anchored to repository patterns and research.
You can deepen an existing technical plan by requesting a deeper review, which triggers an interactive analysis of sub-agent findings to add unit-level guidance and strengthen repository traceability.
The best way to match repository patterns is to use a planning process that automatically anchors implementation steps and scope definitions to your codebase's existing use case scenarios and structural conventions.
Yes, you can use a brainstorm or requirements document as input for technical planning to transform scattered ideas into a named plan with defined scope and actionable unit-level guidance.
When generating implementation plans from scattered requirements, outputs are limited to the structural conventions provided and require explicit feature descriptions or brainstorm documents to ensure accurate scope and traceability.
You need a completed requirements or brainstorm document to start technical planning, as the process requires feature descriptions to generate structured, named plans with actionable unit-level guidance.
kenhiaTransform feature descriptions into structured implementation plans grounded in repo patterns.
vulikjulikExecute markdown implementation task plans sequentially with persistent progress tracking.
GaryOcean428Orchestrate a multi-agent red-team planning workflow to produce implementation plans.
muklesTranslate feature requirements into structured implementation plans with test scenarios.
