phase-orchestrator

Solid

Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes plans in the write-phase-plan format. Use when the user provides a plan, checklist, PRD, or phase document and asks for delegated multi-agent execution across phases.

Code & Development 13 stars 1 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
38
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Phase Orchestrator ## Goal Run a phase-based plan through a repeatable delegated workflow. The plan is the source of truth, any PRD/spec is supporting context, and each phase should move through orientation, implementation, validation, review, plan updates, and commits by default. Use this skill only when the user explicitly asks for delegated phase orchestration, invokes this skill, or asks to implement a plan/checklist using subagents. ## Companion Skills This skill is the parent of a five-skill workflow: - `write-phase-plan` — authors plans in the format this skill consumes best. - `phase-implementer` — the delegated worker contract for implementing exactly one phase (Phase Loop step 2). - `phase-reviewer` — the delegated worker contract for the review-and-fix pass on a completed phase (Phase Loop step 4). - `phase-final-reviewer` — the delegated worker contract for the end-to-end review of the whole feature after all phases (Final Whole-Feature Pass). Each worker skill carries that role's standing rules: single-phase or single-pass scope, no-revert discipline, no-commit default, and the required final-response format. The parent's prompt only needs to supply the per-run context from the templates below. How to dispatch a worker role depends on the host: 1. **Named custom agents.** If the host supports named custom agents or subagent types (Cursor custom agents, for example), prefer a dedicated agent per role whose definition is the matching companio...

Details

Author
hraness
Repository
hraness/wordcell
Created
2 months ago
Last Updated
2 weeks ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

phase-orchestrator

Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes plans in the write-phase-plan format. Use when the user provides a plan, checklist, PRD, or phase document and asks for delegated multi-agent execution across phases.

0 Updated 2 weeks ago
hraness
AI & Automation Listed

phase-orchestrator

Execute an existing multi-phase repository plan with bounded implementation workers, independent review, join gates, validation, and final integration. Use when the user explicitly asks for delegated or multi-agent execution of a phase plan. Do not use for ordinary single-owner coding, plan authoring, semantic reasoning, or as a replacement for host scheduling and repo gates.

0 Updated yesterday
hraness
AI & Automation Listed

orchestrator

Coordinate large, multi-feature implementations by acting as an orchestrator that spawns focused sub-agents — one per RFC or feature area — while managing phasing, parallelization, and integration verification. Use this skill when a task spans 3+ independent features, multiple RFCs, or requires parallel implementation across different areas of the codebase. Also triggers on phrases like "orchestrate this", "spawn sub-agents", "implement all RFCs", "parallel implementation", "multi-agent", or "build the full app". Do NOT use for single-feature or single-file tasks — those should be implemented directly.

2 Updated 1 weeks ago
mouchegmouradian