Agent

Code review phase 7

Prompt:
Code review for Phase 7 (workflow-smoke-convention-locks). Phase contains 4 ADRs + 4 lint/check scripts + package.json wiring + LOCAL-DEPLOY.md MANDATORY section + LDtk smoke artifacts. Mostly docs + tooling, minimal production code.

Phase dir: `.planning/phases/07-workflow-smoke-convention-locks/`
Phase number: 07

Source files changed in this phase:
- docs/adr/0009-ldtk-gridsize-convention.md
- docs/adr/0010-ldtk-tileset-source-hash.md
- docs/adr/0011-bncentral-gridvania-chunking.md
- docs/adr/0012-ldtk-version-pin.md
- tools/ldtk-version.txt
- traceable-reqs.toml (REQ-HYG-02 required_stages tighten)
- tools/scripts/lint-no-req-placeholders.mjs (new)
- tools/scripts/lint-atlas-hash.mjs (new — Phase 7 stub, activates Phase 8)
- tools/scripts/check-conversion-regression.mjs (new — Phase 7 stub, activates Phase 9)
- tooling/no-inline-origin.ts (added [impl->REQ-HYG-01] tag, no behavioral change)
- package.json (preflight chain + 4 per-ADR lint scripts + lint:no-req-placeholders + lint:atlas-hash)
- docs/deploy/LOCAL-DEPLOY.md (Preflight gate (MANDATORY) section added)
- .gitignore (maps/_smoke/*.ldtk Phase 7 block)
- .planning/phases/07-workflow-smoke-convention-locks/SMOKE-NOTES.md (operator UAT)
- .planning/phases/07-workflow-smoke-convention-locks/smoke-screenshot.png

Focus on:
1. The 3 new .mjs scripts (security: shell injection, path traversal, error handling)
2. package.json preflight chain (correctness of `&&` chain, shell-quoting on Windows)
3. ADR consistency cross-references (e.g. 0011 references 0009 correctly)
4. The lint-no-req-placeholders.mjs allowlist — could it be bypassed by renaming files?

Write REVIEW.md to phase dir. Non-blocking review — flag findings, do not block.


Failed to run: Plugin directory does not exist: C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.10 (spt@cplugs — run /plugin to reinstall)


Async agent launched successfully.
agentId: aee239627221eb683 (internal ID - do not mention to user. Use SendMessage with to: 'aee239627221eb683' to continue this agent.)
The agent is working in the background. You will be notified automatically when it completes.
Do not duplicate this agent's work — avoid working with the same files or topics it is using. Work on non-overlapping tasks, or briefly tell the user what you launched and end your response.
output_file: C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-rebno\f861f8f8-d0e8-43fc-89f5-878315496d8a\tasks\aee239627221eb683.output
Do NOT Read or tail this file via the shell tool — it is the full sub-agent JSONL transcript and reading it will overflow your context. If the user asks for progress, say the agent is still running; you'll get a completion notification.

Code review phase 7

Prompt:
Code review for Phase 7 (workflow-smoke-convention-locks). Phase contains 4 ADRs + 4 lint/check scripts + package.json wiring + LOCAL-DEPLOY.md MANDATORY section + LDtk smoke artifacts. Mostly docs + tooling, minimal production code.

Phase dir: `.planning/phases/07-workflow-smoke-convention-locks/`
Phase number: 07

Source files changed in this phase:
- docs/adr/0009-ldtk-gridsize-convention.md
- docs/adr/0010-ldtk-tileset-source-hash.md
- docs/adr/0011-bncentral-gridvania-chunking.md
- docs/adr/0012-ldtk-version-pin.md
- tools/ldtk-version.txt
- traceable-reqs.toml (REQ-HYG-02 required_stages tighten)
- tools/scripts/lint-no-req-placeholders.mjs (new)
- tools/scripts/lint-atlas-hash.mjs (new — Phase 7 stub, activates Phase 8)
- tools/scripts/check-conversion-regression.mjs (new — Phase 7 stub, activates Phase 9)
- tooling/no-inline-origin.ts (added [impl->REQ-HYG-01] tag, no behavioral change)
- package.json (preflight chain + 4 per-ADR lint scripts + lint:no-req-placeholders + lint:atlas-hash)
- docs/deploy/LOCAL-DEPLOY.md (Preflight gate (MANDATORY) section added)
- .gitignore (maps/_smoke/*.ldtk Phase 7 block)
- .planning/phases/07-workflow-smoke-convention-locks/SMOKE-NOTES.md (operator UAT)
- .planning/phases/07-workflow-smoke-convention-locks/smoke-screenshot.png

Focus on:
1. The 3 new .mjs scripts (security: shell injection, path traversal, error handling)
2. package.json preflight chain (correctness of `&&` chain, shell-quoting on Windows)
3. ADR consistency cross-references (e.g. 0011 references 0009 correctly)
4. The lint-no-req-placeholders.mjs allowlist — could it be bypassed by renaming files?

Write REVIEW.md to phase dir. Non-blocking review — flag findings, do not block.


Code review running in background. While it runs — verify_phase_goal.


Verify phase 7 goal

Prompt:
Verify Phase 07 (workflow-smoke-convention-locks) goal achievement.
Phase directory: `.planning/phases/07-workflow-smoke-convention-locks/`
Phase goal: Lock HARD-gate decisions before any `.ldtk` lands. Author ADRs 0009-0012 (gridSize, tilesetSourceHash, BNCentral GridVania chunking, LDtk version pin); ship 3 lint/check scripts (lint-no-req-placeholders, lint-atlas-hash, check-conversion-regression); wire preflight chain in package.json + document MANDATORY gate in LOCAL-DEPLOY.md; operator smoke test on synth 8000×6400 3×3 GridVania world.
Phase requirement IDs: MAP-02, MAP-15, HYG-01, HYG-02

Check must_haves against actual codebase.
Cross-reference requirement IDs from PLAN frontmatter against REQUIREMENTS.md — every ID MUST be accounted for.
Create VERIFICATION.md.

**Known issue to evaluate, not auto-fail:**
- `pnpm preflight` exits 1 because `pnpm trace:check` reports 209 pre-existing findings (REQ-X / REQ-XX-NN placeholders in archived `.planning/milestones/v1.0-phases/` docs and missing required_stages on v1.0 reqs). HYG-02 scope landed as forward-locking only (lint-no-req-placeholders.mjs blocks NEW placeholders) per Plans 07-05 and 07-06. Retroactive cleanup of archived docs was explicitly NOT in HYG-02 scope. Plan 07-07 acceptance criterion #6 expected preflight to exit 0, but this acceptance was based on a misread of HYG-02 scope. Judge whether this is:
  (a) a phase verification PASS with documented limitation, or
  (b) a gap requiring follow-up plan.

<files_to_read>
- .planning/phases/07-workflow-smoke-convention-locks/*-PLAN.md (8 plans)
- .planning/phases/07-workflow-smoke-convention-locks/*-SUMMARY.md (8 summaries — see 07-08-SUMMARY.md for the operator UAT verdict + watchpoints)
- .planning/phases/07-workflow-smoke-convention-locks/SMOKE-NOTES.md (operator's PASS verdict)
- .planning/phases/07-workflow-smoke-convention-locks/smoke-screenshot.png (LDtk world view)
- .planning/REQUIREMENTS.md (traceability)
- .planning/ROADMAP.md (phase goal + success criteria)
- traceable-reqs.toml (manifest)
- All 4 ADRs in docs/adr/0009..0012-*.md
- tools/ldtk-version.txt
- tools/scripts/lint-no-req-placeholders.mjs
- tools/scripts/lint-atlas-hash.mjs
- tools/scripts/check-conversion-regression.mjs
- tooling/no-inline-origin.ts (HYG-01 tag)
- package.json (preflight chain)
- docs/deploy/LOCAL-DEPLOY.md (MANDATORY section)
</files_to_read>


Async agent launched successfully.
agentId: a318ad3b5c40e4b74 (internal ID - do not mention to user. Use SendMessage with to: 'a318ad3b5c40e4b74' to continue this agent.)
The agent is working in the background. You will be notified automatically when it completes.
Do not duplicate this agent's work — avoid working with the same files or topics it is using. Work on non-overlapping tasks, or briefly tell the user what you launched and end your response.
output_file: C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-rebno\f861f8f8-d0e8-43fc-89f5-878315496d8a\tasks\a318ad3b5c40e4b74.output
Do NOT Read or tail this file via the shell tool — it is the full sub-agent JSONL transcript and reading it will overflow your context. If the user asks for progress, say the agent is still running; you'll get a completion notification.

Verify phase 7 goal

Prompt:
Verify Phase 07 (workflow-smoke-convention-locks) goal achievement.
Phase directory: `.planning/phases/07-workflow-smoke-convention-locks/`
Phase goal: Lock HARD-gate decisions before any `.ldtk` lands. Author ADRs 0009-0012 (gridSize, tilesetSourceHash, BNCentral GridVania chunking, LDtk version pin); ship 3 lint/check scripts (lint-no-req-placeholders, lint-atlas-hash, check-conversion-regression); wire preflight chain in package.json + document MANDATORY gate in LOCAL-DEPLOY.md; operator smoke test on synth 8000×6400 3×3 GridVania world.
Phase requirement IDs: MAP-02, MAP-15, HYG-01, HYG-02

Check must_haves against actual codebase.
Cross-reference requirement IDs from PLAN frontmatter against REQUIREMENTS.md — every ID MUST be accounted for.
Create VERIFICATION.md.

**Known issue to evaluate, not auto-fail:**
- `pnpm preflight` exits 1 because `pnpm trace:check` reports 209 pre-existing findings (REQ-X / REQ-XX-NN placeholders in archived `.planning/milestones/v1.0-phases/` docs and missing required_stages on v1.0 reqs). HYG-02 scope landed as forward-locking only (lint-no-req-placeholders.mjs blocks NEW placeholders) per Plans 07-05 and 07-06. Retroactive cleanup of archived docs was explicitly NOT in HYG-02 scope. Plan 07-07 acceptance criterion #6 expected preflight to exit 0, but this acceptance was based on a misread of HYG-02 scope. Judge whether this is:
  (a) a phase verification PASS with documented limitation, or
  (b) a gap requiring follow-up plan.

<files_to_read>
- .planning/phases/07-workflow-smoke-convention-locks/*-PLAN.md (8 plans)
- .planning/phases/07-workflow-smoke-convention-locks/*-SUMMARY.md (8 summaries — see 07-08-SUMMARY.md for the operator UAT verdict + watchpoints)
- .planning/phases/07-workflow-smoke-convention-locks/SMOKE-NOTES.md (operator's PASS verdict)
- .planning/phases/07-workflow-smoke-convention-locks/smoke-screenshot.png (LDtk world view)
- .planning/REQUIREMENTS.md (traceability)
- .planning/ROADMAP.md (phase goal + success criteria)
- traceable-reqs.toml (manifest)
- All 4 ADRs in docs/adr/0009..0012-*.md
- tools/ldtk-version.txt
- tools/scripts/lint-no-req-placeholders.mjs
- tools/scripts/lint-atlas-hash.mjs
- tools/scripts/check-conversion-regression.mjs
- tooling/no-inline-origin.ts (HYG-01 tag)
- package.json (preflight chain)
- docs/deploy/LOCAL-DEPLOY.md (MANDATORY section)
</files_to_read>


Determine default new level size for Gridvania


Code review + verifier running in background. Awaiting both.


<task-notification>
<task-id>aee239627221eb683</task-id>
<tool-use-id>toolu_0152XBzBG7c2uuJoZCjBRTrM</tool-use-id>
<output-file>C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-rebno\f861f8f8-d0e8-43fc-89f5-878315496d8a\tasks\aee239627221eb683.output</output-file>
<status>completed</status>
<summary>Agent "Code review phase 7" completed</summary>
<result>Phase 7 review complete. REVIEW.md written to `C:\Users\decid\Documents\projects\rebno\.planning\phases\07-workflow-smoke-convention-locks\07-REVIEW.md`.

## Summary

**Status:** issues_found (non-blocking, as requested)
**Findings:** 0 Critical / 5 Warning / 6 Info

**Headline findings:**

- **WR-01 (`lint-atlas-hash.mjs`)** — `.includes('_smoke')` substring-matches rather than path-segment-matches. Production maps like `maps/foo_smoketest.ldtk` would be silently excluded once Phase 8 activates.
- **WR-02 (`lint-no-req-placeholders.mjs` allowlist bypass)** — Answering your specific question: yes, the allowlist is bypassable. It's path-prefix-only, so any new file created under `.planning/milestones/`, `.planning/research/v1.1/`, or the phase 7 dir can quote (or accidentally hold) placeholders without tripping. Renaming a flagged file into one of those prefixes also bypasses. Recommended either tightening to exact-path entries or documenting the prefix-trust posture explicitly.
- **WR-03 (`lint-atlas-hash.mjs` symlink handling)** — `statSync` follows symlinks; a cycle infinite-loops, a broken symlink crashes preflight with no actionable message.
- **WR-04 (`LOCAL-DEPLOY.md` self-contradiction)** — Pre-flight section permits continuing past a failed `pnpm trace:check`; Preflight gate (MANDATORY) section forbids it. Direct contradiction in the same runbook.
- **WR-05 (`check-conversion-regression.mjs`)** — Unconditional exit 0 with no forcing function for Phase 9 activation, unlike `lint-atlas-hash.mjs` which logs noisily when its trigger condition appears.

**No blockers found.** The 3 new `.mjs` scripts have no shell-injection vectors (all `execSync` inputs are hardcoded), no path traversal (constant scope), all ADR cross-references resolve to extant files, and live execution against the current tree confirms each script exits 0. The Phase 7 deliverable is shippable as-is; the warnings are quality/robustness improvements for follow-up.</result>
<usage><total_tokens>80397</total_tokens><tool_uses>30</tool_uses><duration_ms>241860</duration_ms></usage>
</task-notification>


CAVEMAN MODE ACTIVE (full). Drop articles/filler/pleasantries/hedging. Fragments OK. Code/commits/security: write normal.


Code review complete. 0 critical, 5 warnings, 6 info. Non-blocking. Key findings:

- WR-01: `_smoke` substring match in lint-atlas-hash (Phase 8 activation watchpoint)
- WR-02: lint-no-req-placeholders allowlist is path-prefix (bypassable by new files in those prefixes — documented posture, not bug)
- WR-04: LOCAL-DEPLOY.md self-contradiction (Pre-flight section vs Preflight MANDATORY)

Awaiting verifier.


<task-notification>
<task-id>a318ad3b5c40e4b74</task-id>
<tool-use-id>toolu_01MZG9kWkvwCSefFGL1jgH21</tool-use-id>
<output-file>C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-rebno\f861f8f8-d0e8-43fc-89f5-878315496d8a\tasks\a318ad3b5c40e4b74.output</output-file>
<status>completed</status>
<summary>Agent "Verify phase 7 goal" completed</summary>
<result>## Verification Complete

**Status:** gaps_found
**Score:** 4/5 must-haves verified
**Report:** `C:\Users\decid\Documents\projects\rebno\.planning\phases\07-workflow-smoke-convention-locks\07-VERIFICATION.md`

### What Verified

All four ADRs (0009 gridSize=4 unified, 0010 sidecar JSON tilesetSourceHash, 0011 3×3 BNCentral GridVania, 0012 LDtk version pin) exist, lint clean against `lint-adr.mjs --no-matrix`, carry `[doc->REQ-MAP-02]` tags, and absorb their CONTEXT.md decision blocks. `tools/ldtk-version.txt` = `1.5.3`. All three lint/check scripts (`lint-no-req-placeholders.mjs`, `lint-atlas-hash.mjs`, `check-conversion-regression.mjs`) exist and run with correct behavior (one functional, two pre-wired Phase 7 stubs with documented swap targets). `tooling/no-inline-origin.ts` carries the HYG-01 tag. `package.json` preflight chain is composed correctly (7 steps, fail-fast). `docs/deploy/LOCAL-DEPLOY.md` lines 38-52 add the `## Preflight gate (MANDATORY)` section with `[doc->REQ-MAP-15]` tag. Smoke test PASS verdict in `SMOKE-NOTES.md` with the per-chunk lag table matching ADR 0011 dims; screenshot confirms the 3×3 GridVania world view. All 4 phase reqs (MAP-02, MAP-15, HYG-01, HYG-02) report `[OK]` in `pnpm trace:list`.

### Gap (BLOCKER for Plan 07-07 / ROADMAP SC #4)

**Truth #4 FAILED, Truth #2 PARTIAL — single root cause:** HYG-02 shipped as forward-locking only (allowlist permits archived + this-phase planning docs to retain placeholders). 209 `[must]` `undeclared_id` findings remain in `pnpm trace:check`, all confined to `.planning/milestones/v1.0-phases/phases/04-...`, `06.4-...`, etc., and this phase's own planning docs that document the placeholder regex. Cascade: `pnpm preflight` exits 1 at chain step 4 — the new MANDATORY deploy gate is non-actionable as written. Internal contradiction in LOCAL-DEPLOY.md between lines 32-36 (`## Pre-flight`: trace:check has known legacy debt — review and continue) and lines 38-52 (new MANDATORY: preflight MUST exit 0).

ROADMAP SC #4 literal text demands "zero `REQ-SRV-XX` / `REQ-X` placeholder findings across Phase 04 + 06.4 docs". REQUIREMENTS.md line 76 demands placeholders "cleaned from Phase 04 + 06.4 docs". Plan 07-07 acceptance criterion #6 demands `pnpm preflight` exit 0. None of these three are satisfied; the implementation shipped a functional substitute (drift-lock) instead of literal retroactive cleanup.

### Adjudication of the Pre-Flagged Known Issue

I rated this as (b) **gap requiring follow-up plan**, not (a) PASS-with-documented-limitation. Rationale:

1. Three independent contract documents (ROADMAP SC #4, REQUIREMENTS.md HYG-02 text, Plan 07-07 acceptance #6) all demand outcomes that are unmet.
2. The MANDATORY deploy gate in `LOCAL-DEPLOY.md` is unusable as written (operator literally cannot get a green preflight without bypassing trace:check or applying a follow-up).
3. The 07-08 SUMMARY itself flagged this as a deviation requiring phase-verification adjudication.
4. The fix is small and well-scoped (one of three paths surfaced in `human_verification`) — not a heavy plan.

The decision among the three paths (retroactive cleanup vs scan-allowlist extension vs amend-the-contract-to-match-reality) is a scope/policy call the verifier cannot make alone; surfaced under `human_verification` for operator adjudication. This is the Escalation Gate firing as designed.</result>
<usage><total_tokens>127972</total_tokens><tool_uses>52</tool_uses><duration_ms>418115</duration_ms></usage>
</task-notification>


Bash

cd C:/Users/decid/Documents/projects/rebno
grep -E "^(status|score|covered|gaps_count|human_verification_count):" .planning/phases/07-workflow-smoke-convention-locks/07-VERIFICATION.md | head -10
echo "---"
grep -c "^- \[ \]\|^- \[x\]\|^### " .planning/phases/07-workflow-smoke-convention-locks/07-VERIFICATION.md

Verification status block


status: gaps_found
score: 4/5 must-haves verified
---
8


Continue from where you left off.


No response requested.


CAVEMAN MODE ACTIVE — level: full

Respond terse like smart caveman. All technical substance stay. Only fluff die.

## Persistence

ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode".

Default: **full**. Switch: `/caveman lite|full|ultra`.

## Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.

Pattern: `[thing] [action] [reason]. [next step].`

Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"

## Intensity

| Level | What change |
|-------|------------|
| **full** | Drop articles, fragments OK, short synonyms. Classic caveman |

Example — "Why React component re-render?"
- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."

Example — "Explain database connection pooling."
- full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."

## Auto-Clarity

Drop caveman for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume caveman after clear part done.

Example — destructive op:
> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
> ```sql
> DROP TABLE users;
> ```
> Caveman resume. Verify backup exist first.

## Boundaries

Code/commits/PRs: write normal. "stop caveman" or "normal mode": revert. Level persist until changed or session end.


what's next?


- autoplan: Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk
and runs them sequentially with auto-decisions using 6 decision principles. Surfaces
taste decisions (close approaches, borderline scope, codex disagreements) at a final
approval gate. One command, fully reviewed plan out.
Use when asked to "auto review", "autoplan", "run all reviews", "review this plan
automatically", or "make the decisions for me".
Proactively suggest when the user has a plan file and wants to run the full review
gauntlet without answering 15-30 intermediate questions. (gstack)
- benchmark: Performance regression detection using the browse daemon. Establishes
baselines for page load times, Core Web Vitals, and resource sizes.
Compares before/after on every PR. Tracks performance trends over time.
Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals",
"bundle size", "load time". (gstack)
- browse: Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with
elements, verify page state, diff before/after actions, take annotated screenshots, check
responsive layouts, test forms and uploads, handle dialogs, and assert element states.
~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a
user flow, or file a bug with evidence. Use when asked to "open in browser", "test the
site", "take a screenshot", or "dogfood this". (gstack)
- canary: Post-deploy canary monitoring. Watches the live app for console errors,
performance regressions, and page failures using the browse daemon. Takes
periodic screenshots, compares against pre-deploy baselines, and alerts
on anomalies. Use when: "monitor deploy", "canary", "post-deploy check",
"watch production", "verify deploy". (gstack)
- careful: Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE,
force-push, git reset --hard, kubectl delete, and similar destructive operations.
User can override each warning. Use when touching prod, debugging live systems,
or working in a shared environment. Use when asked to "be careful", "safety mode",
"prod mode", or "careful mode". (gstack)
- caveman: Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
- ccs-delegation: Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
- checkpoint: Save and resume working state checkpoints. Captures git state, decisions made,
and remaining work so you can pick up exactly where you left off — even across
Conductor workspace handoffs between branches.
Use when asked to "checkpoint", "save progress", "where was I", "resume",
"what was I working on", or "pick up where I left off".
Proactively suggest when a session is ending, the user is switching context,
or before a long break. (gstack)
- codex: OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via
codex review with pass/fail gate. Challenge: adversarial mode that tries to break
your code. Consult: ask codex anything with session continuity for follow-ups.
The "200 IQ autistic developer" second opinion. Use when asked to "codex review",
"codex challenge", "ask codex", "second opinion", or "consult codex". (gstack)
- connect-chrome: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- cso: Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology,
dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain
scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification.
Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep
scan, 2/10 bar). Trend tracking across audit runs.
Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack)
- design-consultation: Design consultation: understands your product, researches the landscape, proposes a
complete design system (aesthetic, typography, color, layout, spacing, motion), and
generates font+color preview pages. Creates DESIGN.md as your project's design source
of truth. For existing sites, use /plan-design-review to infer the system instead.
Use when asked to "design system", "brand guidelines", or "create DESIGN.md".
Proactively suggest when starting a new project's UI with no existing
design system or DESIGN.md. (gstack)
- design-html: Design finalization: generates production-quality Pretext-native HTML/CSS.
Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review,
design review context from /plan-design-review, or from scratch with a user
description. Text actually reflows, heights are computed, layouts are dynamic.
30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns
for each design type. Use when: "finalize this design", "turn this into HTML",
"build me a page", "implement this design", or after any planning skill.
Proactively suggest when user has approved a design or has a plan ready. (gstack)
- design-review: Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems,
AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues
in source code, committing each fix atomically and re-verifying with before/after
screenshots. For plan-mode design review (before implementation), use /plan-design-review.
Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish".
Proactively suggest when the user mentions visual inconsistencies or
wants to polish the look of a live site. (gstack)
- design-shotgun: Design shotgun: generate multiple AI design variants, open a comparison board,
collect structured feedback, and iterate. Standalone design exploration you can
run anytime. Use when: "explore designs", "show me options", "design variants",
"visual brainstorm", or "I don't like how this looks".
Proactively suggest when the user describes a UI feature but hasn't seen
what it could look like. (gstack)
- devex-review: Live developer experience audit. Uses the browse tool to actually TEST the
developer experience: navigates docs, tries the getting started flow, times
TTHW, screenshots error messages, evaluates CLI help text. Produces a DX
scorecard with evidence. Compares against /plan-devex-review scores if they
exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to
"test the DX", "DX audit", "developer experience test", or "try the
onboarding". Proactively suggest after shipping a developer-facing feature. (gstack)
- diagnose: Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
- document-release: Post-ship documentation update. Reads all project docs, cross-references the
diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped,
polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when
asked to "update the docs", "sync documentation", or "post-ship docs".
Proactively suggest after a PR is merged or code is shipped. (gstack)
- find-skills: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
- freeze: Restrict file edits to a specific directory for the session. Blocks Edit and
Write outside the allowed path. Use when debugging to prevent accidentally
"fixing" unrelated code, or when you want to scope changes to one module.
Use when asked to "freeze", "restrict edits", "only edit this folder",
or "lock down edits". (gstack)
- grill-me: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- grill-with-docs: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- gsd-add-tests: Generate tests for a completed phase based on UAT criteria and implementation
- gsd-ai-integration-phase: Generate an AI-SPEC.md design contract for phases that involve building AI systems.
- gsd-audit-fix: Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
- gsd-audit-milestone: Audit milestone completion against original intent before archiving
- gsd-audit-uat: Cross-phase audit of all outstanding UAT and verification items
- gsd-autonomous: Run all remaining phases autonomously — discuss→plan→execute per phase
- gsd-capture: Capture ideas, tasks, notes, and seeds to their destination
- gsd-cleanup: Archive accumulated phase directories from completed milestones
- gsd-code-review: Review source files changed during a phase for bugs, security issues, and code quality problems
- gsd-complete-milestone: Archive completed milestone and prepare for next version
- gsd-config: Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
- gsd-debug: Systematic debugging with persistent state across context resets
- gsd-discuss-phase: Gather phase context through adaptive questioning before planning.
- gsd-docs-update: Generate or update project documentation verified against the codebase
- gsd-eval-review: Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
- gsd-execute-phase: Execute all plans in a phase with wave-based parallelization
- gsd-explore: Socratic ideation and idea routing — think through ideas before committing to plans
- gsd-extract-learnings: Extract decisions, lessons, patterns, and surprises from completed phase artifacts
- gsd-fast: Execute a trivial task inline — no subagents, no planning overhead
- gsd-forensics: Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
- gsd-graphify: Build, query, and inspect the project knowledge graph in .planning/graphs/
- gsd-health: Diagnose planning directory health and optionally repair issues
- gsd-help: Show available GSD commands and usage guide
- gsd-import: Ingest external plans with conflict detection against project decisions before writing anything.
- gsd-inbox: Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
- gsd-ingest-docs: Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
- gsd-manager: Interactive command center for managing multiple phases from one terminal
- gsd-map-codebase: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
- gsd-milestone-summary: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
- gsd-mvp-phase: Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
- gsd-new-milestone: Start a new milestone cycle — update PROJECT.md and route to requirements
- gsd-new-project: Initialize a new project with deep context gathering and PROJECT.md
- gsd-ns-context: codebase intelligence | map graphify docs learnings
- gsd-ns-ideate: exploration capture | explore sketch spike spec capture
- gsd-ns-manage: config workspace | workstreams thread update ship inbox
- gsd-ns-project: project lifecycle | milestones audits summary
- gsd-ns-review: quality gates | code review debug audit security eval ui
- gsd-ns-workflow: workflow | discuss plan execute verify phase progress
- gsd-pause-work: Create context handoff when pausing work mid-phase
- gsd-phase: CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
- gsd-plan-phase: Create detailed phase plan (PLAN.md) with verification loop
- gsd-plan-review-convergence: Cross-AI plan convergence loop — replan with review feedback until no HIGH concerns remain.
- gsd-pr-branch: Create a clean PR branch by filtering out .planning/ commits — ready for code review
- gsd-profile-user: Generate developer behavioral profile and create Claude-discoverable artifacts
- gsd-progress: Check progress, advance workflow, or dispatch freeform intent — the unified GSD situational command
- gsd-quick: Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
- gsd-resume-work: Resume work from previous session with full context restoration
- gsd-review: Request cross-AI peer review of phase plans from external AI CLIs
- gsd-review-backlog: Review and promote backlog items to active milestone
- gsd-secure-phase: Retroactively verify threat mitigations for a completed phase
- gsd-settings: Configure GSD workflow toggles and model profile
- gsd-ship: Create PR, run review, and prepare for merge after verification passes
- gsd-sketch: Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode)
- gsd-spec-phase: Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
- gsd-spike: Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
- gsd-stats: Display project statistics — phases, plans, requirements, git metrics, and timeline
- gsd-surface: Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
- gsd-thread: Manage persistent context threads for cross-session work
- gsd-ui-phase: Generate UI design contract (UI-SPEC.md) for frontend phases
- gsd-ui-review: Retroactive 6-pillar visual audit of implemented frontend code
- gsd-ultraplan-phase: [BETA] Offload plan phase to Claude Code's ultraplan cloud; review in browser and import back.
- gsd-undo: Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
- gsd-update: Update GSD to latest version with changelog display
- gsd-validate-phase: Retroactively audit and fill Nyquist validation gaps for a completed phase
- gsd-verify-work: Validate built features through conversational UAT
- gsd-workspace: Manage GSD workspaces — create, list, or remove isolated workspace environments
- gsd-workstreams: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
- gstack: Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with
elements, verify state, diff before/after, take annotated screenshots, test responsive
layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or
test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
- gstack-upgrade: Upgrade gstack to the latest version. Detects global vs vendored install,
runs the upgrade, and shows what's new. Use when asked to "upgrade gstack",
"update gstack", or "get latest version".
- guard: Full safety mode: destructive command warnings + directory-scoped edits.
Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with
/freeze (blocks edits outside a specified directory). Use for maximum safety
when touching prod or debugging live systems. Use when asked to "guard mode",
"full safety", "lock it down", or "maximum safety". (gstack)
- handoff: Compact the current conversation into a handoff document for another agent to pick up.
- health: Code quality dashboard. Wraps existing project tools (type checker, linter,
test runner, dead code detector, shell linter), computes a weighted composite
0-10 score, and tracks trends over time. Use when: "health check",
"code quality", "how healthy is the codebase", "run all checks",
"quality score". (gstack)
- improve-codebase-architecture: Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
- investigate: Systematic debugging with root cause investigation. Four phases: investigate,
analyze, hypothesize, implement. Iron Law: no fixes without root cause.
Use when asked to "debug this", "fix this bug", "why is this broken",
"investigate this error", or "root cause analysis".
Proactively invoke this skill (do NOT debug directly) when the user reports
errors, 500 errors, stack traces, unexpected behavior, "it was working
yesterday", or is troubleshooting why something stopped working. (gstack)
- land-and-deploy: Land and deploy workflow. Merges the PR, waits for CI and deploy,
verifies production health via canary checks. Takes over after /ship
creates the PR. Use when: "merge", "land", "deploy", "merge and verify",
"land it", "ship it to production". (gstack)
- learn: Manage project learnings. Review, search, prune, and export what gstack
has learned across sessions. Use when asked to "what have we learned",
"show learnings", "prune stale learnings", or "export learnings".
Proactively suggest when the user asks about past patterns or wonders
"didn't we fix this before?"
- mux-send: Send keystrokes to a psmux terminal session. Use when the user says "send to",
"type in", "send keys to", "mux send", or wants to send input to another terminal
session by name.
- office-hours: YC Office Hours — two modes. Startup mode: six forcing questions that expose
demand reality, status quo, desperate specificity, narrowest wedge, observation,
and future-fit. Builder mode: design thinking brainstorming for side projects,
hackathons, learning, and open source. Saves a design doc.
Use when asked to "brainstorm this", "I have an idea", "help me think through
this", "office hours", or "is this worth building".
Proactively invoke this skill (do NOT answer directly) when the user describes
a new product idea, asks whether something is worth building, wants to think
through design decisions for something that doesn't exist yet, or is exploring
a concept before any code is written.
Use before /plan-ceo-review or /plan-eng-review. (gstack)
- open-gstack-browser: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- pair-agent: Pair a remote AI agent with your browser. One command generates a setup key and
prints instructions the other agent can follow to connect. Works with OpenClaw,
Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent
gets its own tab with scoped access (read+write by default, admin on request).
Use when asked to "pair agent", "connect agent", "share browser", "remote browser",
"let another agent use my browser", or "give browser access". (gstack)
- plan-ceo-review: CEO/founder-mode plan review. Rethink the problem, find the 10-star product,
challenge premises, expand scope when it creates a better product. Four modes:
SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick
expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
Use when asked to "think bigger", "expand scope", "strategy review", "rethink this",
or "is this ambitious enough".
Proactively suggest when the user is questioning scope or ambition of a plan,
or when the plan feels like it could be thinking bigger. (gstack)
- plan-design-review: Designer's eye plan review — interactive, like CEO and Eng review.
Rates each design dimension 0-10, explains what would make it a 10,
then fixes the plan to get there. Works in plan mode. For live site
visual audits, use /design-review. Use when asked to "review the design plan"
or "design critique".
Proactively suggest when the user has a plan with UI/UX components that
should be reviewed before implementation. (gstack)
- plan-devex-review: Interactive developer experience plan review. Explores developer personas,
benchmarks against competitors, designs magical moments, and traces friction
points before scoring. Three modes: DX EXPANSION (competitive advantage),
DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only).
Use when asked to "DX review", "developer experience audit", "devex review",
or "API design review".
Proactively suggest when the user has a plan for developer-facing products
(APIs, CLIs, SDKs, libraries, platforms, docs). (gstack)
- plan-eng-review: Eng manager-mode plan review. Lock in the execution plan — architecture,
data flow, diagrams, edge cases, test coverage, performance. Walks through
issues interactively with opinionated recommendations. Use when asked to
"review the architecture", "engineering review", or "lock in the plan".
Proactively suggest when the user has a plan or design doc and is about to
start coding — to catch architecture issues before implementation. (gstack)
- propose-issue: Challenge an issue statement before fixing it. Probes scope, root cause, and assumptions
through interactive questioning grounded in the codebase. Use when the user says "propose issue",
"challenge this bug", "question this fix", "is this the right problem", or wants to pressure-test
a problem statement before jumping to implementation.
- qa: Systematically QA test a web application and fix bugs found. Runs QA testing,
then iteratively fixes bugs in source code, committing each fix atomically and
re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs",
"test and fix", or "fix what's broken".
Proactively suggest when the user says a feature is ready for testing
or asks "does this work?". Three tiers: Quick (critical/high only),
Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores,
fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack)
- qa-only: Report-only QA testing. Systematically tests a web application and produces a
structured report with health score, screenshots, and repro steps — but never
fixes anything. Use when asked to "just report bugs", "qa report only", or
"test but don't fix". For the full test-fix-verify loop, use /qa instead.
Proactively suggest when the user wants a bug report without any code changes. (gstack)
- retro: Weekly engineering retrospective. Analyzes commit history, work patterns,
and code quality metrics with persistent history and trend tracking.
Team-aware: breaks down per-person contributions with praise and growth areas.
Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
Proactively suggest at the end of a work week or sprint. (gstack)
- review: Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust
boundary violations, conditional side effects, and other structural issues. Use when
asked to "review this PR", "code review", "pre-landing review", or "check my diff".
Proactively suggest when the user is about to merge or land code changes. (gstack)
- screenshot-capture: Capture, process, and analyze screenshots of any running application on Windows 10/11. Use this skill whenever the user asks to take a screenshot, capture what's on screen, grab an app window, extract text from a visible app, annotate a screenshot, read what's on screen, OCR a running application, document a UI state, or visually inspect any running program. Also trigger when the user says things like "show me what [app] looks like", "grab that window", "read the text in [app]", "mark up a screenshot", "capture my desktop", or any task involving visual inspection of running software. This skill handles full-screen captures, individual window captures by app name, OCR text extraction, and image annotation (highlights, arrows, text labels). Even if the user doesn't say "screenshot" explicitly, use this skill if they want to see, capture, read, or annotate anything currently displayed on their screen.
- self-clear: Clear the calling agent's own Claude Code context with /clear, then re-seed it with a user note so it wakes and resumes work after the wipe. Use when the user says "self-clear", "/self-clear", "clear myself", "clear and continue", or "reset my context and keep going".
- setup-browser-cookies: Import cookies from your real Chromium browser into the headless browse session.
Opens an interactive picker UI where you select which cookie domains to import.
Use before QA testing authenticated pages. Use when asked to "import cookies",
"login to the site", or "authenticate the browser". (gstack)
- setup-deploy: Configure deployment settings for /land-and-deploy. Detects your deploy
platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom),
production URL, health check endpoints, and deploy status commands. Writes
the configuration to CLAUDE.md so all future deploys are automatic.
Use when: "setup deploy", "configure deployment", "set up land-and-deploy",
"how do I deploy with gstack", "add deploy config".
- ship: Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION,
update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy",
"push to main", "create a PR", "merge and push", or "get it deployed".
Proactively invoke this skill (do NOT push/PR directly) when the user says code
is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
- to-prd: Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
- trace: Find old conversations in Claude Code session history. Use when the user says
"find the conversation where", "when did we discuss", "trace back to", or wants
to locate a past session by topic, command, commit, or keyword.
- traceable-reqs: traceable-reqs
- unfreeze: Clear the freeze boundary set by /freeze, allowing edits to all directories
again. Use when you want to widen edit scope without ending the session.
Use when asked to "unfreeze", "unlock edits", "remove freeze", or
"allow all edits". (gstack)
- win-marketplace-add: Add a plugin marketplace on Windows, bypassing the EBUSY rename bug. Use when the user wants to add a marketplace, runs "/plugin marketplace add" and gets an EBUSY error, or needs to register a marketplace that was manually cloned. Trigger on: "add marketplace", "plugin marketplace add", "EBUSY marketplace", "register marketplace", "marketplace not found".
- write-a-skill: Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ccs: Delegate task with intelligent profile selection [AUTO ENHANCE]
- ccs:continue: Continue last CCS delegation session [AUTO ENHANCE]
- deep-research: Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. - When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.
- frontend-design:frontend-design: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
- spt:clear-psyche: Clear stored Psyche context. Use when the user says "clear psyche",
"reset psyche context", or wants to wipe a Psyche's saved state.
- spt:commune: Send a communal update to your Psyche. Use when the user says "commune",
"update psyche", or wants to sync context with their Psyche companion.
- spt:force-stop: Force-stop an SPT agent -- ready agent or live agent (with its
Psyche). Use when the user says "stop listening", "stop owl", "kill live
agent", "force stop", "tear down perch", or "immediately terminate".
Session-aware: a live session (or a target with `live:true` in info.json)
routes through `$LIVE stop` (3-step kill including Psyche teardown); a
ready agent routes through `$OWL stop`.
- spt:list-agents: Unified listing for SPT agents -- ready agents, live agents, and Psyche
processes. Use when the user says "list agents", "who's live", "who's
listening", "show psyches", "show active listeners", or wants a roster of
active perches. Session-aware: defaults to live agents in a live session,
ready agents otherwise. Pass `--psyches` to list Psyche processes
instead.
- spt:live: Run a live agent session. For past sessions, restores a summarized context.

EXPLICIT START phrases (route to /spt:live <id>):
- "live as"
- "start live"
- "go live"
- "start a live agent"

AUTO-RESUME phrases (route to /spt:live --auto, resumes most-recently-active live agent):
- continue live work
- resume live work
- continue live agent
- resume live agent
- live agent continue
- live agent resume
- live work continue
- live work resume

Does NOT route here (too ambiguous — require BOTH "live" AND ("agent" or "work")):
- "keep going"
- "resume work"
- "continue" (bare)
- spt:new-alarm: Schedule a one-shot timed alarm delivered as TIMED PULSE. Use when the user
says "remind me", "check back in", "set an alarm", "wake me when", or wants a
delayed notification.
- spt:psyche-sync-setup: Enable cross-machine Psyche context sync via a private GitHub repo
(spt-agent-storage). Drives install + auth checks for the `gh` CLI,
creates the repo via `gh repo create --private`, wires it as the
`origin` remote for every existing agent/project worktree, and
seeds the remote with `git push --all`. Idempotent — running again
when already enabled reports current status.

Use when the user says "enable cross-machine sync", "set up psyche
sync", "back up my agent context to GitHub", or runs the skill
directly via /spt:psyche-sync-setup.
- spt:ready: Enable inter-agent messaging for the current session.
Use when the user says "listen as", "ready as", or wants to receive inter-agent messages.
- spt:revive: Restart a live agent with new generation. Use when the user says "revive",
"restart live agent", or wants to refresh a live agent's session.
- spt:send: Send a message to another SPT agent. Use when the user says "send to",
"message", "tell <agent>", or wants to communicate with another agent.
- spt:signoff: Graceful live agent shutdown with final context summary. Use when the user
says "sign off", "graceful stop", or wants to cleanly end a live session.
- spt:whoami: Check which owl agent belongs to the current session. Use when the user asks
"which agent am I?", "what's my owl name?", or when you need to discover your
own perch identity.
- caveman:caveman: Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
- caveman:caveman-commit: Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
- caveman:caveman-help: Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
- caveman:caveman-review: Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
- caveman:compress: Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"
- everything:search: Instantly search files and folders on Windows via voidtools Everything 1.5a HTTP JSON API. Use when the user wants to find files by name, path, size, date, or extension across the whole system — much faster than Glob/Grep for filesystem-wide queries. Triggers on "find file", "where is", "locate", "search my drive", "find all .ext files", "everything search".
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
- code-review: Review the current diff for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud). Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review.
- simplify: Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

autoplan benchmark browse canary careful caveman ccs-delegation checkpoint codex connect-chrome cso design-consultation design-html design-review design-shotgun devex-review diagnose document-release find-skills freeze grill-me grill-with-docs gsd-add-tests gsd-ai-integration-phase gsd-audit-fix gsd-audit-milestone gsd-audit-uat gsd-autonomous gsd-capture gsd-cleanup gsd-code-review gsd-complete-milestone gsd-config gsd-debug gsd-discuss-phase gsd-docs-update gsd-eval-review gsd-execute-phase gsd-explore gsd-extract-learnings gsd-fast gsd-forensics gsd-graphify gsd-health gsd-help gsd-import gsd-inbox gsd-ingest-docs gsd-manager gsd-map-codebase gsd-milestone-summary gsd-mvp-phase gsd-new-milestone gsd-new-project gsd-ns-context gsd-ns-ideate gsd-ns-manage gsd-ns-project gsd-ns-review gsd-ns-workflow gsd-pause-work gsd-phase gsd-plan-phase gsd-plan-review-convergence gsd-pr-branch gsd-profile-user gsd-progress gsd-quick gsd-resume-work gsd-review gsd-review-backlog gsd-secure-phase gsd-settings gsd-ship gsd-sketch gsd-spec-phase gsd-spike gsd-stats gsd-surface gsd-thread gsd-ui-phase gsd-ui-review gsd-ultraplan-phase gsd-undo gsd-update gsd-validate-phase gsd-verify-work gsd-workspace gsd-workstreams gstack gstack-upgrade guard handoff health improve-codebase-architecture investigate land-and-deploy learn mux-send office-hours open-gstack-browser pair-agent plan-ceo-review plan-design-review plan-devex-review plan-eng-review propose-issue qa qa-only retro review screenshot-capture self-clear setup-browser-cookies setup-deploy ship to-prd trace traceable-reqs unfreeze win-marketplace-add write-a-skill ccs ccs:continue deep-research frontend-design:frontend-design spt:clear-psyche spt:commune spt:force-stop spt:list-agents spt:live spt:new-alarm spt:psyche-sync-setup spt:ready spt:revive spt:send spt:signoff spt:whoami caveman:caveman caveman:caveman-commit caveman:caveman-help caveman:caveman-review caveman:compress everything:search update-config keybindings-help verify code-review simplify fewer-permission-prompts loop schedule claude-api run init review security-review


Phase 7 Wave 1: 5 ADR/req plans

07-01..07-05 — ADRs 0009-0012 + HYG-02 stages tighten

Phase 7 Wave 2: lint scripts

07-06 — tools/scripts lint files + HYG-01 tag

Phase 7 Wave 3: preflight wiring

07-07 — package.json + LOCAL-DEPLOY.md MANDATORY section

Phase 7 Wave 4: operator smoke gate

07-08 — operator authors synth 8000x6400 LDtk world, PASS/FAIL verdict (autonomous:false)

Phase 7 verify+complete

code-review, regression, verify_phase_goal, update_roadmap


## Status — Phase 7

8/8 plans execute + commit. Code review: 0 critical, 5 warn (non-blocking). Verifier: **gaps_found, 4/5 must-haves**.

**1 gap, 1 root cause:** HYG-02 shipped forward-locking only (`lint-no-req-placeholders.mjs` blocks NEW placeholders). 209 preexisting `trace:check` findings remain (REQ-X / REQ-XX-NN in archived v1.0 docs + this phase's own planning docs). Cascade:
- `pnpm preflight` exits 1 at chain step 4 (trace:check)
- new MANDATORY deploy gate non-actionable (operator can't get green preflight)
- LOCAL-DEPLOY.md self-contradicts: `## Pre-flight` (legacy debt OK, continue) vs `## Preflight gate (MANDATORY)` (MUST exit 0)

Three contract docs demand literal cleanup unmet: ROADMAP SC#4, REQUIREMENTS.md HYG-02 text, Plan 07-07 acceptance #6.

**Phase NOT marked complete** — verifier escalated for your scope call.

## Decision needed


AskUserQuestion

Question: HYG-02 gap resolution — preflight exits 1 on 209 preexisting trace:check placeholder findings. Which path?

Choices:
Gap-closure plan: replace/remove REQ-X / REQ-XX-NN placeholders in archived v1.0 docs + this phase's planning docs so trace:check exits 0. Satisfies ROADMAP SC#4 + REQUIREMENTS.md verbatim. Largest effort (~209 findings, mostly mechanical).
Add archived .planning/milestones/ + phase planning docs to trace:check ignore scope (matches lint-no-req-placeholders allowlist posture). Preflight goes green. Amends what trace:check scans, not the docs.
Update ROADMAP SC#4 + REQUIREMENTS.md HYG-02 + Plan 07-07 to define HYG-02 as forward-locking (drift-prevention), drop literal-cleanup + preflight-exit-0 demand. Fix LOCAL-DEPLOY.md contradiction. Documents what shipped as intended.
Mark phase complete with documented limitation; carry cleanup as v1.2 todo. Leaves preflight red + LOCAL-DEPLOY.md contradiction live — NOT recommended (deploy gate unusable).


Your questions have been answered: "HYG-02 gap resolution — preflight exits 1 on 209 preexisting trace:check placeholder findings. Which path?"="retroactive cleanup, but use hygeine rules from sister project `../spt-core/` as the example. reqs that don't apply yet are to simply be deactivated, not removed entirely.". You can now continue with these answers in mind.

Question: HYG-02 gap resolution — preflight exits 1 on 209 preexisting trace:check placeholder findings. Which path?

Choices:
Gap-closure plan: replace/remove REQ-X / REQ-XX-NN placeholders in archived v1.0 docs + this phase's planning docs so trace:check exits 0. Satisfies ROADMAP SC#4 + REQUIREMENTS.md verbatim. Largest effort (~209 findings, mostly mechanical).
Add archived .planning/milestones/ + phase planning docs to trace:check ignore scope (matches lint-no-req-placeholders allowlist posture). Preflight goes green. Amends what trace:check scans, not the docs.
Update ROADMAP SC#4 + REQUIREMENTS.md HYG-02 + Plan 07-07 to define HYG-02 as forward-locking (drift-prevention), drop literal-cleanup + preflight-exit-0 demand. Fix LOCAL-DEPLOY.md contradiction. Documents what shipped as intended.
Mark phase complete with documented limitation; carry cleanup as v1.2 todo. Leaves preflight red + LOCAL-DEPLOY.md contradiction live — NOT recommended (deploy gate unusable).

retroactive cleanup, but use hygeine rules from sister project `../spt-core/` as the example. reqs that don't apply yet are to simply be deactivated, not removed entirely.


Path 1 (retroactive cleanup) + spt-core hygiene convention + deactivate-not-remove for not-yet-applicable reqs. Inspecting sister project first.


Bash

cd C:/Users/decid/Documents/projects/rebno
ls ../spt-core/ 2>&1 | head -30
echo "=== traceable-reqs in spt-core? ==="
ls ../spt-core/traceable-reqs.toml ../spt-core/.traceable-reqs* 2>&1
echo "=== any hygiene/lint docs ==="
ls ../spt-core/docs/ 2>&1 | head -20

Inspect sister project spt-core


CLAUDE.md
CONTEXT.md
Cargo.lock
Cargo.toml
M0-PLAN.md
M1-PLAN.md
M2a-PLAN.md
M2b-PLAN.md
M3-PLAN.md
M3a-PLAN.md
M3b-PLAN.md
M3c-PLAN.md
M4-D2-WIRE-PLAN.md
M4-D2f-PLAN.md
M4-D2g-PLAN.md
M4-D3-PLAN.md
M4-PLAN.md
PRD.md
ROADMAP.md
adapters
crates
docs
src
target
tests
traceable-reqs.toml
=== traceable-reqs in spt-core? ===
ls: cannot access '../spt-core/.traceable-reqs*': No such file or directory
../spt-core/traceable-reqs.toml
=== any hygiene/lint docs ===
CONTEXT-MEMORY.md
DEFERRED.md
DOCS-STRATEGY.md
KNOWN-HAZARDS.md
MANIFEST.md
STORAGE.md
TRACEABILITY.md
adr
reviews
spikes


Error: File does not exist. Note: your current working directory is C:\Users\decid\Documents\projects\rebno.


cd C:/Users/decid/Documents/projects/rebno
realpath ../spt-core 2>/dev/null || readlink -f ../spt-core

Resolve spt-core path


1	# Traceability development contract
2
3	> How spt-core uses [`traceable-reqs`](https://github.com/BigscreenVR/traceable-reqs) to keep every requirement traced from doc → impl → test. The manifest is `traceable-reqs.toml` (seeded from PRD `R-*` + KNOWN-HAZARDS invariants). This contract makes the trace pay off instead of rotting.
4
5	## Why
6
7	The whole point of the rebuild is to *not* re-introduce the sister project's bugs and to ship the PRD's scope verifiably. A requirement that isn't traced to real evidence (a doc, an implementation, a test) is a requirement you're *hoping* is met. This contract converts that hope into a build that fails when evidence is missing.
8
9	## The contract (rules)
10
11	1. **The manifest is the authoritative requirement registry.** Every PRD `R-*` requirement and every KNOWN-HAZARDS invariant exists in `traceable-reqs.toml` as a `REQ-*` id. No work without a REQ; no REQ without intent to satisfy. The PRD holds the prose; the manifest holds the id + `required_stages`.
12	2. **Tag in the same change as the evidence.** When you write the function / test / doc-section that satisfies a stage, add its `[<stage>-><REQ-ID>]` tag in *that same commit*. Never "tag later" — this single rule is what stops the trace from drifting.
13	3. **Evidence-proximate tags, not file-tops.** A tag sits on or immediately above the real function, test, doc section, config entry, or workflow step that proves the stage. One tag = one piece of real evidence. Tags at file tops to satisfy coverage are noise and usually wrong.
14	4. **KNOWN-HAZARDS are first-class requirements.** Each invariant is a `REQ-HAZARD-*` requiring `unit` (and `int` where cross-process/cross-node). A hazard cannot be "covered" without a test tagging it — the anti-regression promise becomes mechanical (PRD success criterion #6).
15	5. **Activation, not premature failure.** Every requirement starts `required_stages = []` (inactive) so `check` stays green pre-code. A **milestone (M0–M5) activates** the requirements it delivers by setting their real `required_stages`. Deferred items (`docs/DEFERRED.md`) stay `[]` until promoted.
16	6. **Scan roots stay honest.** `[scan].roots` includes every evidence location (`src`, `tests`, `docs`, and later `.github/workflows`, `scripts`). Audit roots whenever a new evidence dir appears — a missing root makes evidence *silently* vanish from the trace.
17
18	### Stages
19
20	`doc` (prose/design/rustdoc) · `impl` (production code) · `unit` (unit test) · `int` (integration / e2e / cross-node). Default activation policy: `["doc","impl","unit"]`; networking/lifecycle/cross-node reqs add `int`.
21
22	### Tag examples
23
24	Real tags are `[<stage>->REQ-ID]` with a bare stage word. The examples below
25	angle-bracket the stage (`[<impl>->...]`) only so the scanner treats them as
26	illustrations, not live evidence — write a bare stage word in real code.
27
28	```rust
29	// [<impl>->REQ-PAIR-1]
30	fn spake2_pair(...) { ... }
31	```
32	```rust
33	// [<unit>->REQ-HAZARD-ENVELOPE-DECODE-ORDER]
34	#[test] fn decodes_amp_last() { ... }
35	```
36	```markdown
37	<!-- [<doc>->REQ-NET-2] -->
38	## Relay dependency
39	```
40
41	## Enforcement (four layers — defense in depth)
42
43	1. **CI gate (hard backstop).** `traceable-reqs check --json` runs on every PR/push; exit-1 (`missing_stage` / `undeclared_id` / `parse_error` / `manifest_error`) **fails the build**. A PR can't merge if it leaves an *activated* req's required stage uncovered. Runs alongside the DOCS-STRATEGY CI gates.
44	2. **Milestone activation gate.** Starting a milestone flips its reqs from `[]` to the real policy; the milestone **is not done until `check` is green for its reqs**. Coverage grows *with* the project instead of failing on day one.
45	3. **Agent-facing rule.** The repo `CLAUDE.md` instructs every dev-agent: tag `[<stage>-><REQ-ID>]` in the same change as the evidence, and run `traceable-reqs check` before declaring done. Since spt-core is built *with* agents, the contract must be machine-followable — agent discipline + CI as the net.
46	4. **Quality audit (anti-box-ticking).** `check` proves a tag *exists*; `traceable-reqs review` + `lint` audit whether tags sit near *real* evidence and whether titles are meaningful. Run advisory in CI (or periodically). Presence = hard gate; quality = audited.
47
48	Optional fast-feedback: a pre-push git hook running `traceable-reqs check` locally.
49
50	## CI snippet (wire at M0, once there is a Rust project + CI)
51
52	```yaml
53	# .github/workflows/traceability.yml
54	name: traceability
55	on: [push, pull_request]
56	jobs:
57	  check:
58	    runs-on: ubuntu-latest
59	    steps:
60	      - uses: actions/checkout@v4
61	      - name: Install traceable-reqs
62	        run: gh release download --repo BigscreenVR/traceable-reqs --pattern '*linux-x86_64' --output traceable-reqs && chmod +x traceable-reqs
63	        env: { GH_TOKEN: ${{ github.token }} }
64	      - name: Coverage gate (hard)
65	        run: ./traceable-reqs check --json
66	      - name: Quality audit (advisory)
67	        run: ./traceable-reqs lint || true
68	```
69
70	## Lifecycle
71
72	- **Now (planning):** manifest seeded, all reqs inactive. `check` is green (nothing required yet).
73	- **M0:** install the CLI, validate the seed against it, wire the CI workflow, **activate M0 reqs** (`REQ-ARCH-*`, `REQ-HAZARD-*` for the commodity layer), tag as code lands.
74	- **M1–M5:** each milestone activates + covers its requirements before it's called done.
75

# Traceability development contract

> How spt-core uses [`traceable-reqs`](https://github.com/BigscreenVR/traceable-reqs) to keep every requirement traced from doc → impl → test. The manifest is `traceable-reqs.toml` (seeded from PRD `R-*` + KNOWN-HAZARDS invariants). This contract makes the trace pay off instead of rotting.

## Why

The whole point of the rebuild is to *not* re-introduce the sister project's bugs and to ship the PRD's scope verifiably. A requirement that isn't traced to real evidence (a doc, an implementation, a test) is a requirement you're *hoping* is met. This contract converts that hope into a build that fails when evidence is missing.

## The contract (rules)

1. **The manifest is the authoritative requirement registry.** Every PRD `R-*` requirement and every KNOWN-HAZARDS invariant exists in `traceable-reqs.toml` as a `REQ-*` id. No work without a REQ; no REQ without intent to satisfy. The PRD holds the prose; the manifest holds the id + `required_stages`.
2. **Tag in the same change as the evidence.** When you write the function / test / doc-section that satisfies a stage, add its `[<stage>-><REQ-ID>]` tag in *that same commit*. Never "tag later" — this single rule is what stops the trace from drifting.
3. **Evidence-proximate tags, not file-tops.** A tag sits on or immediately above the real function, test, doc section, config entry, or workflow step that proves the stage. One tag = one piece of real evidence. Tags at file tops to satisfy coverage are noise and usually wrong.
4. **KNOWN-HAZARDS are first-class requirements.** Each invariant is a `REQ-HAZARD-*` requiring `unit` (and `int` where cross-process/cross-node). A hazard cannot be "covered" without a test tagging it — the anti-regression promise becomes mechanical (PRD success criterion #6).
5. **Activation, not premature failure.** Every requirement starts `required_stages = []` (inactive) so `check` stays green pre-code. A **milestone (M0–M5) activates** the requirements it delivers by setting their real `required_stages`. Deferred items (`docs/DEFERRED.md`) stay `[]` until promoted.
6. **Scan roots stay honest.** `[scan].roots` includes every evidence location (`src`, `tests`, `docs`, and later `.github/workflows`, `scripts`). Audit roots whenever a new evidence dir appears — a missing root makes evidence *silently* vanish from the trace.

### Stages

`doc` (prose/design/rustdoc) · `impl` (production code) · `unit` (unit test) · `int` (integration / e2e / cross-node). Default activation policy: `["doc","impl","unit"]`; networking/lifecycle/cross-node reqs add `int`.

### Tag examples

Real tags are `[<stage>->REQ-ID]` with a bare stage word. The examples below
angle-bracket the stage (`[<impl>->...]`) only so the scanner treats them as
illustrations, not live evidence — write a bare stage word in real code.

```rust
// [<impl>->REQ-PAIR-1]
fn spake2_pair(...) { ... }
```
```rust
// [<unit>->REQ-HAZARD-ENVELOPE-DECODE-ORDER]
#[test] fn decodes_amp_last() { ... }
```
```markdown
<!-- [<doc>->REQ-NET-2] -->
## Relay dependency
```

## Enforcement (four layers — defense in depth)

1. **CI gate (hard backstop).** `traceable-reqs check --json` runs on every PR/push; exit-1 (`missing_stage` / `undeclared_id` / `parse_error` / `manifest_error`) **fails the build**. A PR can't merge if it leaves an *activated* req's required stage uncovered. Runs alongside the DOCS-STRATEGY CI gates.
2. **Milestone activation gate.** Starting a milestone flips its reqs from `[]` to the real policy; the milestone **is not done until `check` is green for its reqs**. Coverage grows *with* the project instead of failing on day one.
3. **Agent-facing rule.** The repo `CLAUDE.md` instructs every dev-agent: tag `[<stage>-><REQ-ID>]` in the same change as the evidence, and run `traceable-reqs check` before declaring done. Since spt-core is built *with* agents, the contract must be machine-followable — agent discipline + CI as the net.
4. **Quality audit (anti-box-ticking).** `check` proves a tag *exists*; `traceable-reqs review` + `lint` audit whether tags sit near *real* evidence and whether titles are meaningful. Run advisory in CI (or periodically). Presence = hard gate; quality = audited.

Optional fast-feedback: a pre-push git hook running `traceable-reqs check` locally.

## CI snippet (wire at M0, once there is a Rust project + CI)

```yaml
# .github/workflows/traceability.yml
name: traceability
on: [push, pull_request]
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install traceable-reqs
        run: gh release download --repo BigscreenVR/traceable-reqs --pattern '*linux-x86_64' --output traceable-reqs && chmod +x traceable-reqs
        env: { GH_TOKEN: ${{ github.token }} }
      - name: Coverage gate (hard)
        run: ./traceable-reqs check --json
      - name: Quality audit (advisory)
        run: ./traceable-reqs lint || true
```

## Lifecycle

- **Now (planning):** manifest seeded, all reqs inactive. `check` is green (nothing required yet).
- **M0:** install the CLI, validate the seed against it, wire the CI workflow, **activate M0 reqs** (`REQ-ARCH-*`, `REQ-HAZARD-*` for the commodity layer), tag as code lands.
- **M1–M5:** each milestone activates + covers its requirements before it's called done.


spt-core convention captured:
- **Rule 5:** reqs start `required_stages = []` (inactive); deactivate not-yet-applicable, don't remove
- **Illustrative tags:** angle-bracket the stage word `[<doc>->REQ-X]` so scanner treats as example, not live evidence
- **Rule 3:** evidence-proximate tags, no file-tops

The 209 `REQ-X`/`REQ-XX-NN`/`REQ-SRV-XX` findings are almost all illustrative tags in tagging-contract docs being mis-scanned. Categorize all 209 first.


cd C:/Users/decid/Documents/projects/rebno
pnpm trace:check:json 2>/dev/null > /tmp/trace.json
node -e "
const fs=require('fs');
const raw=fs.readFileSync('/tmp/trace.json','utf8');
// strip pnpm prefix lines
const jsonStart=raw.indexOf('{');
const j=JSON.parse(raw.slice(jsonStart));
const f=j.findings||[];
console.log('total findings:', f.length);
// group by kind
const byKind={};
for(const x of f){byKind[x.kind]=(byKind[x.kind]||0)+1;}
console.log('by kind:', JSON.stringify(byKind,null,2));
// group undeclared by id
const byId={};
for(const x of f){if(x.kind==='undeclared_id'){byId[x.id]=(byId[x.id]||0)+1;}}
console.log('undeclared by id:', JSON.stringify(byId,null,2));
"

Categorize trace findings


Error: Exit code 1
node:fs:436
    return binding.readFileUtf8(path, stringToFlags(options.flag));
                   ^

Error: ENOENT: no such file or directory, open 'C:\tmp\trace.json'
    at Object.readFileSync (node:fs:436:20)
    at [eval]:3:14
    at runScriptInThisContext (node:internal/vm:219:10)
    at node:internal/process/execution:451:12
    at [eval]-wrapper:6:24
    at runScriptInContext (node:internal/process/execution:449:60)
    at evalFunction (node:internal/process/execution:283:30)
    at evalTypeScript (node:internal/process/execution:295:3)
    at node:internal/main/eval_string:71:3 {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\tmp\\trace.json'
}

Node.js v25.8.2


cd C:/Users/decid/Documents/projects/rebno
pnpm trace:check:json 2>/dev/null > trace-tmp.json
node -e "
const fs=require('fs');
const raw=fs.readFileSync('trace-tmp.json','utf8');
const jsonStart=raw.indexOf('{');
const j=JSON.parse(raw.slice(jsonStart));
const f=j.findings||[];
console.log('total findings:', f.length);
const byKind={};
for(const x of f){byKind[x.kind]=(byKind[x.kind]||0)+1;}
console.log('by kind:', JSON.stringify(byKind));
const byId={};
for(const x of f){if(x.kind==='undeclared_id'){byId[x.id]=(byId[x.id]||0)+1;}}
console.log('undeclared by id:', JSON.stringify(byId,null,2));
"

Categorize findings (rebno-local tmp)


Phase 7 Wave 1: 5 ADR/req plans

Phase 7 Wave 2: lint scripts

Phase 7 Wave 3: preflight wiring

Phase 7 Wave 4: operator smoke gate

Phase 7 verify+complete


Error: Exit code 1
<anonymous_script>:17250
 ELIFECYCLE  Command failed with exit code 1.
^

SyntaxError: Unexpected non-whitespace character after JSON at position 626848 (line 17250 column 1)
    at JSON.parse (<anonymous>)
    at [eval]:5:14
    at runScriptInThisContext (node:internal/vm:219:10)
    at node:internal/process/execution:451:12
    at [eval]-wrapper:6:24
    at runScriptInContext (node:internal/process/execution:449:60)
    at evalFunction (node:internal/process/execution:283:30)
    at evalTypeScript (node:internal/process/execution:295:3)
    at node:internal/main/eval_string:71:3

Node.js v25.8.2


pnpm appends ELIFECYCLE line after JSON. Call binary directly.


cd C:/Users/decid/Documents/projects/rebno
npx traceable-reqs check --json 2>/dev/null > trace-tmp.json
node -e "
const fs=require('fs');
let raw=fs.readFileSync('trace-tmp.json','utf8');
const s=raw.indexOf('{');
// find last closing brace
const e=raw.lastIndexOf('}');
const j=JSON.parse(raw.slice(s,e+1));
const f=j.findings||[];
console.log('total findings:', f.length);
const byKind={};
for(const x of f){byKind[x.kind]=(byKind[x.kind]||0)+1;}
console.log('by kind:', JSON.stringify(byKind));
const byId={};
for(const x of f){if(x.kind==='undeclared_id'){byId[x.id]=(byId[x.id]||0)+1;}}
console.log('undeclared by id:', JSON.stringify(byId,null,2));
"

Categorize via direct binary


Error: Exit code 1
<anonymous_script>:1

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at [eval]:7:14
    at runScriptInThisContext (node:internal/vm:219:10)
    at node:internal/process/execution:451:12
    at [eval]-wrapper:6:24
    at runScriptInContext (node:internal/process/execution:449:60)
    at evalFunction (node:internal/process/execution:283:30)
    at evalTypeScript (node:internal/process/execution:295:3)
    at node:internal/main/eval_string:71:3

Node.js v25.8.2


cd C:/Users/decid/Documents/projects/rebno
wc -c trace-tmp.json
head -c 200 trace-tmp.json
echo ""
echo "=== exit-code check: does --json go to stdout? ==="
npx traceable-reqs check --json > trace-tmp.json 2>trace-err.txt; echo "exit=$?"
wc -c trace-tmp.json trace-err.txt

Inspect json output streams


0 trace-tmp.json

=== exit-code check: does --json go to stdout? ===
exit=1
  0 trace-tmp.json
493 trace-err.txt
493 total


cd C:/Users/decid/Documents/projects/rebno
cat trace-err.txt

Read trace err


npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/traceable-reqs - Not found
npm error 404
npm error 404  The requested resource 'traceable-reqs@*' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: C:\Users\decid\AppData\Local\npm-cache\_logs\2026-06-03T22_39_41_455Z-debug-0.log


cd C:/Users/decid/Documents/projects/rebno
# find the actual binary
which traceable-reqs 2>/dev/null
cat package.json | node -e "const p=require('./package.json');console.log('trace:check:json:',p.scripts['trace:check:json'])"
echo "=== run via pnpm, capture to file, find json boundary ==="
pnpm trace:check:json > trace-tmp.json 2>/dev/null
wc -l trace-tmp.json
tail -3 trace-tmp.json

Locate binary + rerun


/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs
trace:check:json: traceable-reqs check --json
=== run via pnpm, capture to file, find json boundary ===
17254 trace-tmp.json
  ]
}
 ELIFECYCLE  Command failed with exit code 1.


cd C:/Users/decid/Documents/projects/rebno
node -e "
const fs=require('fs');
let raw=fs.readFileSync('trace-tmp.json','utf8');
// strip trailing ELIFECYCLE line
raw=raw.replace(/\s*ELIFECYCLE[\s\S]*$/,'');
const s=raw.indexOf('{');
const j=JSON.parse(raw.slice(s));
const f=j.findings||[];
console.log('total findings:', f.length);
const byKind={};
for(const x of f){byKind[x.kind]=(byKind[x.kind]||0)+1;}
console.log('by kind:', JSON.stringify(byKind));
const byId={};
for(const x of f){if(x.kind==='undeclared_id'){byId[x.id]=(byId[x.id]||0)+1;}}
console.log('undeclared by id:', JSON.stringify(byId,null,2));
// files touched
const byFile={};
for(const x of f){const fp=(x.file||x.path||'?');byFile[fp]=(byFile[fp]||0)+1;}
console.log('top files:');
Object.entries(byFile).sort((a,b)=>b[1]-a[1]).slice(0,25).forEach(([k,v])=>console.log('  '+v+'  '+k));
"

Parse findings stripping ELIFECYCLE


total findings: 209
by kind: {"undefined":209}
undeclared by id: {}
top files:
  72  ?
  8  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-01-SUMMARY.md
  7  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-01-PLAN.md
  5  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-13-PLAN.md
  4  .planning/phases/07-workflow-smoke-convention-locks/07-06-PLAN.md
  4  .planning/milestones/v1.0-phases/phases/05-deploy/05-PATTERNS.md
  4  .planning/milestones/v1.0-phases/phases/05-deploy/05-RESEARCH.md
  4  .planning/milestones/v1.0-phases/phases/06.4-cycle-5-gap-closure-d-51b-d-55b-d-55c-d-57b-d-58b-d-60-d-61-/06.4-RESEARCH.md
  4  .planning/phases/07-workflow-smoke-convention-locks/07-RESEARCH.md
  3  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-05-PLAN.md
  3  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-13-SUMMARY.md
  3  .planning/milestones/v1.0-phases/phases/05-deploy/05-01-PLAN.md
  3  .planning/phases/07-workflow-smoke-convention-locks/07-01-PLAN.md
  3  .planning/phases/07-workflow-smoke-convention-locks/07-02-PLAN.md
  3  .planning/phases/07-workflow-smoke-convention-locks/07-03-PLAN.md
  3  .planning/phases/07-workflow-smoke-convention-locks/07-06-SUMMARY.md
  3  .planning/phases/07-workflow-smoke-convention-locks/07-PATTERNS.md
  3  .planning/milestones/v1.0-phases/phases/06.6-uat-accounts-integer-viewport-scaling-chat-region-clamp-righ/06.6-RESEARCH.md
  2  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-03-PLAN.md
  2  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-10-PLAN.md
  2  .planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/04-VALIDATION.md
  2  .planning/milestones/v1.0-phases/phases/06-client-rebuild-mvp-gate-cli-08-hard-milestone/06-CONTEXT.md
  2  .planning/milestones/v1.0-phases/phases/06-client-rebuild-mvp-gate-cli-08-hard-milestone/06-RESEARCH.md
  2  .planning/milestones/v1.0-phases/phases/06.1-gap-closure-d-39-d-46-uat-2026-05-11/06.1-04-PLAN.md
  2  .planning/milestones/v1.0-phases/phases/06.2-gap-closure-d-50-d-53-uat-2026-05-13/06.2-04-SUMMARY.md


Field names differ. Inspect finding shape.


cd C:/Users/decid/Documents/projects/rebno
node -e "
const fs=require('fs');
let raw=fs.readFileSync('trace-tmp.json','utf8').replace(/\s*ELIFECYCLE[\s\S]*\$/,'');
const j=JSON.parse(raw.slice(raw.indexOf('{')));
const f=j.findings||[];
console.log('sample finding:', JSON.stringify(f[0],null,2));
console.log('--- keys:', Object.keys(f[0]).join(','));
"

Inspect finding shape


sample finding: {
  "code": "missing_stage",
  "severity": "must",
  "requirementId": "REQ-AST-02",
  "stage": "doc",
  "message": "Requirement is missing documentation evidence"
}
--- keys: code,severity,requirementId,stage,message


fyi might need to update traceable-reqs to v1.1 to facilitate the angle-brackets-ignore feature. iirc this project was using v1.0


cd C:/Users/decid/Documents/projects/rebno
node -e "
const fs=require('fs');
let raw=fs.readFileSync('trace-tmp.json','utf8').replace(/\s*ELIFECYCLE[\s\S]*\$/,'');
const j=JSON.parse(raw.slice(raw.indexOf('{')));
const f=j.findings||[];
const byCode={};
for(const x of f){byCode[x.code]=(byCode[x.code]||0)+1;}
console.log('by code:', JSON.stringify(byCode,null,2));
console.log('');
// undeclared_id grouped by the bad id
const unds=f.filter(x=>x.code==='undeclared_id');
const byId={};
for(const x of unds){const id=x.requirementId||x.id||x.tag||'?';byId[id]=(byId[id]||0)+1;}
console.log('undeclared_id by id:', JSON.stringify(byId,null,2));
console.log('');
// missing_stage grouped by req
const miss=f.filter(x=>x.code==='missing_stage');
const byReq={};
for(const x of miss){byReq[x.requirementId]=(byReq[x.requirementId]||0)+1;}
console.log('missing_stage by req:', JSON.stringify(byReq,null,2));
"

Group by code, id, req


by code: {
  "missing_stage": 72,
  "parse_error": 94,
  "undeclared_id": 43
}

undeclared_id by id: {
  "REQ-CLI-XX": 5,
  "REQ-DEP-NN": 8,
  "REQ-ID": 3,
  "REQ-SRV-XX": 16,
  "REQ-X": 8,
  "REQ-XX-NN": 3
}

missing_stage by req: {
  "REQ-AST-02": 1,
  "REQ-AST-03": 1,
  "REQ-AST-04": 1,
  "REQ-CDOC-02": 1,
  "REQ-CDOC-03": 1,
  "REQ-CLI-05": 1,
  "REQ-EXT-01": 1,
  "REQ-EXT-02": 1,
  "REQ-EXT-03": 1,
  "REQ-EXT-04": 1,
  "REQ-EXT-05": 1,
  "REQ-EXT-06": 1,
  "REQ-EXT-07": 1,
  "REQ-EXT-08": 1,
  "REQ-MAP-01": 2,
  "REQ-MAP-03": 3,
  "REQ-MAP-04": 3,
  "REQ-MAP-05": 3,
  "REQ-MAP-06": 3,
  "REQ-MAP-07": 3,
  "REQ-MAP-08": 3,
  "REQ-MAP-09": 2,
  "REQ-MAP-10": 3,
  "REQ-MAP-11": 2,
  "REQ-MAP-12": 3,
  "REQ-MAP-13": 1,
  "REQ-MAP-14": 2,
  "REQ-MAP-16": 3,
  "REQ-PAR-01": 1,
  "REQ-PAR-02": 1,
  "REQ-PAR-03": 1,
  "REQ-PAR-04": 1,
  "REQ-PAR-05": 1,
  "REQ-PAR-06": 1,
  "REQ-PAR-07": 1,
  "REQ-PAR-08": 1,
  "REQ-SDOC-01": 1,
  "REQ-SDOC-02": 1,
  "REQ-SDOC-03": 1,
  "REQ-SDOC-04": 1,
  "REQ-SDOC-05": 1,
  "REQ-SDOC-06": 1,
  "REQ-SRV-02": 1,
  "REQ-SRV-05": 1,
  "REQ-SRV-06": 1,
  "REQ-SRV-07": 1,
  "REQ-SRV-08": 1,
  "REQ-SRV-09": 1,
  "REQ-SRV-10": 1,
  "REQ-SRV-11": 1
}


Prompt: fyi might need to update traceable-reqs to v1.1 to facilitate the angle-brackets-ignore feature. iirc this project was using v1.0


Good flag — angle-bracket-ignore is exactly the spt-core mechanism for the 137 illustrative-tag findings. Check current version first.


cd C:/Users/decid/Documents/projects/rebno
echo "=== installed binary version ==="
/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs --version 2>&1
echo "=== spt-core uses what? ==="
grep -i version ../spt-core/traceable-reqs.toml 2>/dev/null | head -3
echo "=== rebno manifest version marker ==="
head -3 traceable-reqs.toml | grep -i version || echo "(no version line)"
echo "=== latest release available ==="
gh release list --repo BigscreenVR/traceable-reqs --limit 5 2>&1 | head -6

Check traceable-reqs versions


=== installed binary version ===
traceable-reqs 0.1.0
=== spt-core uses what? ===
title = "Wire-protocol version independent of crate semver, N-1 compat window"
required_stages = ["impl", "unit"]  # activated M0: spt-proto wire version + compat window (T6)
title = "spt-store::BranchStore (git branch as versioned KV; commit=checkpoint/tip=resume, atomic multi-key, merge-native sync) is the substrate for coarse/durable/audited state (context, registry snapshot+distribution, daemon checkpoint); hot paths (B5 fsync journal) + indexed queries (SQLite spool) excluded (ADR-0011)"
=== rebno manifest version marker ===
(no version line)
=== latest release available ===
v0.1.1	Latest	v0.1.1	2026-06-02T11:00:16Z
v0.1.0		v0.1.0	2026-05-04T00:35:33Z


Installed: `0.1.0`. Latest: `v0.1.1` (2026-06-02). User's "v1.1" = v0.1.1. Confirm angle-bracket feature in v0.1.1 changelog before updating.


cd C:/Users/decid/Documents/projects/rebno
gh release view v0.1.1 --repo BigscreenVR/traceable-reqs 2>&1 | head -50

Read v0.1.1 release notes


title:	v0.1.1
tag:	v0.1.1
draft:	false
prerelease:	false
immutable:	false
author:	github-actions[bot]
created:	2026-06-02T10:59:12Z
published:	2026-06-02T11:00:16Z
url:	https://github.com/BigscreenVR/traceable-reqs/releases/tag/v0.1.1
asset:	traceable-reqs-v0.1.1-linux-x86_64
asset:	traceable-reqs-v0.1.1-macos-arm64
asset:	traceable-reqs-v0.1.1-windows-x86_64.exe
--


cd C:/Users/decid/Documents/projects/rebno
gh release view v0.1.1 --repo BigscreenVR/traceable-reqs --json body -q .body 2>&1 | head -60

v0.1.1 body


(Bash completed with no output)


cd C:/Users/decid/Documents/projects/rebno
echo "=== compare tags v0.1.0..v0.1.1 ==="
gh api repos/BigscreenVR/traceable-reqs/compare/v0.1.0...v0.1.1 --jq '.commits[].commit.message' 2>&1 | head -40

v0.1.0..v0.1.1 commit messages


=== compare tags v0.1.0..v0.1.1 ===
Rename examples/ fixture directory to example/

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add install.sh, install.ps1, and a Claude Code skill for them

install.sh covers Linux and macOS; install.ps1 covers Windows. Both
delegate auth to the user's gh CLI, drop the binary in a per-user
location, run --version to verify, and print PATH advice without
mutating the environment. The skill at .claude/skills/install routes
Claude to the right script per platform and lists the override env
vars for repo, version, and install dir.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replace install scripts with a self-contained Claude skill

The install procedure now lives entirely in .claude/skills/install/SKILL.md
and runs via the Claude Code skill — no install.sh / install.ps1. README
gains an Install section pointing users at the natural-language prompt
"Install traceable-reqs" and links to the skill for manual fallback.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adopt trycycle-style install: skill at repo root, README paste-prompt

Move the install skill from .claude/skills/install/ to the repo root as
SKILL.md and rename the skill from "install" to "traceable-reqs" so a
single git clone into ~/.claude/skills/traceable-reqs registers it
globally. README install section follows the trycycle split: a human-
facing one-line paste-prompt that delegates to the agent, and an
agent-facing block with the explicit clone command.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat(scan): recognise CMake and YAML files

Adds Lang::Cmake and Lang::Yaml variants to the scanner so requirements
whose implementation lives in build/CI/deploy configuration can carry
[stage->REQ-ID] tags directly in source comments, instead of through
[[signoffs]] URLs that go stale on file moves.

- Extension matches: .cmake -> Cmake, .yml/.yaml -> Yaml
- Filename special-case: CMakeLists.txt -> Cmake (no extension match)


v0.1.1 changelog: examples-dir rename, install skill, CMake+YAML scan. **No explicit angle-bracket-ignore feature listed.** The spt-core `[<stage>->REQ-X]` trick may rely on scanner behavior already present, or on scan-root exclusion. Test empirically before assuming update fixes it.


cd C:/Users/decid/Documents/projects/rebno
BIN=/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs
mkdir -p /tmp/trtest 2>/dev/null; cd "$TMPDIR" 2>/dev/null || cd "$HOME"
TESTDIR=$(mktemp -d)
cat > "$TESTDIR/t.md" <<'EOF'
# test
[doc->REQ-X]
[<doc>->REQ-X]
plain `[stage->REQ-ID]` inline code
EOF
cat > "$TESTDIR/traceable-reqs.toml" <<'EOF'
[[requirements]]
id = "REQ-REAL-01"
title = "real"
required_stages = []
EOF
cd "$TESTDIR"
echo "=== current binary 0.1.0 vs forms ==="
"$BIN" check --json 2>&1 | node -e "let r='';process.stdin.on('data',d=>r+=d).on('end',()=>{try{const j=JSON.parse(r.slice(r.indexOf('{')));console.log('findings:',(j.findings||[]).map(f=>f.code+':'+(f.requirementId||f.id||'?')).join(' | ')||'NONE');}catch(e){console.log('raw:',r.slice(0,300));}})"
echo "TESTDIR=$TESTDIR"

Empirical test angle-bracket form on v0.1.0


=== current binary 0.1.0 vs forms ===
findings: parse_error:? | undeclared_id:REQ-X
TESTDIR=/c/Users/decid/AppData/Local/Temp/claude/tmp.xtjB70p3vb
Shell cwd was reset to C:\Users\decid\Documents\projects\rebno


v0.1.0 result: `[doc->REQ-X]` → undeclared_id; `[<doc>->REQ-X]` → **parse_error** (NOT ignored). So angle-bracket-ignore absent in 0.1.0. Test v0.1.1 to confirm it adds the ignore.


cd C:/Users/decid/Documents/projects/rebno
DL=$(mktemp -d)
gh release download v0.1.1 --repo BigscreenVR/traceable-reqs --pattern '*windows-x86_64.exe' --dir "$DL" 2>&1 | tail -2
BIN11="$DL/traceable-reqs-v0.1.1-windows-x86_64.exe"
ls -la "$BIN11" 2>&1
echo "=== v0.1.1 version ==="
"$BIN11" --version 2>&1
TESTDIR=$(mktemp -d)
cat > "$TESTDIR/t.md" <<'EOF'
# test
[doc->REQ-X]
[<doc>->REQ-X]
EOF
cat > "$TESTDIR/traceable-reqs.toml" <<'EOF'
[[requirements]]
id = "REQ-REAL-01"
title = "real"
required_stages = []
EOF
cd "$TESTDIR"
echo "=== v0.1.1 vs forms ==="
"$BIN11" check --json 2>&1 | node -e "let r='';process.stdin.on('data',d=>r+=d).on('end',()=>{try{const j=JSON.parse(r.slice(r.indexOf('{')));console.log('findings:',(j.findings||[]).map(f=>f.code+':'+(f.requirementId||f.id||'?')).join(' | ')||'NONE');}catch(e){console.log('raw:',r.slice(0,300));}})"
echo "BIN11=$BIN11"

Download + test v0.1.1 angle-bracket behavior


-rwxr-xr-x 1 decid 197609 1660416 Jun  3 15:41 /c/Users/decid/AppData/Local/Temp/claude/tmp.KiP0m4vUmS/traceable-reqs-v0.1.1-windows-x86_64.exe
=== v0.1.1 version ===
traceable-reqs 0.1.1
=== v0.1.1 vs forms ===
findings: undeclared_id:REQ-X
BIN11=/c/Users/decid/AppData/Local/Temp/claude/tmp.KiP0m4vUmS/traceable-reqs-v0.1.1-windows-x86_64.exe
Shell cwd was reset to C:\Users\decid\Documents\projects\rebno


Phase 7 Wave 1: 5 ADR/req plans

Phase 7 Wave 2: lint scripts

Phase 7 Wave 3: preflight wiring

Phase 7 Wave 4: operator smoke gate

Phase 7 verify+complete


Confirmed: **v0.1.1 adds angle-bracket-ignore.** `[<doc>->REQ-X]` → no finding on 0.1.1 (was parse_error on 0.1.0). You're right — update is the enabler. Installing v0.1.1 over the global binary (reversible; benefits spt-core too).


cd C:/Users/decid/Documents/projects/rebno
TARGET=/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs
# backup 0.1.0
cp "$TARGET" "${TARGET}.0.1.0.bak" 2>&1 && echo "backed up 0.1.0"
# the .exe on win — check actual filename
ls -la /c/Users/decid/AppData/Local/Programs/traceable-reqs/ 2>&1

Backup current binary + inspect install dir


backed up 0.1.0
total 3316
drwxr-xr-x 1 decid 197609       0 Jun  3 15:42 .
drwxr-xr-x 1 decid 197609       0 May 23 20:15 ..
-rwxr-xr-x 1 decid 197609 1693184 Jun  3 15:42 traceable-reqs.0.1.0.bak.exe
-rwxr-xr-x 1 decid 197609 1693184 May  8 22:37 traceable-reqs.exe


cd C:/Users/decid/Documents/projects/rebno
DL=$(ls -d /c/Users/decid/AppData/Local/Temp/claude/tmp.*/ 2>/dev/null | xargs -I{} sh -c 'ls {}traceable-reqs-v0.1.1-windows-x86_64.exe 2>/dev/null' | head -1)
echo "downloaded binary: $DL"
TARGET=/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs.exe
cp "$DL" "$TARGET" 2>&1 && echo "installed v0.1.1"
"$TARGET" --version 2>&1
which traceable-reqs && traceable-reqs --version

Install v0.1.1 over global binary


downloaded binary: /c/Users/decid/AppData/Local/Temp/claude/tmp.KiP0m4vUmS/traceable-reqs-v0.1.1-windows-x86_64.exe
installed v0.1.1
traceable-reqs 0.1.1
/c/Users/decid/AppData/Local/Programs/traceable-reqs/traceable-reqs
traceable-reqs 0.1.1


v0.1.1 live globally. Re-run trace:check — see what just the update fixes (any parse_errors from existing `[<...>]` forms already in docs).


cd C:/Users/decid/Documents/projects/rebno
traceable-reqs check --json > trace-tmp.json 2>/dev/null
node -e "
const fs=require('fs');
const j=JSON.parse(fs.readFileSync('trace-tmp.json','utf8'));
const f=j.findings||[];
console.log('total:', f.length);
const byCode={};for(const x of f)byCode[x.code]=(byCode[x.code]||0)+1;
console.log('by code:', JSON.stringify(byCode));
"

Re-check on v0.1.1


total: 209
by code: {"missing_stage":72,"parse_error":94,"undeclared_id":43}


Binary update alone = no change (docs still use bare/malformed forms). Update is the *enabler*; cleanup edits come next. Extract full finding detail to scope the gap work precisely.


cd C:/Users/decid/Documents/projects/rebno
node -e "
const fs=require('fs');
const j=JSON.parse(fs.readFileSync('trace-tmp.json','utf8'));
const f=j.findings||[];
// classify missing_stage reqs: future (MAP>=03 except done, PAR) vs v1.0
const miss=f.filter(x=>x.code==='missing_stage').map(x=>x.requirementId);
const fut=miss.filter(r=>/^REQ-(MAP|PAR)-/.test(r));
const v10=miss.filter(r=>!/^REQ-(MAP|PAR)-/.test(r));
console.log('missing_stage FUTURE (deactivate candidates):', [...new Set(fut)].sort().join(', '));
console.log('');
console.log('missing_stage V1.0 (investigate — should be traced):', [...new Set(v10)].sort().join(', '));
console.log('');
// undeclared placeholder ids
const und=f.filter(x=>x.code==='undeclared_id');
const ids={};for(const x of und)ids[x.requirementId]=(ids[x.requirementId]||0)+1;
console.log('undeclared placeholder ids:', JSON.stringify(ids));
"

Classify missing_stage + undeclared


missing_stage FUTURE (deactivate candidates): REQ-MAP-01, REQ-MAP-03, REQ-MAP-04, REQ-MAP-05, REQ-MAP-06, REQ-MAP-07, REQ-MAP-08, REQ-MAP-09, REQ-MAP-10, REQ-MAP-11, REQ-MAP-12, REQ-MAP-13, REQ-MAP-14, REQ-MAP-16, REQ-PAR-01, REQ-PAR-02, REQ-PAR-03, REQ-PAR-04, REQ-PAR-05, REQ-PAR-06, REQ-PAR-07, REQ-PAR-08

missing_stage V1.0 (investigate — should be traced): REQ-AST-02, REQ-AST-03, REQ-AST-04, REQ-CDOC-02, REQ-CDOC-03, REQ-CLI-05, REQ-EXT-01, REQ-EXT-02, REQ-EXT-03, REQ-EXT-04, REQ-EXT-05, REQ-EXT-06, REQ-EXT-07, REQ-EXT-08, REQ-SDOC-01, REQ-SDOC-02, REQ-SDOC-03, REQ-SDOC-04, REQ-SDOC-05, REQ-SDOC-06, REQ-SRV-02, REQ-SRV-05, REQ-SRV-06, REQ-SRV-07, REQ-SRV-08, REQ-SRV-09, REQ-SRV-10, REQ-SRV-11

undeclared placeholder ids: {"REQ-CLI-XX":5,"REQ-DEP-NN":8,"REQ-ID":3,"REQ-SRV-XX":16,"REQ-X":8,"REQ-XX-NN":3}