auto-orchestrator

Auto Orchestrator

Overview

This skill automatically detects where you are in the development lifecycle and invokes the right skills in sequence. Instead of manually calling /spec, then /plan, then /build, etc., you describe what you want and this skill figures out what's needed and drives through each phase with gate checks between them.

When to Use

• You have a feature, project, or task and want Claude to drive it end-to-end
• You're not sure which skill to start with
• You want the full lifecycle: spec -> plan -> build -> test -> review -> simplify -> ship

How It Works

Phase Detection

Before doing anything, assess the current state:

1. Does a spec exist for this work?
   - NO  -> Start at Phase 1 (Spec)
   - YES -> Move to next check

2. Is the work broken into tasks?
   - NO  -> Start at Phase 2 (Plan)
   - YES -> Move to next check

3. Is there code to implement?
   - YES, unfinished tasks remain -> Start at Phase 3 (Build + Test)
   - YES, all tasks done -> Move to next check

4. Has the code been reviewed?
   - NO  -> Start at Phase 4 (Review + Simplify)
   - YES -> Move to next check

5. Is it ready to ship?
   - YES -> Start at Phase 5 (Ship)

Phase 1: Spec (spec-driven-development)

Trigger: No spec exists, requirements are vague or incomplete.

Action: Read ${HAMZAISH_ROOT:-$HOME/Claude/Hamzaish}/factory/skills/spec-driven-development/SKILL.md and follow its full process.

Gate: Present the spec to the user. Do NOT proceed to Phase 2 until the user approves the spec.

Output: A structured spec with acceptance criteria.

---

Phase 2: Plan (planning-and-task-breakdown)

Trigger: Spec exists but work hasn't been broken into tasks.

Action: Read ${HAMZAISH_ROOT:-$HOME/Claude/Hamzaish}/factory/skills/planning-and-task-breakdown/SKILL.md and follow its full process.

Gate: Present the task breakdown to the user. Do NOT proceed to Phase 3 until the user approves the plan.

Output: Ordered list of tasks with acceptance criteria and dependencies.