Agent skill

Orchestrate Project

by danielvm-git in danielvm-git/bigpowers

Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates.

MITAuto-check passed

Install Orchestrate Project

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestrate-project .claude/skills/orchestrate-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .claude/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestrate-project .agents/skills/orchestrate-project && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .agents/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestrate-project .cursor/skills/orchestrate-project && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .cursor/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/orchestrate-project

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestrate-project .gemini/skills/orchestrate-project && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .gemini/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestrate-project .github/skills/orchestrate-project && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .github/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill orchestrate-project -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers orchestrate-project --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestrate-project .opencode/skills/orchestrate-project && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "orchestrate-project" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/orchestrate-project into .opencode/skills/orchestrate-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate-project", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: orchestrate-project
GitHub stars: 257
Token cost: ~923 tokens
SKILL.md length: 323 words
Files: 2
Skills in repo: 39
Repo updated: Sep 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates.

Works in 6 steps: DISCOVER (3-6 hours): Understand… → ELABORATE (3-6 hours): Research… → PLAN (2-4 hours): Write verifiable plan.… → …
Coordinate multi-phase projects with guaranteed quality checkpoints
SKILL.md covers Quick Start, The 6-Phase Core Loop, How Orchestrate Works and Orchestration Modes, plus 1 more section
Calls claude and bash

What it does

Orchestrate Project is an agent skill from danielvm-git/bigpowers. Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Use to coordinate multi-phase projects with guaranteed quality checkpoints. One-time command for the entire project lifecycle.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `REFERENCE.md`).

The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

Coordinate multi-phase projects with guaranteed quality checkpoints

Example prompts

“/orchestrate-project”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

DISCOVER (3-6 hours): Understand problem. Deliverables: requirements/VISION_LATEST.yaml, requirements/SCOPE_LATEST.yaml…
ELABORATE (3-6 hours): Research solutions. Deliverables: Prior art in scope YAML, ADRs in specs/adr/.
PLAN (2-4 hours): Write verifiable plan. Deliverables: release-plan.yaml, epics/eNN-*.yaml with verify: per task.
BUILD (1-8 hours): Execute plan. Runs build-epic once per story in WSJF order. Deliverables: Code; update execution-status.yaml.
VERIFY (1-3 hours): Validate success criteria. Deliverables: UAT evidence, specs/EVALS-*.md if used.
RELEASE (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z), state.yaml release.last_tag.

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- claude
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Orchestrate Project loads about 923 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 323 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~67
When it runs · the whole SKILL.md, loaded when a task matches: ~923

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 323 words, ~923 tokens.

Download SKILL.mdSave it as .claude/skills/orchestrate-project/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: orchestrate-project
description: Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Use to coordinate multi-phase projects with guaranteed quality checkpoints. One-time command for the entire project lifecycle.
model: sonnet
effort: standard

Orchestrate

HARD GATE — HARD GATE — Do NOT invoke orchestrate-project unless you have a clear multi-phase workflow. Single-skill tasks should use dedicated skills instead. Orchestrate is for complex, multi-stage work that requires coordination across phases.

The orchestrate skill coordinates projects through a prescriptive 6-phase core loop with hard gates, ensuring consistent quality and preventing scope creep.

Quick Start

bash

# Start a new project (initializes specs/ YAML cockpit and begins discover phase)
claude /orchestrate --mode standard

# Or resume an existing project at the current phase
claude /orchestrate --mode standard --resume

# For low-risk scenarios (hotfixes, refactors on well-tested code)
claude /orchestrate --mode fast-track

The 6-Phase Core Loop

DISCOVER (3-6 hours): Understand problem. Deliverables: requirements/VISION_LATEST.yaml, requirements/SCOPE_LATEST.yaml, plans/TECH_STACK_LATEST.md.
ELABORATE (3-6 hours): Research solutions. Deliverables: Prior art in scope YAML, ADRs in specs/adr/.
PLAN (2-4 hours): Write verifiable plan. Deliverables: release-plan.yaml, epics/eNN-*.yaml with verify: per task.
BUILD (1-8 hours): Execute plan. Runs build-epic once per story in WSJF order. Deliverables: Code; update execution-status.yaml.
VERIFY (1-3 hours): Validate success criteria. Deliverables: UAT evidence, specs/EVALS-*.md if used.
RELEASE (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z), state.yaml release.last_tag.

Checkpoint / resume

Track progress via specs/state.yaml project_cycle:

project_cycle.current_phase: current phase (1–6)
project_cycle.completed_phases: completed phase numbers
handoff.next_skill: skill for the current phase
On resume, read project_cycle.current_phase and continue from there

See REFERENCE.md for detailed phase specifications and gate types.

How Orchestrate Works

Maintains state.yaml — Tracks current phase, active_epic, active_flow, decisions, risks.
Spawns appropriate skills — Routes by model: frontmatter. Decisions pass only via specs/state.yaml handoff between spawns.
Methodology lenses — If specs/tech-architecture/e*-TEST_PLAN_LATEST.md or ADRs exist, apply at phase gates.
Enforces gates — Hard stops if success criteria not met.
The Gatekeeper — Between stories in BUILD: read specs/execution-status.yaml; previous story must be done before starting the next; use build-epic for the 8-step epic cycle.
Pauses for confirmation — After each phase, asks "Ready to proceed?".
Snapshots — bash scripts/bp-yaml-snapshot.sh before major release cuts.

Orchestration Modes

Standard: Enforce all gates. Use for new features and major refactors.
Fast-Track: Skip negotiable gates. Use for hotfixes and minor improvements.
Ad-Hoc: Warnings only. Use for prototyping and spikes (non-production).

See REFERENCE.md for full mode behaviors.

Verification

All phases complete with artifacts:

bash

verify: test -f specs/state.yaml && test -f specs/release-plan.yaml && test -f specs/product/SCOPE_LATEST.yaml && ls specs/epics/*.yaml 1>/dev/null && echo "✅ All phases complete"

<!-- story: e05s03 -->

Files

SKILL.md and 1 other file in skills/orchestrate-project of danielvm-git/bigpowers.

SKILL.md
REFERENCE.md

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Orchestrate Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Orchestrate Project compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Orchestrate Project this skilldanielvm-git/bigpowers	257	—	~923	Automated safety check: Pass	MIT	16 days ago
Team Agent Orchestrationaffaan-m/ECC	275k	1 repos	~1.2k	Automated safety check: Pass	MIT	3 days ago
Orca Orchestrationstablyai/orca	87k	—	~916	Automated safety check: Pass	MIT	today
Agent Orchestrator Taskruvnet/ruflo	74k	3 repos	~1k	Automated safety check: Pass	MIT	today
Plan Orchestrateaffaan-m/ECC	275k	1 repos	~4.5k	Automated safety check: Pass	MIT	3 days ago
Orchestratesickn33/agentic-awesome-skills	47k	1 repos	~692	Automated safety check: Pass	MIT	today

Similar skills

Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
275k GitHub starsUsed in 1 repo~1.2k tokens
Agent WorkflowsAuto-check passed
Orca Orchestration
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
87k GitHub stars~916 tokensUpdated today
Agent WorkflowsAuto-check passed
Agent Orchestrator Task
ruvnet/ruflo
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
74k GitHub starsUsed in 3 repos~1k tokens
Agent WorkflowsAuto-check passed
Plan Orchestrate
affaan-m/ECC
Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts.
275k GitHub starsUsed in 1 repo~4.5k tokens
Agent WorkflowsAuto-check passed
Orchestrate
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
47k GitHub starsUsed in 1 repo~692 tokens
Agent WorkflowsAuto-check passed
Swarm Orchestration
ruvnet/ruflo
Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.
74k GitHub starsUsed in 2 repos~779 tokens
Agent WorkflowsAuto-check passed

Questions about Orchestrate Project

What does Orchestrate Project do?

Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Orchestrate Project is an agent skill from danielvm-git/bigpowers. Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates.

When should I use Orchestrate Project?

Orchestrate Project fits situations like: coordinate multi-phase projects with guaranteed quality checkpoints.

How do I install Orchestrate Project in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill orchestrate-project -a claude-code`. Or copy the skill folder (skills/orchestrate-project in danielvm-git/bigpowers) into .claude/skills/orchestrate-project in your project. Claude Code loads it when a task matches its description.

How do I install Orchestrate Project in Codex?

Run `npx skills add danielvm-git/bigpowers --skill orchestrate-project -a codex`. Or copy the skill folder (skills/orchestrate-project in danielvm-git/bigpowers) into .agents/skills/orchestrate-project in your project. Codex loads it when a task matches its description.

Can I use Orchestrate Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill orchestrate-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrate-project, .gemini/skills/orchestrate-project, .github/skills/orchestrate-project and .opencode/skills/orchestrate-project in your project.

What does Orchestrate Project need to run?

Going by SKILL.md and its folder, Orchestrate Project needs the command-line tools its instructions call (claude and bash).

Does Orchestrate Project access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Orchestrate Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Orchestrate Project use?

Orchestrate Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Orchestrate Project use?

About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Orchestrate Project?

Skills that share tags, products or a category with Orchestrate Project: Team Agent Orchestration (affaan-m/ECC, 275k stars), Orca Orchestration (stablyai/orca, 87k stars), Agent Orchestrator Task (ruvnet/ruflo, 74k stars) and Plan Orchestrate (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Orchestrate Project?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 257 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Orchestrate Project

Install Orchestrate Project

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Orchestrate

Quick Start

The 6-Phase Core Loop

Checkpoint / resume

How Orchestrate Works

Orchestration Modes

Verification

Files

Compare with similar skills

Similar skills

Team Agent Orchestration

Orca Orchestration

Agent Orchestrator Task

Plan Orchestrate

Orchestrate

Swarm Orchestration

More from danielvm-git/bigpowers

Extract Design

Align Grid

Assess Impact

Audit Code

Audit Plan

Compose Workflow

Questions about Orchestrate Project