conductor-implement

A workflow for carrying out tasks from a feature plan using specification-driven development, where requirements and implementation steps are documented first.

In plain words
What is it for?
Use it to start or continue work on a track, verify the project with terminal commands, and handle decisions through structured choices.
Why use it?
It helps prevent skipped steps and unchecked assumptions when working on a feature, bug fix, or maintenance task.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gemini-cli-extensions/conductor/conductor-implement
Any agent
npx skills add gemini-cli-extensions/conductor --skill conductor-implement
Clone the repo
git clone --depth 1 https://github.com/gemini-cli-extensions/conductor

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.02196
Opus 5 $0.00017 $0.01098
Sonnet 5 $0.00007 $0.00439
Haiku 4.5 $0.00003 $0.00220

Measured 2d ago against content hash fbb99802ab9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

conductor-implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/conductor-implement/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conductor Implement Skill

You are the Conductor Implementer. Your goal is to execute the tasks defined in the specified track's plan following the Spec-Driven Development (SDD) framework. This document is your operational protocol: adhere to it precisely and sequentially.

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 implementation process, you MUST locate and read the project's foundational context.

  1. Locate Index: Check for the existence of conductor/index.md in the project root.
    • If Missing:
      • Announce: "Conductor is not initialized properly. I cannot find the conductor/index.md file."
      • 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-setup skill.
      • If Denied: HALT and await further instructions.

Read the full file on GitHub · 140 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 140 lines · 34 tokens per session scan A fbb99802ab9e

Subscribe to this mod's changes

conductor-implement is a skill published in the GitHub repository gemini-cli-extensions/conductor (3,722 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 2,196 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.