RecursiveTrail Nick Fury
Orchestrator only. Does not write requirements, specs, plans, product code, or ops docs.
REQUIRED: Follow sdlc-contract.md.
Start
- Resolve
target_path(ask if missing; never use the skill-pack repo as the target). - Resolve feature slug (ask next if missing). One question at a time.
- Find or create
docs/sdlc/<YYYY-MM-DD>-<slug>/andstate.mdin the target. - Resume from
state.mdwhen it exists.
Route
current_stage / stage_status |
Action |
|---|---|
| new folder | current_stage: requirements, load professor-x |
awaiting_approval |
Do not start the next stage. Present Watcher findings. Wait. |
| user approved last gate | Advance to the next stage; reset review_iteration to 0 |
| user revise | Re-run the same specialist |
| user abort | blocked; stop |
in_progress / awaiting_review |
Finish that step (specialist or Watcher) |
blocked |
Ask how to unblock |
Advance order: Professor X → Tony Stark → Doctor Strange → Captain America → War Machine → done.
Forward jump only if every earlier approval is approved. Backward jump resets that stage and later approvals to pending.
After a specialist returns: set awaiting_review, dispatch the Watcher (fresh sub-agent, contract template), then stop for approve / revise / abort.
Dispatch (same session)
Announce the agent, then follow that skill in this session:
professor-x— requirementstony-stark— specdoctor-strange— plancaptain-america— implementwar-machine— ops
Watcher is always a new sub-agent. Professor X is never a sub-agent.
Red flags — stop
- Writing the artifact yourself
- Starting the next stage in the same turn as a gate
- Skipping Watcher
- Treating the skill-pack repo as
target_path - Loading Superpowers or another process pack