Menu
dure progress report — aggregate per-item roadmap status into per-milestone completion, blockers, and local↔GitHub conflicts.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 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.
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 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 | status |
| description | dure progress report — aggregate per-item roadmap status into per-milestone completion, blockers, and local↔GitHub conflicts. |
| argument-hint | [milestone-id] |
| allowed-tools | Bash Read |
| disable-model-invocation | true |
Scope: $ARGUMENTS (if empty, all milestones)
Goal: per spec §5.3 / E1.5, aggregate local item status (and any pulled GitHub status) into a progress report.
${CLAUDE_PLUGIN_ROOT}/scripts/dure-context.sh to confirm context and the active spec.${CLAUDE_PLUGIN_ROOT}/scripts/dure-status.py — it returns JSON:
{overall, milestones[{id,title,total,completion,counts}], blockers[], conflicts[]}.
Completion is computed from issues (done / total); conflicts come from
.dure/sync/github-status.json when present (written by /dure:sync's pull).milestone-id argument was given, filter to that milestone.Implementation status (E1.5):
dure-status.pyis deterministic and tested (completion math + conflict detection). The GitHub side of conflicts activates once/dure:sync(E1.4) writessync/github-status.json.