run-orchestrator
SolidExecute 5-phase TDD workflow for complex features. Use when the user invokes /run, asks to build/create/implement a feature, requests a complex multi-file change, or types 'fasttrack:'. Enforces phase gates, sprint contracts, and builder!=reviewer discipline.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- nguyenthienthanh
- Repository
- nguyenthienthanh/aura-frog
- Created
- 8 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
orchestrate
Run the full flow workflow end-to-end — kickoff (framing + setup) → optional research → plan (with optional multi-LLM brainstorming) → develop → deploy → optional cleanup — based on a single task goal from the user. Use this when the user wants to hand off a complete task and let the workflow run, rather than driving each step manually. Skips research and brainstorming automatically for size S tasks; runs the full pipeline for size L. Even when the user just says "build me X", consider this skill if the task warrants the full discipline.
orchestrate
Advance one planwright spec by one step: pick the next ready unit critical-path-first (or a cohesion bundle), run the freshness gate, record the dispatch under the per-spec lock, and dispatch /execute-task via the backend. A stateless, disposable control tower; a reconcile sweep rebuilds from disk. Never merges, marks a PR ready, or auto-chains into /spec-kickoff. --bookkeeping runs the drain + PR reconcile; --watch loops the step.
workflow-orchestrator
Take on a substantial, multi-step effort as a strategic orchestrator — intake the goal, research and plan it solo, execute it through parallel/sequential agent workflows, then personally verify the result end to end. Use this whenever the user wants to tackle something big or ambitious: a large feature, a cross-cutting refactor, a migration, a codebase-wide audit, a "do all of X / sync everything / overhaul Y" task, or any effort that won't fit in one pass and needs to be planned and orchestrated with rigor. Trigger when the user invokes it by name, says things like "orchestrate this / run a workflow / use subagents / plan and build this / take this on end to end," OR simply describes a meaty multi-part task and wants it done thoroughly and efficiently — even if they never say the words "workflow" or "orchestrate." Do NOT use it for small, single-step tasks that one pass handles directly.