planner

Convert approved SPECs into phased execution plans with dependencies.

3|1|Updated Feb 19, 2026

Search Tags:#planning #coordination #execution #spec #plan #task-decomposition

Ready to run

npx skills add https://github.com/zazzcode/zazz-skills --skill planner-zazzcode

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans are hard to derive from complex SPECs; this skill converts an approved SPEC into a concrete, phased execution plan that guides teams.

Core Features & Use Cases

Converts an approved SPEC into a phased PLAN with defined ownership, tests traceability, and coordination rules.
Produces a PLAN beside the SPEC and updates the deliverables index for discoverability.
Supports shared-file coordination guidance from AGENTS.md and captures merge points and dependencies.

Quick Start

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.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I turn an approved SPEC into an execution-ready plan?▼

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.

What is task decomposition for complex software specifications?▼

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.

How do I generate a phased plan with file ownership from a spec?▼

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.

Does the generated plan preserve the original SPEC file?▼

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.

Can I apply repository context to align plans with AGENTS.md?▼

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.

What is the best way to coordinate shared files during execution planning?▼

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.