specrew: Command for Claude Code

.specify/extensions/specrew-speckit/commands/speckit.specrew-speckit.sync-feature-closeout.md

speckit.specrew-speckit.sync-feature-closeout is a command for Claude Code from alonf/specrew. It costs 12 tokens per session (603 once invoked), scanned A, a copy of speckit.specrew-speckit.sync-clarify, MIT.

A project-state command that records when a feature reaches its closeout checkpoint after its changes are committed.

In plain words
What is it for?
Use it to mark a completed feature, write its closeout state, and enforce the next approval step.
Why use it?
It preserves the session’s progress and creates the record needed before the workflow can move forward.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

This is alonf/specrew's own configuration. It tells Claude Code how to work on specrew 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 specrew configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alonf/specrew. 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/alonf/specrew/main/.specify/extensions/specrew-speckit/commands/speckit.specrew-speckit.sync-feature-closeout.md
Clone the repo
git clone --depth 1 https://github.com/alonf/specrew

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 speckit.specrew-speckit.sync-feature-closeout

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

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

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00603
Opus 5 $0.00006 $0.00302
Sonnet 5 $0.00002 $0.00121
Haiku 4.5 $0.00001 $0.00060

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

Security

Grade A, and why

speckit.specrew-speckit.sync-feature-closeout 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 5d 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

80% identical to speckit.specrew-speckit.sync-clarify — 22 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.

.specify/extensions/specrew-speckit/commands/speckit.specrew-speckit.sync-feature-closeout.md · 47 lines

How it starts

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

Sync Feature Closeout Boundary State

Record the arrival (before the advancement gate)

After feature-closeout artifacts are committed to the feature branch, record the boundary arrival FIRST — the sync mints the pending crossing and writes .specrew/runtime/pending-verdict-stop.md, the controller truth the verdict stop renders from (DRIFT-198-I011-012: gating before the sync left the stop with no artifact, the marker-invention precondition):

$featureJson = Get-Content -LiteralPath .\.specify\feature.json -Raw -Encoding UTF8 | ConvertFrom-Json
$featureRef = Split-Path -Leaf $featureJson.feature_directory
$iterationsRoot = Join-Path $featureJson.feature_directory 'iterations'
$iterationNumber = if (Test-Path -LiteralPath $iterationsRoot -PathType Container) {
    @(Get-ChildItem -LiteralPath $iterationsRoot -Directory | Sort-Object Name -Descending | Select-Object -First 1)[0].Name
}
pwsh -File .\.specify\extensions\specrew-speckit\scripts\sync-boundary-state.ps1 -ProjectPath . -BoundaryType feature-closeout -FeatureRef $featureRef -IterationNumber $iterationNumber

If the sync fails, stop and report the exact file-write error before continuing. If the sync is refused because an earlier crossing is still unapproved (the ratchet), that refusal IS the stop — surface it and wait for the human; do not work around it.

Advancement gate (after the arrival is recorded)

The gate BLOCKS until the human's verdict authorizes this crossing:

. .\.specify\extensions\specrew-speckit\scripts\shared-governance.ps1
$authorization = Test-SpecrewBoundaryAuthorization -ProjectRoot . -CurrentBoundary 'iteration-closeout' -RequestedBoundary 'feature-closeout'
if (-not $authorization.Authorized) {
  Write-Output (Write-SpecrewBoundaryAuthorizationDirective -CurrentBoundary $authorization.CurrentBoundary -RequestedBoundary $authorization.RequestedBoundary -DirectiveSentinel $authorization.DirectiveSentinel)
  throw $authorization.Reason
}

On a gate block, .specrew/runtime/pending-verdict-stop.md is the controller truth: render the six-section boundary packet from its Boundary to ask for, Human approval phrase, and Marker last line exactly values, then stop for the human's verdict. Do not infer a marker from the phase you are in.

Read the full file on GitHub · 47 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. 5d ago First seen · 47 lines · 12 tokens per session scan A 5e0ecd2c8aa1

Subscribe to this mod's changes

speckit.specrew-speckit.sync-feature-closeout is a command published in the GitHub repository alonf/specrew (54 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 603 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to speckit.specrew-speckit.sync-clarify, differing in 22 lines, and is treated as a copy.