A change-control command for marking one stage of a development method as needing rework. It also marks later documents as out of date when they depend on that stage.

Use it when requirements, testing analysis, design, implementation planning, test results, walkthroughs, reviews, or release checks must be redone.

It prevents outdated plans, tests, reports, and release checklists from being treated as current after an earlier decision changes.

redo — Command for Claude Code by Lab94/frenchie-skill

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.

Clone the repo

git clone --depth 1 https://github.com/Lab94/frenchie-skill

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/lab94/frenchie-skill/redo/github.svg)](https://agentmods.dev/commands/lab94/frenchie-skill/redo)

Your own site

<a href="https://agentmods.dev/commands/lab94/frenchie-skill/redo"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/redo/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/lab94/frenchie-skill/redo"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/redo.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 911 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00911
Opus 5.5	$0.00000	$0.00364
Sonnet 5.5	$0.00000	$0.00182
Haiku 4.5	$0.00000	$0.00091

Measured 1mo ago against content hash 3aae7e4e70d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

redo 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 1mo 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.

method/commands/redo.md · 50 lines

How it starts

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

/redo

Mark a Method stage as needing rework. Cascades staleness to all downstream artifacts so /method-check and /frenchie-method accurately reflect what is current.

Syntax: /redo <stage>

Aliases: /frenchie-redo.

Stages

Argument	Artifact	Downstream cascade
`requirement`	`01-requirement.md`	`02-acceptance-criteria.md`, `03-test-case.md`, `04-implementation-plan.md`, `05-design.md`, `06-test-report.md`, `09-release-checklist.md`
`qa-analysis`	`03-test-case.md`	`04-implementation-plan.md`, `06-test-report.md`, `09-release-checklist.md`
`design`	`05-design.md`	`04-implementation-plan.md`, `06-test-report.md`, `09-release-checklist.md`
`sa-analysis`	`04-implementation-plan.md`	`06-test-report.md`, `09-release-checklist.md`
`run-test`	`06-test-report.md`	`09-release-checklist.md`
`walkthrough`	`07-walkthrough.md`	`08-review-report.md`, `09-release-checklist.md`
`pr-review`	`08-review-report.md`	`09-release-checklist.md`
`release-check`	`09-release-checklist.md`	(none)

security-review and task-plan do not produce a single canonical artifact — /redo does not accept them as direct stages. To redo security analysis, redo the upstream stage (requirement or sa-analysis) and re-invoke /security-review.

If /redo design changes user-facing affordances (button labels, control visibility, flow ordering), also /redo qa-analysis afterward. The cascade table does not auto-invalidate qa-analysis on design because most design redos are visual (color, spacing, typography) and do not affect Gherkin scenarios — but the moment a label or control changes, scenarios like "Then the user clicks Save" become stale and the test cases need a refresh. The chain is manual to keep the common case (visual tweaks) cheap.

Behavior

Resolve the active feature using the rules in skills/core/state-check.md.
Look up the artifact for <stage> in the active feature's state.
Mark that artifact's status as stale (or draft if no body has been written).
Cascade: for every downstream artifact in the table above, if it currently has status: ready, downgrade it to stale. Artifacts already missing or draft stay as they are.

Append to state.json.decisions[]:

{ "at": "<ISO>", "decision": "redo-<stage>", "reason": "<user reason if given>" }

Update state.json.lastModifiedAt (current ISO) and lastModifiedBy (current agent identifier).
Recommend the next command — typically the slash command that produces the artifact for <stage> (e.g. /redo design recommends /design). The user is responsible for invoking it.

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

1mo ago First seen · 50 lines · 0 tokens per session scan A 3aae7e4e70d6

Subscribe to this mod's changes

redo is a command published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 911 tokens. 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-31.

Planning

redo

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/redo

Stages

Behavior

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

speckit.bug.fix

speckit.bug.test