review-spec
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Independently review one verified CCL-backed Spec candidate against its frozen deterministic contract; persist stable structured findings and route exact finding remediation without creating new semantics.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- fclabs/skillstheir own version, first seen Nov 12, 2026
- 0xdeafcafe/skillstheir own version, first seen Nov 6, 2026
- alo-exp/silver-bullettheir own version, first seen Nov 1, 2026
- holgerleichsenring/specification-first-agentic-developmenttheir own version, first seen Oct 28, 2026
- Tngc93/product-management-skillstheir own version, first seen Oct 20, 2026
- swm8023/skillstheir own version, first seen Oct 14, 2026
Used with
Projects with it also use create-spec.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
srobinsonSkillcreate-spec
Create a task specification (SPEC.md) through interactive requirements elicitation. Use when helping users define what they want to build before autonomous execution begins.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- warpdotdev/oz-for-oss★ 313same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- tranhieutt/software_development_department★ 71same name
- holgerleichsenring/specification-first-agentic-development★ 41same name
- Codagent-AI/agent-skills★ 31same name
- alo-exp/silver-bullet★ 7same name
- sergeyklay/.agents★ 6same name
- dekoza/oh-my-slop★ 4same name
- NitinJ/specforge★ 4same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-remediationSkill
- attentionSkill
- classify-docSkill
- codebase-designSkill
- codebase-memory-mcpSkill
- codegraphSkill
- coding-standardsSkill
- contract-ledgerSkill
- conventional-commitsSkill
- database-migrationsSkill
- deduplicate-codeSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- format-codeSkill
- github-issue-dependenciesSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implement-ticketSkill
- improve-codebase-architectureSkill
- project-delivery-managementSkill
- project-trackingSkill
- prototypeSkill
- repowiseSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-architectureSkill
- setup-matt-pocock-skillsSkill
- spec-contractSkill
- spec-merge-cleanupSkill
- tddSkill
- teachSkill
- to-adr-docSkill
- to-docSkill
- to-specsSkill
- to-ticketsSkill
- triageSkill
- verify-architectureSkill
- verify-codeSkill
- verify-spec-closureSkill
- verify-specSkill
- verify-ticket-closureSkill
- verify-ticket-decompositionSkill
- wayfinderSkill
- wiki-lintSkill
- wiki-syncSkill
- wiki-synthesizeSkill
- writing-great-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 20 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Do not reinterpret the defect locally.
- Very specific: line 122
If current architecture authority proves material behavior absent from CCL/OBL, classify contract-authority-gap.
- Distinctive: line 127
After Reviewer A has produced a complete draft coverage artifact and draft finding set, dispatch a second fresh reviewer as the coverage …
- Distinctive: line 226
After Reviewer B and after every coverage reconciliation, run:
- Distinctive: line 246
Do not manually construct these lines.
- Distinctive: line 260
Read it back exactly, re-extract JSON, rerun the validator against the same current Spec contract, and require the same Review Coverage …
- Very specific: line 352
Read the comment back exactly and rerun review_findings.py validate against the read-back final ledger, read-back coverage artifact, and …
- Distinctive: line 358
Every current finding has exactly:
- Distinctive: line 410
Do not claim a target family, error branch, owner path, or test surface is uncovered until Reviewer B has checked the recovered test …
- Distinctive: line 450
Before persisting or consuming the ledger, extract JSON and run:
- Distinctive: line 474
if an affected cell hash changes, the old finding is stale until explicitly reconciled.
- Distinctive: line 476
if evidence shows a draft finding was materially over-scoped or false, correct/reject it before persistence rather than preserving bad …
- Very specific: line 514
Only after both reviewers, coverage validation, final finding adjudication, and coverage↔finding validation complete, invoke $attention …
- Distinctive: line 566
Do not self-report/reconstruct machine-owned counts or hashes.
- Very specific: line 600
When remediation-owned Blocking findings remain and all review correctness gates are valid, the owning lifecycle destination is $to-tickets.
- Very specific: line 606
If review coverage, finding adjudication, or coverage↔finding linkage is incomplete/invalid, do not emit a remediation handoff.
- Distinctive: line 637
Before receipt persistence re-read candidate, verification receipt, deterministic contract, v2 ticket coverage, final finding ledger, …
- Distinctive: line 643
Before any terminal PASS or FAIL Human Handoff:
- Distinctive: line 646
read all three back and rerun their validators.
- Distinctive: line 652
read the Session Ledger back and require that it matches the final review frontier.
- Very specific: line 654
If Session Ledger reconciliation/readback fails, do not emit a terminal Human Handoff.
- Distinctive: line 689
Do not invoke cleanup or remediation implicitly.
- Distinctive: line 697
create Root Blockers for current remediation.
- Distinctive: line 701
treat Project fields as review authority.
- Distinctive: line 702
use review-coverage surfaces or probes as a second semantic contract.
- Distinctive: line 703
treat a structurally valid coverage row as proof that a finding's evidence is true.
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Spec
$review-spec is the final independent adversarial review of the exact candidate already
passed by $verify-spec.
Review independence is about finding implementation, standards, integration, proof, and architecture-realization defects that verification missed. It is not authority to reinterpret planning prose, create a new contract cell, or broaden CCL.
The review contract is the exact deterministic Spec cell universe:
OBL-* -> exact CCL assertions
IMP-* -> private/mechanical planning
TEST-* -> proof/test planning
EXC-* -> exclusions1. Bind the exact verified candidate
Recover from durable state:
- parent Spec and governance mode;
- fixed baseline, branch, exact current
HEAD; - latest passing
## Spec Verification Receipt; - receipt-bound
SPEC_BODY_HASHandSPEC_CONTRACT_HASH; - deterministic current
$spec-contract; - current
ticket-coverage-manifest:v2; - implementation ticket/closure evidence;
- exactly one conventional
Spec Review: ...issue, creating it if absent; - current review finding ledger, if present;
- current review coverage receipt, if present;
- current review finding-adjudication receipt, if present;
- current Session Ledger continuation record.
Require the current candidate to match the passing verification receipt, except for a
proven policy-only synchronization allowed by AGENTS.md.
Rebuild the deterministic Spec contract and v2 coverage. If projection/coverage is stale:
cell-routing-defect -> $to-tickets
contract/planning gap -> $to-specs / semantic owner
malformed CCL projection -> $to-specsDo not reinterpret the defect locally.
2. Conventional Spec Review issue
The one review issue contains:
**Parent Spec:** #<spec>It owns:
- one active structured Review Finding Continuity Ledger;
- one active candidate-bound Review Coverage Receipt;
- one active Review Finding Adjudication Receipt;
- Review Remediation Ticket lineage;
- the final Spec Review Exit Receipt.
The parent Spec continues to own Workspace Metadata, Spec Verification Receipts, and Ticket Coverage Manifest v2.
3. Two fresh reviewers, complementary duties
Dispatch exactly two fresh non-mutating reviewers for the exact candidate, sequentially. They receive the exact frozen Spec cells/CCL addresses and may independently derive falsifiers and evidence, but may not add/remove/redefine contract cells.
Reviewer A — contract-cell adversarial sweep
Execute sequentially:
- Standards, when applicable;
- Spec, always;
- Architecture, when applicable.
Reviewer A must inspect the complete frozen contract even after discovering a Blocking finding. A Blocking finding does not terminate the sweep, reduce the remaining cell universe, or authorize an early remediation handoff.
For every contract cell, Reviewer A must produce the candidate-bound coverage row defined in Section 3A. The row must inventory concrete implementation/proof/authority/composition surfaces and record adversarial probes for the required review lenses.
Reviewer A also produces a draft finding set. Draft findings are not lifecycle authority and must not be persisted as the active v2 finding ledger until Reviewer B adjudicates them.
Standards
Review current applicable repository engineering/coding/testing/workflow standards that govern the changed implementation surfaces.
Standards findings must cite the exact governing standard. Standards may constrain implementation quality; they do not create new product/domain semantics.
Spec
Challenge whether the integrated candidate satisfies every frozen cell, including production composition, negative behavior, and test adequacy.
A current in-contract defect is Blocking even when verification previously passed.
Architecture
Challenge whether implementation structure realizes exact CCL semantics and current architecture constraints that are implementation consequences of those contracts.
ADR/wiki rationale may explain why. It may not strengthen CCL.
If current architecture authority proves material behavior absent from CCL/OBL, classify
contract-authority-gap; do not invent a review-owned obligation.
Reviewer B — coverage and finding challenger
After Reviewer A has produced a complete draft coverage artifact and draft finding set, dispatch a second fresh reviewer as the coverage challenger and finding adjudicator.
Reviewer B does not merely repeat Reviewer A. It must challenge both:
- whether coverage omitted a materially distinct implementation, proof, lifecycle, commit-boundary, read/write, sibling, or composition surface implicated by a frozen cell; and
- whether every draft finding is factually supported, correctly scoped to the exact affected cells, and expressed by a falsifier no broader than current contract authority.
Reviewer B receives:
- exact candidate and Spec contract;
- implementation ticket/closure evidence already recovered by the workflow;
- Reviewer A's complete draft coverage artifact;
- prior active v2 finding ledger for continuity;
- Reviewer A's draft finding set.
For every OBL-*, Reviewer B must test whether broad/cross-cutting behavior was collapsed
into one superficial probe when materially independent paths exist.
For every TEST-*, Reviewer B must challenge whether proof exercises the authoritative
claim and materially relevant negative behavior rather than merely the implemented happy
path.
For every draft finding Reviewer B must:
- re-open every concrete cited code/test evidence locator rather than trusting Reviewer A's summary;
- compare the evidence claim against what the cited source actually demonstrates;
- challenge every proposed affected cell and identify any governing affected cell omitted from the draft;
- challenge whether any named behavior/path/family is already proved by another cited or recovered test;
- challenge the frozen falsifier for overbreadth, invented semantics, and false negatives.
The disposition for each draft finding is exactly one of:
confirmed
corrected
rejectedcorrected means reconcile the draft finding before persistence: preserve RF identity only
when continuity rules permit it, correct evidence/falsifier/cells, then adjudicate the final
row again. rejected means the draft must not enter the final finding ledger or coverage
finding links.
The final persisted ledger may contain only rows that Reviewer B has independently
confirmed after all corrections. A reviewer may not persist a row while its evidence or
affected-cell scope remains disputed.
Reviewer B must complete its challenge across the entire contract even when it finds an omission, incorrect finding, or product defect. There is no early handoff on the first problem.
3A. Machine-validated review completeness
Reviewer completeness is represented by exactly one JSON artifact with schema:
polaris.review-coverage/v1The top-level artifact binds:
schema
spec_contract_hash
reviewed_head
cellsIt contains exactly one row for every current Spec contract cell, in canonical Spec-contract
order. Each row binds exact cell, cell_hash, and kind, then records:
surfaces— concrete reviewed production/proof/composition/authority surfaces, each with stable row-localsurface_id, role, and evidence locator;lenses— complete required review-lens set for that cell kind, each explicitlycoveredornot-applicable; not-applicable requires concrete rationale;probes— concrete adversarial falsifier/evidence rows tied to one covered lens and one or more declared surfaces, with any resultingRF-*identities.
Required lenses are machine-owned by
.agents/skills/review-spec/scripts/review_coverage.py:
material-contract -> positive, negative, composition, proof
implementation -> implementation, composition, proof
testing -> proof, negative
exclusion -> exclusionA reviewer may mark a lens not-applicable only with explicit rationale. It may not
silently omit the lens. Every covered lens requires at least one adversarial probe, and
every declared surface must be exercised by at least one probe.
After Reviewer B and after every coverage reconciliation, run:
python .agents/skills/review-spec/scripts/review_coverage.py validate \
<spec-contract.json> <review-coverage.json>Require exact successful receipt beginning with:
REVIEW COVERAGE: VALID
Reviewed HEAD: <sha>
Spec Contract Hash: <hash>
Contract cells reviewed: <n>/<n>
Unchecked contract cells: 0
Declared review surfaces: <n>
Adversarial probes: <n>
Review Coverage SHA-256: <hash>Do not manually construct these lines. Copy them only from successful current-run validator stdout.
Persist exactly one active coverage comment on the conventional Spec Review issue:
<!-- review-spec-coverage:v1
<exact polaris.review-coverage/v1 JSON>
-->
## Review Coverage Receipt
<exact machine receipt>Read it back exactly, re-extract JSON, rerun the validator against the same current Spec contract, and require the same Review Coverage SHA-256 before Exit or FAIL handoff.
A stale reviewed HEAD, stale Spec Contract Hash, missing/duplicate/reordered cell, stale
cell hash, omitted required lens, covered lens with no probe, or declared surface with no
probe is incomplete review state. Remain in $review-spec.
The coverage artifact proves review-process coverage. It is not a second semantic contract. Its surfaces/probes/rationales cannot create or strengthen CCL.
3B. Machine-validated final finding correctness
Reviewer B's final adjudication is represented by exactly one JSON artifact:
polaris.review-finding-adjudication/v1It binds:
schema
spec_contract_hash
reviewed_head
findingsThere is exactly one adjudication row for every final v2 finding row, in final ledger order. Each row contains:
finding_id
finding_sha256
verdict
evidence_checks
cell_scope_checks
falsifier_checkThe final verdict is always confirmed. Draft corrected and rejected states are
resolved before final validation.
For each final finding:
finding_sha256binds the exact canonical final v2 finding row;evidence_checksrecords every concrete code/test locator cited in final finding evidence, the exact claim made about that locator, what Reviewer B observed there, and resultsupports;cell_scope_checkscovers every affected cell/hash in the final row and explains why the defect/proof gap actually affects that exact cell;falsifier_checkexplains why the final falsifier is current, concrete, and no broader than the frozen contract.
The final coverage and final finding ledger must agree bidirectionally. For every RF-*,
the exact set of cells whose coverage probes cite that RF must equal the exact affected-cell
set in the final ledger. Unknown RF references, missing RF links, or extra RF/cell links
fail closed.
Run:
python .agents/skills/review-spec/scripts/review_findings.py validate \
<spec-contract.json> \
<review-coverage.json> \
<review-findings.json> \
<review-adjudication.json>Require exact success beginning with:
REVIEW FINDINGS: VALID
Reviewed HEAD: <sha>
Spec Contract Hash: <hash>
Final findings adjudicated: <n>/<n>
Coverage/finding cell links: VALID
Unchecked cited code evidence locators: 0A final finding is not durable review authority until this validator passes.
Persist exactly one active adjudication comment on the conventional Spec Review issue:
<!-- review-spec-finding-adjudication:v1
<exact polaris.review-finding-adjudication/v1 JSON>
-->
## Review Finding Adjudication Receipt
<exact machine receipt>Read the comment back exactly and rerun review_findings.py validate against the read-back
final ledger, read-back coverage artifact, and same Spec contract. Require the same Finding
Adjudication SHA-256 before Exit or FAIL handoff.
4. Finding model
Every current finding has exactly:
Finding ID: RF-<stable n>
Axis: Standards | Spec | Architecture
Severity: Blocking | Advisory
Classification:
implementation-defect
standards-defect
test/proof-defect
cell-routing-defect
contract-authority-gap
planning-cell-gap
Cells: <exact current cells + hashes | empty when legitimately standards-only>
Standard refs: <exact standards authority | empty>
Falsifier: <concrete state making the finding true>
Evidence: <concrete current evidence>
Owner: <workflow owner>
Status: open | resolved | owner-overridden | scope-retiredRouting:
implementation-defect
standards-defect
test/proof-defect
-> Review Remediation Ticket path through $to-tickets
cell-routing-defect
-> $to-tickets on current decomposition owner
contract-authority-gap
planning-cell-gap
-> $to-specs / semantic owner
genuine new material semantic choice
-> $contract-ledger / governing $wayfinder as applicableAdvisory findings do not become remediation tickets unless explicitly promoted through current authority.
A finding may cite only cells actually affected by its frozen falsifier. A nearby cell, shared implementation surface, or same domain is not sufficient.
For a test/proof-defect, distinguish carefully:
- product behavior absent/broken -> implementation defect;
- frozen proof requirement not demonstrated -> test/proof defect;
- proof exists elsewhere in the candidate -> no proof finding for that behavior.
Do not claim a target family, error branch, owner path, or test surface is uncovered until Reviewer B has checked the recovered test inventory for that exact behavior.
5. Structured finding continuity ledger v2
Maintain exactly one active review-ledger comment whose canonical v2 JSON payload is the only current finding/remediation state:
<!-- review-spec-finding-ledger:v2
{
"schema": "polaris.review-findings/v2",
"spec": "#<spec>",
"spec_contract_hash": "<hash>",
"findings": [
{
"finding_id": "RF-1",
"axis": "Spec",
"severity": "Blocking",
"classification": "implementation-defect",
"cells": [
{"cell": "OBL-001", "cell_hash": "<hash>"}
],
"standard_refs": [],
"falsifier": "<exact frozen falsifier>",
"evidence": "<current evidence>",
"owner": "$to-tickets",
"status": "open"
}
]
}
-->
## Review Finding Continuity Ledger
<deterministic human-readable projection>The JSON payload is authoritative finding/remediation state. The rendered projection is human-readable only.
Before persisting or consuming the ledger, extract JSON and run:
python -m scripts.review_remediation validate-ledger \
<spec-contract.json> <review-findings.json>Require:
REVIEW FINDING LEDGER: VALIDThen require REVIEW FINDINGS: VALID from Section 3B before the final ledger is treated as
review authority.
Continuity rules:
- preserve stable
RF-*identity across re-review when the same finding remains; - reviewer silence never erases an existing open finding;
- candidate mutation alone never resolves a finding;
resolvedrequires current evidence against the exact frozen falsifier;owner-overriddenrequires explicit owner authority;scope-retiredrequires explicit current scope authority;- if an affected cell hash changes, the old finding is stale until explicitly reconciled;
- a remediation-owned finding's
falsifieris frozen while open; - if evidence shows a draft finding was materially over-scoped or false, correct/reject it before persistence rather than preserving bad wording for continuity.
For OBL-*, CCL addresses derive from the exact current Spec cell. Do not duplicate a
second hand-authored semantic statement in the finding.
6. Review remediation contract boundary
Open Blocking findings classified:
implementation-defect
standards-defect
test/proof-defectare the only findings eligible for implementation remediation.
They are not grouped into semantic Root Blockers.
$to-tickets may group several eligible findings into one ticket when that is the smallest
coherent execution slice. The deterministic remediation contract is built from:
current Spec contract
+ exact final v2 finding rows
↓
polaris.review-remediation-contract/v1It contains selected findings/falsifiers, exact affected cells, exact Standards refs, and every other current parent-Spec cell as a preservation guardrail.
Grouping changes execution slicing only. It does not create a new invariant, semantic domain, sibling set, or architecture obligation.
7. Review Attention
Only after both reviewers, coverage validation, final finding adjudication, and
coverage↔finding validation complete, invoke $attention against the exact reviewed
candidate.
Attention is report-only. Any material product concern must enter the same finding model. Any newly exposed coverage omission must reconcile coverage and rerun both validators. Any concern that an RF is factually unsupported or mis-scoped returns to Reviewer B adjudication before persistence/Exit.
8. Human-facing aggregate
Always report:
## Standards
### Blocking
- <findings or None.>
### Advisory
- <findings or None.>
## Spec
### Blocking
- <findings or None.>
### Advisory
- <findings or None.>
## Architecture
### Blocking
- <findings or None.>
### Advisory
- <findings or None.>Then copy exact current-run coverage validator receipt and exact current-run finding adjudication validator receipt, followed by:
Open Blocking findings: <n>
Open remediation-owned findings: <n>
Open cell-routing defects: <n>
Open contract/planning gaps: <n>
Finding continuity unresolved: <n>
Coverage challenger: complete
Finding adjudication: completeDo not self-report/reconstruct machine-owned counts or hashes.
9. Exit Gate
PASS requires:
Verification receipt: current and passed
Deterministic Spec contract: VALID
Ticket coverage v2: VALID
Review finding ledger v2: VALID
Review coverage v1: VALID
Review finding adjudication v1: VALID
Reviewer A: complete
Coverage challenger: complete
Finding adjudication: complete
Unchecked contract cells: 0
Unchecked cited code evidence locators: 0
Coverage/finding cell links: VALID
Open Blocking findings: 0
Open cell-routing defects: 0
Open contract-authority gaps: 0
Open planning-cell gaps: 0
Unaccounted prior findings: 0
Candidate changed during review: noAdvisory findings may remain.
A FAIL result caused by remediation-owned Blocking findings still requires both reviewers, full-contract coverage validation, final-finding adjudication, durable exact readback of coverage/ledger/adjudication, and Attention. Finding a Blocking defect early is not permission to stop reviewing the remaining cells.
When remediation-owned Blocking findings remain and all review correctness gates are
valid, the owning lifecycle destination is $to-tickets.
Cell-routing defects route to $to-tickets on current decomposition owner. Contract or
planning gaps route to $to-specs / semantic owner.
If review coverage, finding adjudication, or coverage↔finding linkage is incomplete/invalid,
do not emit a remediation handoff. The current owner remains $review-spec.
10. Spec Review Exit Receipt
On PASS persist:
## Spec Review Exit Receipt
**Status:** passed
**Spec Review:** #<review issue>
**Reviewed HEAD:** <full SHA>
**Reviewed Baseline:** <full Spec baseline SHA>
**Branch:** spec-<spec>
**Spec Body Hash:** <hash>
**Spec Contract Hash:** <hash>
**Finding Ledger Hash:** <sha256 of exact managed ledger body>
**Review Coverage Hash:** <Review Coverage SHA-256>
**Finding Adjudication Hash:** <Finding Adjudication SHA-256>
**Blocking findings:** 0
**Open blocking findings:** 0
**Unaccounted prior findings:** 0
**Unresolved continuity cells:** 0
**Unresolved decomposition defects:** 0
**Review coverage:** complete
**Coverage challenger:** complete
**Finding adjudication:** complete
**Unchecked coverage cells:** 0Before receipt persistence re-read candidate, verification receipt, deterministic contract, v2 ticket coverage, final finding ledger, managed review-coverage comment, and managed finding-adjudication comment. Any stale identity blocks Exit.
11. Durable terminal reconciliation and Human Handoff
Before any terminal PASS or FAIL Human Handoff:
- persist final finding ledger, coverage receipt, and finding-adjudication receipt;
- read all three back and rerun their validators;
- reconcile the managed ChatGPT Session Ledger continuation record to the final reviewed state;
- increment its generation and record exact semantic candidate, authorized delivery tip when policy sync applies, final RF statuses, Review Coverage SHA-256, Finding Adjudication SHA-256, review comment IDs/URLs, and the next workflow owner;
- read the Session Ledger back and require that it matches the final review frontier.
If Session Ledger reconciliation/readback fails, do not emit a terminal Human Handoff. The
current owner remains $review-spec.
Build one polaris.workflow-handoff/v1 manifest with exactly one handoff and at least these
durability sources:
- final review finding ledger comment;
- final review coverage receipt comment;
- final finding-adjudication receipt comment;
- reconciled Session Ledger comment.
For PASS use outcome: success and destination $spec-merge-cleanup.
For any non-success terminal route use outcome: warning and the destination selected by
the Exit Gate.
Finalize the Human Handoff only through:
python .agents/skills/review-spec/scripts/review_spec_handoff.py finalize \
--manifest <handoff-manifest.json> \
--output <handoff-output.txt>Require exact stdout:
WORKFLOW HANDOFF: VALIDThen emit the contents of <handoff-output.txt> byte-for-byte as the terminal handoff block.
A bare lifecycle invocation such as $to-tickets - ..., $to-specs - ..., or
$spec-merge-cleanup - ... is not a valid $review-spec terminal Human Handoff.
Do not invoke cleanup or remediation implicitly.
Non-goals
$review-spec does not:
- reinterpret Spec prose into contract cells;
- reconstruct architecture obligation universes outside CCL;
- create Root Blockers for current remediation;
- invent semantic requirements during review;
- repair implementation itself;
- mutate CCL;
- treat Project fields as review authority;
- use review-coverage surfaces or probes as a second semantic contract;
- treat a structurally valid coverage row as proof that a finding's evidence is true;
- preserve an incorrect draft finding merely to avoid changing RF wording.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

