agentleFS
Sign inStart free
mmaripanguecmmaripanguec/dev-sdd-kit/.claude/skills/orchestrate/SKILL.md

orchestrate

Skill2 starsChanged 4 months agoMITView on GitHub

Walks the E2E 9-phase cycle for a feature, delegating to the per-phase agents and stopping at each human gate. Only invocable by humans.

161 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use define-requirements, orchestrate-plan and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sson0-erSkill

    define-requirements

    Work with the user, one question at a time, to complete the requirements document (docs/claudex/<slug>/01-requirements.md). Run by the orchestrator (parent). Stays out of design and implementation.

    Also in 3 projects that use this

  • EternallLightSkill

    orchestrate-plan

    Use when executing a locked, reviewed PLAN.md by delegating the implementation to visible worker agents in Orca, herdr, or cmux ONE PHASE at a time — splitting the plan into context-window-sized phases, giving every phase a pristine worker context, and (when the plan touches INDEPENDENT repos) running one worker per repo IN PARALLEL. Triggers on "run the plan with a worker", "execute the plan in the other pane", "split the plan into phases and build it with workers", "build the backend and frontend in parallel panes". Not for edits you can finish inline; outside Orca, herdr, or cmux use tgc-skills:orchestrate.

    Also in 3 projects that use this

  • sson0-erSkill

    record-evidence

    How to record external facts (docs, command output, codebase findings) as evidence and design choices as decisions. Used by the researcher, designer and reviewer agents.

    Also in 3 projects that use this

  • PinkneyJiangSkill

    improve-architecture

    扫描代码库中的架构摩擦点，识别浅模块并挖掘深模块演进机会。生成可视化交互式 HTML 诊断报告，并在用户确认后闭环实施深度重构。

    Also in 4 projects that use this

  • kjnezSkill

    ticket

    Work on a JIRA/Linear ticket end-to-end: read ticket details, explore codebase, create a branch, implement with TDD, run quality checks, update ticket status, and create a PR. Use when the user provides a ticket ID to implement. Triggers on requests like "/ticket PROJ-123", "work on this ticket", "implement PROJ-123".

    Also in 4 projects that use this

  • xfstudioSkill

    reverse-engineer

    Expert reverse engineer specializing in binary analysis,

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 144 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the E2E cycle for: $ARGUMENTS

    line 8
  2. Distinctive:

    After each phase: write the artifact in specs/ or knowledge/ and commit before moving on (a mid-flow failure does not lose previous phases).

    line 12
  3. Distinctive:

    When F9 finishes: verify the cycle closed — postmortems and incidents fed knowledge/, and the spec ended in "implemented" state with its …

    line 41

“Common” is measured: kept by at least 6 in 10 of the 144 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the E2E cycle for: $ARGUMENTS

Global orchestrator rules

  • Sequential: advance phase by phase; NEVER skip a human gate.
  • After each phase: write the artifact in specs/ or knowledge/ and commit before moving on (a mid-flow failure does not lose previous phases).
  • Escalate: on ambiguity, contradiction or impossible verification, stop and ask the human at the nearest gate. Do not assume.
  • Accountability: record in each gate's artifact who approved, when, and on which version (commit).

Sequence

F0 Triage → STEP 0 of /spec-create: existing application or new application? · load the current context packs · dependencies without context => ASK (repo, onboarding, pack), never assume · inconsistency => ASK · ambiguity detected => /clarify (max. 5 questions; the decisions feed /spec-create and, once the spec is created, are recorded in its Clarifications section) F1 Requirement → requirements subagent → INVEST stories P1-P3 → PO/TL GATE F2 Estimation → estimation subagent → points + WSJF F3 Refinement → loop /spec-review + fixes until DoR; /consistency with FIT FOR GATE verdict → DoR GATE F4 Analysis → analysis subagent → rules, deps, limits F5 Design → architecture subagent → contracts, C4, ADRs; /consistency with FIT FOR GATE verdict → Architecture GATE F6 Construction → /harness-init if multi-session; then /implement-task for each task in the plan (TDD) F7 Certification → /converge (gaps → TC tasks, implemented with TDD) + quality subagent → verdict → QA/PR GATE F8 Production → release subagent → risk dossier → CAB Committee GATE F9 Operations → operations subagent → monitoring, postmortem → DevOps/SRE GATE

When F9 finishes: verify the cycle closed — postmortems and incidents fed knowledge/, and the spec ended in "implemented" state with its full traceability (spec → ADR → commits → dossier → operations).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free