spec-consistency

星标12

分支5

更新时间2026年4月29日 07:26

Cross-reference PRD ↔ TODO ↔ specs/*.md for drift, broken cross-links, and orphaned bullets. Use when the user asks to verify documentation consistency, after editing PRD or any spec, before publishing the repo, or when proof-reading.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

AndrewWayne

AndrewWayne/oh-my-warp

打开 GitHub 仓库查看创作者相关仓库

下载

Spec Consistency

Cross-checks that the planning docs agree with each other. The most useful command during the proof-reading phase.

What gets checked

PRD §3.1 ↔ TODO phase headings. Every commitment in PRD.md §3.1 should map to at least one task in TODO.md. Every TODO phase exit criterion should reflect §3.1 wording.
PRD §13 ↔ TODO phases. Phase IDs (Phase 0, v0.1, v0.2, ..., v1.0, Beyond v1) must match exactly between the two.
specs/*.md cross-references. Every file referenced in PRD or TODO (e.g. specs/byorc-protocol.md, specs/fork-strategy.md, specs/threat-model.md, specs/test-plan.md) must either exist or be clearly tagged as a Phase 0 deliverable yet to be written.
Tier-1 provider list parity. Provider names referenced in PRD §5.1, PRD §13 (v0.1 exit criteria), TODO v0.1, and specs/test-plan.md §4.3 must agree.
Brand parity. No file under the project root references the literal product name as anything other than omw. The codename oh-my-warp is allowed in repo paths and §12.1 explanations only.
Test-plan ↔ phases. specs/test-plan.md §8 per-phase commitments must use the same phase IDs as PRD §13 / TODO.

Procedure

Read PRD.md, TODO.md, and every file under specs/.
For each check above, gather evidence with Grep/Read. Build a table of findings.
Report:
- Drift — items mentioned in one doc but not another (with line refs).
- Broken refs — links/cross-refs that point to files that don't exist (and aren't documented as TBD).
- Orphans — TODO bullets with no corresponding PRD commitment, or PRD commitments with no TODO.
- Brand violations — uses of Warp in product-surface contexts.
Do NOT edit any files. This skill is read-only.

Output format

Spec consistency check
  PRD §3.1 ↔ TODO:        OK | DRIFT (N items)
  PRD §13 ↔ TODO phases:  OK | MISMATCH
  Cross-references:        OK | N broken (list)
  Tier-1 provider parity:  OK | DRIFT (where)
  Brand parity:            OK | N violations (path:line)
  Test-plan phases:        OK | MISMATCH

Verdict: CONSISTENT | DRIFT_DETECTED

<itemized findings if any>

Notes

This skill expects specs/byorc-protocol.md, specs/fork-strategy.md, specs/threat-model.md to be missing during Phase 0 — flag as TBD, not as broken.
Run after every PRD or spec edit. Cheap and fast.

同仓库更多 Skills

同仓库

tech-debt-audit

AndrewWayne/oh-my-warp

Use when the user asks for a debt audit, codebase health check, architecture review, quality assessment of the entire omw repo, or a "what's rotten?" survey. Whole-repo scope, not diff-scoped (use /review for diffs, /simplify for tactical cleanup). Optional argument is a subtree (e.g. "crates/omw-server", "vendor/warp-stripped/app/src/ai_assistant"). User-invoked only — does not auto-trigger.

2026-05-0812

release-build-audit

AndrewWayne/oh-my-warp

Walk every Command::new() spawn site in omw_local code and cross-reference against the bundling steps in scripts/build-mac-dmg.sh (and the Windows equivalent). Use BEFORE running a release build script; this is the audit that would have caught the v0.0.3 keychain-helper and Node-on-PATH ship bugs. Argument is the target version.

2026-05-0712

byorc-protocol-check

AndrewWayne/oh-my-warp

Verify changes touching crates/omw-remote/ or specs/byorc-protocol.md against the BYORC protocol invariants. Use when reviewing a PR that modifies the remote daemon, the pairing flow, the signed-request validator, or the protocol spec itself. Read-only review aid.

2026-04-2912

check-scope

AndrewWayne/oh-my-warp

Verify a branch or PR stays inside PRD §3.1 v1.0 Committed Scope. Use when the user wants to check scope drift before opening a PR, when a contributor asks "is this in scope?", or before merging a non-trivial branch.

2026-04-2912

refresh-cassette

AndrewWayne/oh-my-warp

Walk the provider cassette refresh ritual from specs/test-plan.md §4.4. Use when the user explicitly asks to refresh cassettes for a provider, or when CI flags cassette drift. Argument is the provider name (openai, anthropic, openai-compat, ollama). REFUSES to make real API calls unless OMW_CASSETTE_REFRESH=1.

2026-04-2912

release-checklist

AndrewWayne/oh-my-warp

Walk the pre-release checklist from specs/test-plan.md §7 for a target version. Use when the user is preparing a release (tagging v0.1, v0.2, ..., v1.0), wants to verify release readiness, or asks "are we ready to ship?". Argument is the target version.

2026-04-2912

name	spec-consistency
description	Cross-reference PRD ↔ TODO ↔ specs/*.md for drift, broken cross-links, and orphaned bullets. Use when the user asks to verify documentation consistency, after editing PRD or any spec, before publishing the repo, or when proof-reading.
tools	Read, Grep, Bash

Spec Consistency

Cross-checks that the planning docs agree with each other. The most useful command during the proof-reading phase.

What gets checked

PRD §3.1 ↔ TODO phase headings. Every commitment in PRD.md §3.1 should map to at least one task in TODO.md. Every TODO phase exit criterion should reflect §3.1 wording.
PRD §13 ↔ TODO phases. Phase IDs (Phase 0, v0.1, v0.2, ..., v1.0, Beyond v1) must match exactly between the two.
specs/*.md cross-references. Every file referenced in PRD or TODO (e.g. specs/byorc-protocol.md, specs/fork-strategy.md, specs/threat-model.md, specs/test-plan.md) must either exist or be clearly tagged as a Phase 0 deliverable yet to be written.
Tier-1 provider list parity. Provider names referenced in PRD §5.1, PRD §13 (v0.1 exit criteria), TODO v0.1, and specs/test-plan.md §4.3 must agree.
Brand parity. No file under the project root references the literal product name as anything other than omw. The codename oh-my-warp is allowed in repo paths and §12.1 explanations only.
Test-plan ↔ phases. specs/test-plan.md §8 per-phase commitments must use the same phase IDs as PRD §13 / TODO.

Procedure

Read PRD.md, TODO.md, and every file under specs/.
For each check above, gather evidence with Grep/Read. Build a table of findings.
Report:
- Drift — items mentioned in one doc but not another (with line refs).
- Broken refs — links/cross-refs that point to files that don't exist (and aren't documented as TBD).
- Orphans — TODO bullets with no corresponding PRD commitment, or PRD commitments with no TODO.
- Brand violations — uses of Warp in product-surface contexts.
Do NOT edit any files. This skill is read-only.

Output format

Spec consistency check
  PRD §3.1 ↔ TODO:        OK | DRIFT (N items)
  PRD §13 ↔ TODO phases:  OK | MISMATCH
  Cross-references:        OK | N broken (list)
  Tier-1 provider parity:  OK | DRIFT (where)
  Brand parity:            OK | N violations (path:line)
  Test-plan phases:        OK | MISMATCH

Verdict: CONSISTENT | DRIFT_DETECTED

<itemized findings if any>

Notes

This skill expects specs/byorc-protocol.md, specs/fork-strategy.md, specs/threat-model.md to be missing during Phase 0 — flag as TBD, not as broken.
Run after every PRD or spec edit. Cheap and fast.