# orchestration-readme

orchestration-readme breaks large features into structured task files, tracks active stages, and aligns code changes with Git commits inside Claude Code.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/orchestration/ORCHESTRATION-README.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/orchestration-readme

## What it does

The command provisions a dedicated directory hierarchy inside `task-orchestration/`. When initialized via `/orchestration/start`, Claude Code asks clarifying questions about user requirements, builds `MASTER-COORDINATION.md` alongside `EXECUTION-TRACKER.md`, and sorts tasks into folders such as `todos/`, `in_progress/`, `qa/`, and `completed/`.

Task states update directly with `/orchestration/move <id> <status>`. When work on a ticket wraps up, `/orchestration/commit` drafts a standardized Git commit message tied directly to the ticket identifier. The `/orchestration/report` command can output summaries formatted for daily standups or higher-level overviews.

All tracking depends on local Markdown files within the repository. Without running `/orchestration/sync`, external Git changes made outside the assistant will not reflect in the tracker files.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/ORCHESTRATION-README.md` — Call it with /ORCHESTRATION-README. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/ORCHESTRATION-README.md` — Call it with /prompts:ORCHESTRATION-README. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/ORCHESTRATION-README.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/ORCHESTRATION-README.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/orchestration/ORCHESTRATION-README.md

## When to use it
- decompose massive feature specs into discrete markdown task cards
- restore working context after breaks using `/orchestration/resume`
- reconcile task board states against repository commit history
- produce structured progress digests for team standups

## Example prompts
- /orchestration/start Build authentication module with login and email password reset
- /orchestration/status --today
- /orchestration/move TASK-003 qa

## Similar
- [implement-task-linear](https://affpapa.org/en/nevibecode/skills/implement-task-linear.md) — skill · 346 installs
- [conductor](https://affpapa.org/en/nevibecode/plugins/conductor.md) — plugin · ★ 42780 repo stars
- [groove-daily-start](https://affpapa.org/en/nevibecode/skills/groove-daily-start.md) — skill · 573 installs
- [todo](https://affpapa.org/en/nevibecode/commands/todo.md) — command · 2723 installs
- [repo-orchestration](https://affpapa.org/en/nevibecode/skills/repo-orchestration.md) — skill · 431 installs
- [c-linear](https://affpapa.org/en/nevibecode/skills/c-linear.md) — skill · ★ 179 repo stars

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
