plan-orchestrator

Creates repository-aligned multi-agent implementation plans with ownership, waves, and verification matrices.

Updated Jan 31, 2023
One-click install
npx skills add https://github.com/Briian3306/Transporte --skill plan-orchestrator-briian3306
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-orchestrator
Source: https://github.com/Briian3306/Transporte/tree/main/ibarra-app/.agents/skills/plan-orchestrator
Command: npx skills add https://github.com/Briian3306/Transporte --skill plan-orchestrator-briian3306

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-agent work on an epic or feature often produces vague plans, overlapping file ownership, and untracked progress. This Skill generates structured execution plans that assign every task a single owner, disjoint file scope, required skills, and concrete verification commands, while keeping feature_list.json and progress logs synchronized. ## Core Features & Use Cases - Structured Epic Planning: Normalizes a request into docs/plan/<epic>/PLAN_<epic>.md with scope, invariants, dependency waves, and a task/owner/skill matrix. - TDD-Prescribed Tasks: Every behavior task specifies a failing test, red run, minimal green implementation, refactor, and evidence recording. - Synchronized Tracking: Updates feature_list.json, docs/claude-progress.md, and docs/session-handoff.md so planned work stays consistent across artifacts. - Use Case: Given a PRD for a new Supabase-backed Angular feature, produce a plan splitting backend, frontend, documentation, and QA work across agents with exact files and verification commands. ## Quick Start Use the plan-orchestrator skill to create an execution plan for the new reporting epic based on the PRD in docs.

Frequently Asked Questions about plan-orchestrator

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

FAQPage Schema
How do I create a multi-agent implementation plan for an epic?▼

Invoke the skill with the epic request; it normalizes the name to lowercase-hyphenated form and writes docs/plan/<epic>/PLAN_<epic>.md. The plan includes scope, invariants, dependency waves, and a task/owner/skill matrix with exact files and verification commands.

How does the plan assign owners and required skills to tasks?▼

Each task gets exactly one owner with disjoint file scope, mapped through a work-type table: Supabase backend work goes to 01-backend-supabase, Angular UI to the frontend owner, documentation to 04-documentador, and integration to 05-integrador-qa. Required execution skills are listed per row.

Does this skill write product code or migrations?▼

No. The skill only creates plans and may write docs/plan/, feature_list.json, docs/claude-progress.md, and docs/session-handoff.md. Implementation, SQL, migrations, routes, and tests are explicitly out of scope while the skill is active.

How are feature statuses tracked after planning?▼

Planned features are recorded in feature_list.json with ID, owner, dependencies, and not_started status plus concrete verification. A feature is never moved to in_progress or passing merely because it was planned; evidence from executed work is required.

When does a plan require test-driven development steps?▼

Every behavior-change task must prescribe TDD: a failing behavior test, expected red run, minimal green implementation, green run, safe refactor, and recorded evidence. Configuration-only work must instead explain why TDD does not apply and give direct validation.