About grace-status
A skill that runs GRACE status checks and reports project state without changing artifacts. It summarizes integrity, plans, bundles, drift, module health, and the next safe action.
Key features
- 01Read-only project status reporting
- 02Graph and verification integrity checks
- 03Plan and bundle state summaries
- 04Route-aware drift and blocker reporting
- 05Module health and next-action guidance
Use cases
- 01Checking project readiness before execution
- 02Reviewing plan approval or staleness
- 03Identifying integrity issues and blockers
- 04Choosing a safe next project action
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ osovv/ grace-marketplace --skill grace-statusAfter installing, type/grace-statusin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project README
Run `grace status --path PROJECT --json` and report current GRACE 4 state without mutating artifacts. Module-health summary counts are always evaluated; add `--with modules` only when detailed module records are needed.
<must_report>
- Project kind: GRACE 4, legacy GRACE 3 migration candidate, or missing GRACE; plus context completeness.
- Graph/verification projection integrity, routed coverage, and module counts.
- Active/archive bundle statuses and derived states.
needs-plan,needs-plan-approval,stale-plan,integrity-issues, andready-to-executewith readiness mutually exclusive from stale/integrity states.- Route-aware explained/unexplained drift, scope coexistence warnings, and parallel blockers.
- Module-health load failure as integrity/degraded status rather than a crash.
- The next safe action: lint, migrate, specify, plan, or execute. </must_report>
<hard_rules>Do not edit XML statuses. A draft spec without a plan is normal; an approved spec without a plan needs planning. A stale or integrity-invalid approved plan is never ready.</hard_rules>
Comments
Markdown supported