メニュー
dure survey — run the deterministic state survey and surface forward-looking planning signals (closable milestones, empty epics) as evidence for /dure:interview and /dure:plan. Report-only; never creates issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
dure direction — gather survey/audit/status evidence, run a deep interview that converges a project direction, write a validated .dure/directions/<slug>.md proposal, and hand the chosen direction to /dure:plan. Report-only at the validator boundary; never writes the roadmap.
dure audit — run the deterministic repo scanner and surface findings (debt / missing-test / progress-consistency signals) as evidence for /dure:interview and /dure:plan. Report-only; never creates issues.
dure deep interview — interview a vague requirement until understanding converges quantitatively, then crystallize it into .dure/specs/<slug>.md. Four traits — evidence-grounded, red-team, auto-research, quantitative convergence gate.
dure sync — idempotently mirror the local roadmap to GitHub Issues/Milestones. plan/apply separation; structure pushed, status pulled, conflicts reported. gh CLI first.
dure progress report — aggregate per-item roadmap status into per-milestone completion, blockers, and local↔GitHub conflicts.
dure decomposition — decompose the active fixed spec into milestone/epic/issue per-item files (source of truth), review them, and regenerate the index. Every issue gets a non-empty, testable acceptance criterion.
| name | survey |
| description | dure survey — run the deterministic state survey and surface forward-looking planning signals (closable milestones, empty epics) as evidence for /dure:interview and /dure:plan. Report-only; never creates issues. |
| argument-hint | |
| allowed-tools | Bash Read |
| disable-model-invocation | true |
Goal: per specs/dure-survey.md, run the deterministic state survey and present its forward-looking planning signals as evidence for direction-setting. The report runs in the user's language; artifacts stay English (ADR-0007).
.dure/roadmap/ and MUST NOT create issues.
Signals are evidence; the user (or /dure:interview / /dure:plan) decides what becomes work.dure-doctor owns integrity (schema/hierarchy/orphans),
dure-audit owns debt signals, dure-status owns completion — dure-survey owns forward-looking
planning signals (what action is now available).${CLAUDE_PLUGIN_ROOT}/scripts/dure-context.sh to confirm the target repo.${CLAUDE_PLUGIN_ROOT}/scripts/dure-survey.py
→ JSON {status, counts, findings:[{check, severity, id, message}]}.check
(closable-milestone, empty-epic), each with its id and message. Lead with the counts
summary. If findings is empty, say so plainly.closable-milestone, confirm its descendants and close the milestone (a status update,
not new work),empty-epic, feed it into /dure:interview "<epic>" to decompose it, or drop it,/dure:plan.
Let the user choose; do not create issues or edit the roadmap.Implementation status: wraps the tested
scripts/dure-survey.py(2 signals: closable-milestone, empty-epic). The subjective direction-proposal layer (/dure:direction, behind a redteam sign-off gate) is a later M3 increment, kept out of this report-only slice.