Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
Install Conductor Status
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gemini-cli-extensions/conductor conductor-status --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conductor-status .claude/skills/conductor-status && rm -rf skills-srcUse ~/.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/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .claude/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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 install https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-statusType 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.
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gemini-cli-extensions/conductor conductor-status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/conductor-status .agents/skills/conductor-status && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .agents/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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.
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gemini-cli-extensions/conductor conductor-status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/conductor-status .cursor/skills/conductor-status && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .cursor/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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 https://github.com/gemini-cli-extensions/conductor.git --path skills/conductor-status--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gemini-cli-extensions/conductor conductor-status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/conductor-status .gemini/skills/conductor-status && rm -rf skills-srcUse ~/.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/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .gemini/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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.
$ gh skill install gemini-cli-extensions/conductor conductor-statusInstalls 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).
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/conductor-status .github/skills/conductor-status && rm -rf skills-srcUse ~/.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/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .github/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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.
$ npx skills add gemini-cli-extensions/conductor --skill conductor-status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gemini-cli-extensions/conductor conductor-status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gemini-cli-extensions/conductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/conductor-status .opencode/skills/conductor-status && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conductor-status" agent skill from https://github.com/gemini-cli-extensions/conductor/tree/main/skills/conductor-status into .opencode/skills/conductor-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-status", 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
conductor-status- GitHub stars
- 3.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 666 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
- Works in 2 steps: Handshake & Context Initialization → Status Overview Protocol
- Development work in your project
- SKILL.md covers Operational Standards, 1. Handshake & Context… and 2. Status Overview Protocol
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Conductor Status is an agent skill from gemini-cli-extensions/conductor. Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: A plugin for AI coding agents (Antigravity, Claude Code) enabling Spec-Driven Development to specify, plan, and implement software features. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “Use the conductor-status skill to display the current progress of the project by parsing the Tracks Registry and individual track plans”
- “/conductor-status”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6e8f9a8. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Conductor Status loads about 1.3k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 666 words of instructions outside code blocks.
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 gemini-cli-extensions/conductor at commit 6e8f9a8, republished under its Apache-2.0 licence (© gemini-cli-extensions). 666 words, ~1,282 tokens.
Download SKILL.mdSave it as
.claude/skills/conductor-status/SKILL.md (or your agent's skills folder).- name
- conductor-status
- description
- Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
- metadata.version
- 1.0
Conductor Status Skill
You are an AI agent. Your primary function is to provide a status overview of the project by parsing the Tracks Registry and individual track plans.
Operational Standards
- Precise Execution: Do not skip steps. Do not make assumptions about the project state; always verify via the terminal.
- Tool Validation: You MUST validate the success of every tool call. If a command fails, review the error, attempt to self-correct once, or halt and ask for guidance.
- Path Integrity: Always use relative paths starting from the project root (e.g.,
conductor/tracks.md). - Interaction Protocol: When gathering information or asking for decisions, you MUST provide either single-choice or multiple-choice options based on context-aware suggestions. If a specific option is preferred based on project standards or best practices, list it first, prefix it with '(Recommended)', and provide a brief, context-rich explanation of why it is the better choice. You MUST always include a custom or "Other" option to allow user-defined input. Avoid asking raw, open-ended questions without suggestions.
- Sequential Questioning (CRITICAL): When gathering information or asking the user questions, if a native tool is available to present multiple questions for structured answering (e.g., a modal or form tool), you may use it to group questions. However, if you are interacting via standard text chat, you MUST ask questions strictly one at a time and wait for the user's response before proceeding to the next question. Do NOT output multiple questions in a single chat response.
1. Handshake & Context Initialization
Before starting the status overview process, you MUST locate and read the project's foundational context.
Locate Index: Check for the existence of
conductor/index.mdin the project root.- If Missing:
- Announce: "Conductor is not initialized properly. I cannot find the
conductor/index.mdfile." - Ask the user using a Yes/No question if they would like to run the setup process now to initialize Conductor.
- If Approved: Internally invoke the
conductor-setupskill. - If Denied: HALT and await further instructions.
- Announce: "Conductor is not initialized properly. I cannot find the
- If Missing:
Load & Verify Context: Read
conductor/index.mdand use the provided links to locate the core files:- Tracks Registry (
tracks.md) - Product Definition (
product.md) - Tech Stack (
tech-stack.md) - Workflow (
workflow.md) - Health Check: You MUST verify that every linked file actually exists. If ANY of these core files are missing, HALT immediately. Announce which file is missing and ask the user if they would like to run the setup process to repair the environment.
- Tracks Registry (
2. Status Overview Protocol
Follow this sequence to provide a status overview.
Show full SKILL.md (262 more words)Show less
2.1 Read Project Plan
- Locate and Read: Read the content of the Tracks Registry. Check
conductor/index.mdfor the link, otherwise use the Default Path:conductor/tracks.md. - Locate and Read Tracks:
- Parse the Tracks Registry to identify all registered tracks and their paths.
- Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format
- [ ] **Track:or the legacy format## [ ] Track:.
- Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format
- For each track, resolve and read its Implementation Plan. Check the track's
index.mdfor the link, otherwise use the Default Path:conductor/tracks/<track_id>/plan.md.
- Parse the Tracks Registry to identify all registered tracks and their paths.
2.2 Parse and Summarize Plan
- Parse Content:
- Identify major project phases/sections (e.g., top-level markdown headings).
- Identify individual tasks and their current status by looking for checkbox markers:
[x]for completed,[~]for in-progress, and[ ]for pending.
- Generate Summary: Create a concise summary of the project's overall progress. This should include:
- The total number of major phases.
- The total number of tasks.
- The number of tasks completed, in progress, and pending.
2.3 Present Status Overview
- Output Summary: Present the generated summary to the user in a clear, readable format. The status report must include:
- Current Date/Time: The current timestamp.
- Project Status: A high-level summary of progress (e.g., "On Track", "Behind Schedule", "Blocked").
- Current Phase and Task: The specific phase and task currently marked as in progress.
- Next Action Needed: The next task listed as pending.
- Blockers: Any items explicitly marked as blockers in the plan.
- Phases (total): The total number of major phases.
- Tasks (total): The total number of tasks.
- Progress: The overall progress of the plan, presented as tasks_completed/tasks_total (percentage_completed%).
© gemini-cli-extensions, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/conductor-status of gemini-cli-extensions/conductor.
Open the folder on GitHubat commit 6e8f9a8
Compare with similar skills
Conductor Status 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conductor Status this skillgemini-cli-extensions/conductor | 3.8k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from gemini-cli-extensions/conductor
Conductor Setup
gemini-cli-extensions/conductor
Scaffolds the project and sets up the Conductor environment.
Conductor New Track
gemini-cli-extensions/conductor
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
Conductor Implement
gemini-cli-extensions/conductor
Executes the tasks defined in the specified track's plan. An agent skill from gemini-cli-extensions/conductor.
Conductor Review
gemini-cli-extensions/conductor
Reviews the completed track work against guidelines and the plan.
Conductor Revert
gemini-cli-extensions/conductor
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
Related
Categories
Questions about Conductor Status
What does Conductor Status do?
Displays the current progress of the project by parsing the Tracks Registry and individual track plans. Conductor Status is an agent skill from gemini-cli-extensions/conductor. Displays the current progress of the project by parsing the Tracks Registry and individual track plans.
When should I use Conductor Status?
Conductor Status fits situations like: development work in your project.
How do I install Conductor Status in Claude Code?
Run `npx skills add gemini-cli-extensions/conductor --skill conductor-status -a claude-code`. Or copy the skill folder (skills/conductor-status in gemini-cli-extensions/conductor) into .claude/skills/conductor-status in your project. Claude Code loads it when a task matches its description.
How do I install Conductor Status in Codex?
Run `npx skills add gemini-cli-extensions/conductor --skill conductor-status -a codex`. Or copy the skill folder (skills/conductor-status in gemini-cli-extensions/conductor) into .agents/skills/conductor-status in your project. Codex loads it when a task matches its description.
Can I use Conductor Status 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 gemini-cli-extensions/conductor --skill conductor-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conductor-status, .gemini/skills/conductor-status, .github/skills/conductor-status and .opencode/skills/conductor-status in your project.
What does Conductor Status need to run?
SKILL.md names no scripts, command-line tools or credentials: Conductor Status is instructions for the agent only.
Does Conductor Status 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 Conductor Status 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 Conductor Status use?
Conductor Status is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conductor Status use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Conductor Status?
Skills that share tags, products or a category with Conductor Status: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conductor Status?
gemini-cli-extensions (a GitHub organization) maintains it in gemini-cli-extensions/conductor, which has 3,757 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 1, 2026.
Source: gemini-cli-extensions/conductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.