A command for changing a project's specifications or work plan after new information or changing requirements are discovered. It also checks whether other workers are currently executing the plan.

Use it to revise requirements, tasks, or both for an active Conductor track, including changes during parallel execution.

It records changes in one place and highlights the risk of altering work that other agents may already be doing.

How NguyenSiTrung/Conductor-Beads configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/NguyenSiTrung/Conductor-Beads/main/.claude/skills/conductor/references/commands/revise.md

Clone the repo

git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/revise/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/revise)

Your own site

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/revise"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/revise/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/revise"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/revise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,442 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 95% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01442
Opus 5	$0.00000	$0.00721
Sonnet 5	$0.00000	$0.00288
Haiku 4.5	$0.00000	$0.00144

Measured 10d ago against content hash d83d67e41611, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

revise 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 10d 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.

Origin

This is a copy

95% identical to conductor-revise — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/conductor/references/commands/revise.md · 156 lines

How it starts

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

Conductor Revise

Update specifications and plans when implementation reveals issues, requirements change, or scope adjustments are needed.

1. Identify Track

Find active track (marked [~] in tracks.md)
If no active track, ask which track to revise
Check for parallel_state.json (parallel execution in progress)

1a. Parallel Execution Check

If parallel_state.json exists:

"⚠️ This track has parallel workers currently running." "Revising the plan may affect in-progress workers."

"A) Wait for workers to complete, then revise" "B) Revise now (affected workers may need restart)" "C) Cancel revision"

If A: Monitor until complete, then proceed
If B: Note affected tasks in revision, workers operating on changed tasks should abort
If C: HALT

2. Determine Revision Type

Ask what needs revision:

Spec - Requirements changed or misunderstood
Plan - Tasks need to be added, removed, or modified
Both - Significant scope change

3. Gather Context

Ask targeted questions about what was discovered and what needs to change.

4. Create Revision Record

Append to conductor/tracks/<track_id>/revisions.md:

Revision number, date, type
What triggered the revision
Current phase/task when revision occurred
Changes made (spec and/or plan)
Rationale and impact

5. Update Documents

Update spec.md and/or plan.md as needed
Add "Last Revised" marker at top of updated files
New tasks: [ ], Removed tasks: [-] [REMOVED: reason]
Phase-level parallel changes:
- Add/modify  annotations for phase dependencies
- Add/modify  for specific phase dependencies
- If removing a phase that others depend on, update dependent phases
Task-level parallel changes:
- Update  and  annotations
- If parallel phase removed: Mark for sequential execution or update annotations

6. Commit

git add conductor/tracks/<track_id>/
git commit -m "conductor(revise): Update spec/plan for <track_id>"

Read the full file on GitHub · 156 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.

10d ago First seen · 156 lines · 0 tokens per session scan A d83d67e41611

Subscribe to this mod's changes

revise is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,442 tokens. A static security scan graded it A with 0 findings. It is 95% identical to conductor-revise, differing in 4 lines, and is treated as a copy.

Planning

Conductor-Beads: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Conductor Revise

1. Identify Track

1a. Parallel Execution Check

2. Determine Revision Type

3. Gather Context

4. Create Revision Record

5. Update Documents

6. Commit

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement