---
name: Grace Status
slug: grace-status
category: AI Engineering
description: Grace Status reports GRACE 4 project health from the current .grace context, including graph integrity, verification, active changes, scope conflicts, and migration boundaries. Use it to decide the next safe action without mutating artifacts.
github: "https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-status"
language: TypeScript
stars: 239
forks: 54
install: "npx degit https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-status ~/.claude/skills/grace-status"
installs_to: ~/.claude/skills/grace-status
source_path: skills/grace/grace-status/SKILL.md
collection_size: 15
category_size: 2793
collection_url: "https://dirskills.com/collections/osovv/grace-marketplace"
added: 2026-09-03T06:03:54.163Z
last_synced: 2026-09-03T06:03:54.163Z
canonical_url: "https://dirskills.com/skills/grace-status"
---

# Grace Status

Grace Status reports GRACE 4 project health from the current .grace context, including graph integrity, verification, active changes, scope conflicts, and migration boundaries. Use it to decide the next safe action without mutating artifacts.

**Install:**

```bash
npx degit https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-status ~/.claude/skills/grace-status
```

## README

<skill>
<task>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.</task>

<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`, and `ready-to-execute` with 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>

<commands>
- Pre-implementation active-baseline integrity: `grace lint --path PROJECT --assertions current`
- Parallel decision: `grace lint --path PROJECT --parallel-preflight`
- Status snapshot: `grace status --path PROJECT --with modules --json --fail-on errors`
</commands>

<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>
</skill>