planner

Decompose project goals into tasks and milestones with a structured plan schema.

Updated Feb 10, 2026

Search Tags:#planning #specification #coordination #plan #project-management #work-breakdown #modular-design

Ready to run

npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill planner-will-aveva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/Will-Aveva/phoenix-chassis/tree/main/.agent/skills/planner
Command: npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill planner-will-aveva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Partitions project work into coherent, testable units, enabling clear ownership, traceability, and incremental execution without ambiguity.

Core Features & Use Cases

Defines a standard plan schema with sections such as Approach, Work Breakdown, Files & Modules, Test Plan, Risks & Rollback, and Observations.
Supports cross-team coordination by decomposing goals into tasks and milestones, with explicit artifact wiring between modules.
Use Case: When starting a new feature, generate a Plan that maps tasks to owners, deadlines, dependencies, and validation steps.

Quick Start

Provide a project scope and constraints, and the planner will generate a structured Plan with a detailed Work Breakdown and milestone mapping.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I break down project goals into testable work units?▼

To decompose project goals into testable work units, partition project work into clear tasks and milestones using a standard plan schema with sections for Work Breakdown, Files & Modules, and Test Plan. This enables clear ownership, traceability, and incremental execution without ambiguity.

What is the best way to coordinate cross-module dependencies during project planning?▼

Cross-module coordination is achieved by decomposing goals into tasks and milestones with explicit artifact wiring between modules. A structured plan maps tasks to owners, deadlines, dependencies, and validation steps to satisfy systems integration requirements.

How do I generate a structured plan for a new feature?▼

To generate a structured plan for a new feature, provide the project scope and constraints. The planner outputs a detailed Work Breakdown and milestone mapping with defined Approach, Risks & Rollback, and Observations sections.

Does this project planning approach work for research and systems integration phases?▼

Yes, this planning approach applies to the planning phases of product development, systems integration, and research projects. It organizes work into executable plans where cross-module coordination is explicitly required.

What sections are required in a standard work breakdown schema?▼

A standard plan schema requires sections for Approach, Work Breakdown, Files & Modules, Test Plan, Risks & Rollback, and Observations. These sections use MCP tools for symbol discovery and reference tracing to ensure traceability.