Convert approved SPECs into phased execution plans with dependencies.
npx skills add https://github.com/zazzcode/zazz-skills --skill planner-zazzcode
Please help me install this Agent Skill. Skill: planner Source: https://github.com/zazzcode/zazz-skills/tree/main/.agents/skills/planner Command: npx skills add https://github.com/zazzcode/zazz-skills --skill planner-zazzcode
Plans are hard to derive from complex SPECs; this skill converts an approved SPEC into a concrete, phased execution plan that guides teams.
Provide an approved SPEC path and repository context to generate a detailed PLAN that decomposes work, assigns file ownership, and specifies tests and coordination rules.
High-intent search queries and answers about installing and using this skill.
To turn an approved SPEC into an execution-ready plan, you provide the SPEC path and repository context. The system decomposes the spec into phases, assigns file ownership, specifies tests, and generates a PLAN.md file beside the original spec.
Task decomposition for complex software specifications breaks approved SPECs into concrete steps and defined phases. This process applies repository context to align with AGENTS.md, coordinates shared files, and captures explicit dependencies for team execution.
You generate a phased plan with file ownership by feeding an approved SPEC into the planner. It produces a PLAN.md that defines ownership, establishes tests traceability, and outlines coordination rules while updating the deliverables index.
The generated plan strictly preserves the original SPEC file. It creates a separate PLAN.md document beside the spec to ensure the original requirements remain untouched while updating the deliverables index for discoverability.
You can apply repository context to align plans with AGENTS.md. The planner extracts shared-file coordination guidance and merge points from your repository configuration to ensure the execution plan matches your project constraints.
The best way to coordinate shared files during execution planning is capturing merge points and explicit dependencies within a PLAN.md. This approach extracts coordination rules from AGENTS.md to guide teams through shared-file conflicts.
pradeepmouliGenerate baseline-spec.md and current-state.md from repository analysis.
Clouder0Enforce file ownership boundaries to prevent conflicts during parallel development.
jayhjenkinsRestate code review feedback and verify against the repository before implementing changes.
MinhThang1009Generates a dependency-aware execution plan with non-overlapping file assignments from a task list.
