Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

survey

Étoiles0

Forks0

Mis à jour25 juin 2026 à 13:43

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

choo121600

choo121600/dure

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

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

/dure:survey — State Survey (M3 discovery engine)

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).

Boundary (MUST hold)

Report-only. This skill MUST NOT write to .dure/roadmap/ and MUST NOT create issues. Signals are evidence; the user (or /dure:interview / /dure:plan) decides what becomes work.
Disjoint from the other scanners: 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).

Procedure

Run ${CLAUDE_PLUGIN_ROOT}/scripts/dure-context.sh to confirm the target repo.
Run ${CLAUDE_PLUGIN_ROOT}/scripts/dure-survey.py → JSON {status, counts, findings:[{check, severity, id, message}]}.
Present the findings in the user's language, grouped by check (closable-milestone, empty-epic), each with its id and message. Lead with the counts summary. If findings is empty, say so plainly.
Offer next actions without auto-acting:
- for a closable-milestone, confirm its descendants and close the milestone (a status update, not new work),
- for an empty-epic, feed it into /dure:interview "<epic>" to decompose it, or drop it,
- note signals to fold into /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.

Plus depuis ce dépôt

même dépôt

direction

choo121600/dure

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.

2026-06-250

audit

choo121600/dure

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.

2026-06-240

interview

choo121600/dure

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.

2026-06-240

sync

choo121600/dure

dure sync — idempotently mirror the local roadmap to GitHub Issues/Milestones. plan/apply separation; structure pushed, status pulled, conflicts reported. gh CLI first.

2026-06-240

status

choo121600/dure

dure progress report — aggregate per-item roadmap status into per-milestone completion, blockers, and local↔GitHub conflicts.

2026-06-240

plan

choo121600/dure

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.

2026-06-240

/dure:survey — State Survey (M3 discovery engine)

Boundary (MUST hold)

Report-only. This skill MUST NOT write to .dure/roadmap/ and MUST NOT create issues. Signals are evidence; the user (or /dure:interview / /dure:plan) decides what becomes work.

Disjoint from the other scanners: 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).

Procedure

Run ${CLAUDE_PLUGIN_ROOT}/scripts/dure-context.sh to confirm the target repo.

Run ${CLAUDE_PLUGIN_ROOT}/scripts/dure-survey.py → JSON {status, counts, findings:[{check, severity, id, message}]}.

Present the findings in the user's language, grouped by check (closable-milestone, empty-epic), each with its id and message. Lead with the counts summary. If findings is empty, say so plainly.

Offer next actions without auto-acting:

for a closable-milestone, confirm its descendants and close the milestone (a status update, not new work),
for an empty-epic, feed it into /dure:interview "<epic>" to decompose it, or drop it,
note signals to fold into /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.