メニュー
Inspect sd0x Dev Flow state and resume the next required review or verification action. Use when a task was interrupted, after compaction, when asked what remains, or when the auto-loop reports an unfinished gate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | remind |
| description | Inspect sd0x Dev Flow state and resume the next required review or verification action. Use when a task was interrupted, after compaction, when asked what remains, or when the auto-loop reports an unfinished gate. |
Resolve this skill's installed directory from the current SKILL.md, then run:
node "<this-skill-directory>/scripts/status.js"
Inspect reason before following next_action:
reason is reviewer-unavailable, do not run $sd0x-dev-flow-codex:review again on the same fingerprint. Report that the failed gate and reviewer ledger remain intact, then ask the user before a user-authorized reset. Restoring reviewer identities may require a new Codex task, but restart alone does not clear evidence; reset or a genuine fingerprint change is still required.reason is review-in-progress, wait for every terminal reviewer result. If the ledger is stale, do not spawn replacements; ask the user before reset.reason is review-findings-remain, inspect and fix the recorded findings, then run $sd0x-dev-flow-codex:review against the new fingerprint.reason is review-required, run $sd0x-dev-flow-codex:review.For the remaining actions, follow next_action exactly:
verify: run $sd0x-dev-flow-codex:verify.complete: report that all required gates pass for this fingerprint.The loop has no retry ceiling. If the runtime evidence is stale or the user wants
to restart the workflow, explain that $sd0x-dev-flow-codex:reset clears only
sd0x gate evidence and requires explicit user invocation.
Repository-only probe used to determine whether Codex can keep a skill manually invokable while excluding it from implicit routing.
Create, update, batch-sync, or scan date-prefixed single-task request tickets under docs/features/*/requests/. Use for breaking a tech spec into execution tickets, tracking acceptance-criteria progress, finding incomplete or stale requests, or independently verifying one ticket's acceptance criteria. Do not use for feature-wide requirements, technical design, or implementation.
Implement a non-trivial feature end to end with scoped exploration, explicit acceptance criteria, incremental edits, independent review, and deterministic verification. Use when the user asks to build or extend behavior rather than make a tiny isolated edit.
Review the current dirty worktree with a configured Codex-first or Claude primary subagent plus one independent read-only Codex test perspective, fix actionable findings, and record a fingerprint-bound review gate. Use before finishing code or documentation changes, after fixes invalidate prior review, or when the sd0x stop hook requests review.
Install or refresh sd0x Dev Flow project guidance and custom reviewer agents in the current repository. Use when configuring this Codex plugin for a repo, onboarding a project, or repairing missing sd0x AGENTS.md and .codex/agents files.
Create or update GitHub PR with gh CLI. Auto-extracts ticket ID from branch name, generates title/summary from commits. Auto-detects existing PR and switches to update mode. Default: --dry-run (show command, don't execute). Use when: user asks to open/create/update a PR, says /create-pr, wants to refresh PR description after new commits, or says 'update pr', 'update PR title', 'refresh PR body'.