القائمة
Read-only project health check — framework/manifest drift, .openup/state.json integrity, and aggregation of existing --check validators
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
One-command project setup for OpenUP - interactive initialization wizard
Mark a task as complete, update roadmap, commit changes, and prepare traceability logs
Execute an already-claimed lane's Operations boxes with script/judgment classification — script steps run directly with zero self-brief, judgment steps self-brief and execute. Handles only pick/resume; every other resolve path routes to /openup-next.
Run OpenUP Assess Results at iteration end — check evaluation criteria, demo only completed acceptance-tested work, feed discovered work back, and trigger the milestone review at a phase boundary
Run the phase milestone go/no-go — prepare derived evidence, pause for the human decision via an input-request, and record the milestone (never advance the phase itself)
Begin a new OpenUP iteration with proper phase context and task selection
| name | openup-doctor |
| description | Read-only project health check — framework/manifest drift, .openup/state.json integrity, and aggregation of existing --check validators |
| model | haiku |
| fit | {"great":["downstream maintainer asking is my OpenUP install current and unmodified","pre-flight health check on a fresh clone or in CI without the git hooks","diagnosing a corrupt/misnamed .openup/state.json footgun"],"ok":["a quick is-this-project-well-formed sweep before starting work"],"poor":["fixing anything (doctor is strictly diagnostic — fixes live in sync-from-framework.sh / the owning generators)","what can I work on next (that is /openup-readiness)"]} |
| arguments | [{"name":"framework_path","description":"Optional. Path to a framework baseline clone. Enables byte-level CLI drift detection; without it doctor degrades to version-only (offline).","required":false}] |
Run the read-only project health diagnostic and relay its report. The real
artifact is the deterministic scripts/openup-doctor.py; this skill is a thin
wrapper for the interactive "diagnose my project" ask.
This skill is READ-ONLY. It runs one script that writes nothing, fixes
nothing, and mutates no file. Fixes stay in their owning scripts
(sync-from-framework.sh, sync-status.py, the derived-view generators) — do
not offer to apply them from here.
Mechanical step (
model: haiku). Run the script, relay its output, do not re-derive or second-guess its findings.
Run the diagnostic from the project root:
python3 scripts/openup-doctor.py # offline (version-only drift)
# or, with a baseline clone for byte-level CLI drift detection:
python3 scripts/openup-doctor.py --framework-path <path-to-framework-clone>
# add --json for machine-readable output (CI)
Relay the report. Findings are grouped by severity:
.openup/state.json, a manifest-listed CLI
missing, or a read-only validator that itself failed. Exit code is 1.For each error/warning, point at the owning fix (never run it yourself):
behind-on-version / modified CLI → sync-from-framework.sh; stale derived
view → the named generator (e.g. docs-index.py); corrupt state → manual
repair of .openup/state.json.
scripts/openup-doctor.py — the deterministic diagnostic this skill wraps.docs-eng-process/script-cli-reference.md — the CLI signature.