القائمة
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 ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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.
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.
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.
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.
| 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 |
Cross-checks that the planning docs agree with each other. The most useful command during the proof-reading phase.
Phase 0, v0.1, v0.2, ..., v1.0, Beyond v1) must match exactly between the two.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.specs/test-plan.md §4.3 must agree.omw. The codename oh-my-warp is allowed in repo paths and §12.1 explanations only.specs/test-plan.md §8 per-phase commitments must use the same phase IDs as PRD §13 / TODO.PRD.md, TODO.md, and every file under specs/.Grep/Read. Build a table of findings.Warp in product-surface contexts.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>
specs/byorc-protocol.md, specs/fork-strategy.md, specs/threat-model.md to be missing during Phase 0 — flag as TBD, not as broken.