os-status: unified /os-status:fix setup/update skill (ADR-026) #21

New Issue

Closed

opened 2026-07-12 19:43:33 +00:00 by jared · 1 comment

jared commented

2026-07-12 19:43:33 +00:00

Owner

What to build

New skill `/os-status:fix` in `plugins/os-status/` — the unified project setup/update command decided in ADR-026 (docs/memory-system/03-architecture-decisions.md).

Runs the same check registry as the SessionStart hook (`hooks/checks.py`), then for each non-ok result drives the owning plugin's remediation: `/os-adr:init`, `/os-vault:onboard-project`, hub-note creation, os-backlog routing skill (#14) once built.
Idempotent: re-running on a configured project is the update path — no separate update command.
Each `Check` gains a remediation pointer so check + fix live in one registry.
SessionStart warn output suggests `/os-status:fix` as the single entry point (per-check detail stays).
`.cc-os/config` gains a `version` key stamped by fix; future check can warn on outdated config.
Human gates preserved for decision-bearing steps (tracker destination, graphify ignore-list confirmation); mechanical steps run autonomously.
Consider adding a missing-project-graph check (no `graphify-out/`) so graph onboarding gets the same nudge treatment.

Acceptance criteria

`/os-status:fix` on a bare project walks every failing check to resolution or an explicit human gate
Re-run on a configured project is a no-op (reports "up to date")
SessionStart warnings name `/os-status:fix` as the entry point
`version` key written to `.cc-os/config`
Tracker remediation delegates to the routing skill (blocked by #14 for that step only)
Tests per os-status conventions; `bin/refresh-plugins` run after

Blocked by

Partially #14 (tracker remediation step only — everything else can ship first).

## What to build New skill \`/os-status:fix\` in \`plugins/os-status/\` — the unified project setup/update command decided in ADR-026 (docs/memory-system/03-architecture-decisions.md). - Runs the same check registry as the SessionStart hook (\`hooks/checks.py\`), then for each non-ok result drives the owning plugin's remediation: \`/os-adr:init\`, \`/os-vault:onboard-project\`, hub-note creation, os-backlog routing skill (#14) once built. - Idempotent: re-running on a configured project is the update path — no separate update command. - Each \`Check\` gains a remediation pointer so check + fix live in one registry. - SessionStart warn output suggests \`/os-status:fix\` as the single entry point (per-check detail stays). - \`.cc-os/config\` gains a \`version\` key stamped by fix; future check can warn on outdated config. - Human gates preserved for decision-bearing steps (tracker destination, graphify ignore-list confirmation); mechanical steps run autonomously. - Consider adding a missing-project-graph check (no \`graphify-out/\`) so graph onboarding gets the same nudge treatment. ## Acceptance criteria - [ ] \`/os-status:fix\` on a bare project walks every failing check to resolution or an explicit human gate - [ ] Re-run on a configured project is a no-op (reports "up to date") - [ ] SessionStart warnings name \`/os-status:fix\` as the entry point - [ ] \`version\` key written to \`.cc-os/config\` - [ ] Tracker remediation delegates to the routing skill (blocked by #14 for that step only) - [ ] Tests per os-status conventions; \`bin/refresh-plugins\` run after ## Blocked by Partially #14 (tracker remediation step only — everything else can ship first).

jared commented

2026-07-12 19:54:22 +00:00

Author

Owner

Shipped in commit 696aefc (ADR-026, commit ba34e54). /os-status:fix built: --json check runner, remediation pointers, project-graph-present + config-version-current checks, version= stamping, banner entry point. Suite 64/64. All acceptance criteria met; tracker step delegates to /os-backlog:route (built same day).

Shipped in commit 696aefc (ADR-026, commit ba34e54). /os-status:fix built: --json check runner, remediation pointers, project-graph-present + config-version-current checks, version= stamping, banner entry point. Suite 64/64. All acceptance criteria met; tracker step delegates to /os-backlog:route (built same day).