team-roadmap-dev

Convert a project request into phased PLAN, EXEC, and VERIFY workflows.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-roadmap-dev-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-roadmap-dev
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/team-roadmap-dev
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-roadmap-dev-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of complex coding work getting stuck in a single-threaded, ad hoc flow by turning one request into a coordinated roadmap with clear phases, roles, and handoffs.

Core Features & Use Cases

  • Roadmap discussion and session setup: Captures the project goal, execution mode, and analysis depth before work begins.
  • Phased task orchestration: Creates linked PLAN, EXEC, and VERIFY tasks with dependencies, gap-closure loops, and phase transitions.
  • Role-based team workflow: Routes work to coordinator, planner, executor, and verifier roles for research, implementation, and validation.
  • Persistent progress tracking: Maintains session state, roadmap artifacts, summaries, and verification results across runs.
  • Use Case: A developer asks for a feature rollout or refactor, and the Skill breaks it into phases, dispatches each stage to the right role, and tracks completion until the work is verified.

Quick Start

Ask the team-roadmap-dev skill to plan and run a phased implementation for your coding task, then follow the coordinator’s prompts to confirm the roadmap and continue through execution and verification.

Frequently Asked Questions about team-roadmap-dev

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

FAQPage Schema
How do I break a complex software request into phased execution workflows?

Multi-agent orchestration coordinates complex coding by routing work to specialized coordinator, planner, executor, and verifier roles. This role-based team workflow manages research, implementation, and validation to prevent single-threaded ad hoc bottlenecks.

Can I maintain session state across multiple runs of a multi-step coding project?

Yes, persistent session state maintains roadmap artifacts, summaries, and verification results across runs. This ensures continuous progress tracking and coordinated execution even when the phased workflow spans multiple interactions.

What is the best way to verify task completion in a multi-agent roadmap workflow?

Verification in a multi-agent roadmap workflow uses gap-closure loops to validate task completion before phase transitions. The verifier role checks implementation results against the roadmap plan to ensure requirements are satisfied.

How do I set up task dispatch for a feature rollout or refactor?

Task dispatch for a feature rollout starts with roadmap discussion to capture project goals, execution mode, and analysis depth. The system then creates linked tasks with dependencies and routes them to coordinator, planner, executor, and verifier roles.

When do I need gap-closure loops in software development orchestration?

Gap-closure loops are needed in software development orchestration when phased workflows require validation before transitioning between PLAN, EXEC, and VERIFY stages. They ensure dependencies are resolved and task outputs meet verification requirements.