rdocx: Command for Claude Code

.claude/commands/complete-feature.md

complete-feature is a command for Claude Code from tensorbee/rdocx. It costs 19 tokens per session (2,468 once invoked), scanned A, original, MIT.

A feature-completion command that checks the implementation, tests, review results, and design plan, then updates the project trackers and high-level design documents in one commit. In prepare mode it creates a handoff for later integration instead.

In plain words
What is it for?
Use it to complete an in-progress F-ID on a sprint branch, or to prepare a worker branch for integration into the sprint branch.
Why use it?
It keeps the code, status records, and design documentation consistent at the moment a feature is closed. It also verifies that the named test really protects the feature rather than passing accidentally.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

This is tensorbee/rdocx's own configuration. It tells Claude Code how to work on rdocx itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rdocx configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/sprint_workflow.py validate-handoff \.

Reuse

Borrowing it

Nothing to install: this file belongs to tensorbee/rdocx. 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/tensorbee/rdocx/main/.claude/commands/complete-feature.md
Clone the repo
git clone --depth 1 https://github.com/tensorbee/rdocx

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.

agentmods badge for complete-feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/tensorbee/rdocx/complete-feature/github.svg)](https://agentmods.dev/commands/tensorbee/rdocx/complete-feature)
Your own site
<a href="https://agentmods.dev/commands/tensorbee/rdocx/complete-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/complete-feature/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.

agentmods 80×15 button for complete-feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/tensorbee/rdocx/complete-feature"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/complete-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,468 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.02468
Opus 5.5 $0.00008 $0.00987
Sonnet 5.5 $0.00004 $0.00494
Haiku 4.5 $0.00002 $0.00247

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

Security

Grade A, and why

complete-feature 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 6d 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.

.claude/commands/complete-feature.md · 232 lines

How it starts

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

/complete-feature F-XXX [--prepare]

Close out an F-ID. Every tracker is updated in one commit so the delivery record cannot drift from the code.

--prepare is the parallel-work variant a worker runs in its own worktree. It stops short of the sprint ledgers and writes a handoff instead. See "Prepare mode" below.

Steps

  1. Check the preconditions.

    • The F-ID is in-progress.
    • .claude/plans/F-XXX-design.md exists and every local implementation item is ticked. Final sprint items may remain explicitly pending as below.
    • The latest .claude/reviews/F-XXX-* pass reports zero defects and zero smells.
    • Actual /verify --scoped F-XXX local evidence and clean microscope apply to the final feature source. Consume these observations, do not rerun them. Named final sprint checks remain due at the integrated gate.

    If any fails, say which and stop. Before normal completion steps4 onward, require actual final checks to have passed, except the narrow approved local provider-prefix checkpoint below. Otherwise prepare only the explicit final sprint acceptance checkpoint, without delivery completion.

  2. Confirm the test gate evidence is real. Read the retained named local old-source RED and fixed-source GREEN observations. Run only a missing or invalidated check. Do not repeat a passing test just because this command was invoked. A gate that passes against unmodified code is not a gate.

  3. Confirm the HLD is current. Its exact approved impact files must already be included in implementation and review. Do not edit source intent after final verification. An unlisted contradiction requires a plan revision.

  4. Append to docs/sprints/AS_BUILT.md using the template in that file. The **Hash harness** field is mandatory for M1 through M6, recording either "unchanged" or the delta and its justification.

  5. Append to docs/sprints/SPRINT_TRACKER.md: one row with the estimate and the actual.

Read the full file on GitHub · 232 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. 6d ago Changed · +12 lines a68492af4d94
  2. 11d ago Changed · +39 lines eeef66d34e73
  3. 14d ago Changed · +26 lines 6b404f81853c
  4. 26d ago First seen · 155 lines · 19 tokens per session scan A f2e03b74256c

Subscribe to this mod's changes

complete-feature is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 2,468 once invoked, about $0.0001 per session on Opus 5.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-10-04.