メニュー
Self-health check, doom-loop recovery, and patch propagation workflow for the aicoder-opencode control plane
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | aicoder-unblock-and-patch |
| description | Self-health check, doom-loop recovery, and patch propagation workflow for the aicoder-opencode control plane |
| user-invocable | false |
Maintenance and unblock workflow for the aicoder-opencode control plane.
bun run check (build + tests). Fix any failures before proceeding.make validate-dr-repo and make validate-letta-workspace. Confirm
target paths exist and launchers resolve.make doom-loop-dr-repo. If stalled, proceed to the target unblock
procedure below.When a doom-loop fires on a target:
docs/plans/ active-slice to understand what was in flight..opencode/state/checkpoints/ to see last known
state..state/doom-loop/.When a shared skill or plugin needs updating:
src/plugins/ or
.agents/skills/).bun run check to verify.targets/<target>/overlay/.agents/skills/ shim or content.make validate-<target>.Use when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.