phase-orchestrator
SolidOrchestrates 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.
Install
Quality Score: 83/100
Skill Content
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
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.
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.
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.