メニュー
Reproduce, isolate, fix, and re-test regressions or runtime failures with bounded evidence gathering, one implementation writer, and outcome-based verification. Use with godmode-workflow when a failure needs diagnosis before repair.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create controlled, local-first document case files with immutable intake, native PDF extraction, page-scoped OCR escalation, evidence anchors, validation gates, and reproducible archives. Use when Codex must organize or verify sensitive tax, legal, compliance, audit, or administrative paperwork without silently installing tools, uploading documents, submitting forms, deleting originals, or treating model output as verified evidence.
Route cross-domain Codex work through bounded advisory specialists with frozen ownership and explicit handoffs. Use with godmode-workflow when runtime, workflow, governance, quality, documentation, or CI concerns need separate analysis.
Build a disposable local-only prototype through a fast single-writer loop with mandatory watermarks and end-to-end outcome evidence. Use only when production correctness, security review, and release readiness are explicitly deferred.
Perform a findings-first code, architecture, contract, or release-risk review with bounded read-only specialists and evidence-backed severity. Use when the requested outcome is assessment rather than implementation.
Orchestrate non-trivial Codex delivery through governance and capability preflight, bounded parallel discovery, a frozen single-writer contract, independent validation, outcome evidence, and release handoff. Use for complex implementation, migration, or release work that benefits from coordinated subagents.
Apply conservative best practices for SwiftUI work on macOS and iOS, including state flow, target-safe changes, and focused Xcode validation.
| name | godmode-debug |
| description | Reproduce, isolate, fix, and re-test regressions or runtime failures with bounded evidence gathering, one implementation writer, and outcome-based verification. Use with godmode-workflow when a failure needs diagnosis before repair. |
Use this skill with $godmode-workflow. Keep the failing behavior as the
primary contract from discovery through verification.
runtime_platform for toolchain or OS behavior and
researcher for source or repository evidence.builder the smallest safe fix. Do not parallelize tracked-file
writes.validator and tester independently against the original failing path
and the surrounding regression surface.Every delegated task must declare objective, inputs, required output, write
scope, done criterion, and escalation condition as defined by
$godmode-workflow.
If evidence disproves the hypothesis, return to isolation with the new facts; do not stack speculative fixes.