# Process Checks

Use these repeatable checks after changing DevFoundry workflow docs, templates, skills, or personas. Run them from the repository root.

## Filename Convention
Confirm live process docs and templates use the canonical `SPEC-<id>-<short-name>.md` convention and do not reintroduce stale patterns:

```powershell
rg "specs/active/<id>-|specs/archive/<id>-|SPEC-<id>-<name>|specs/active/<id>\.md|specs/archive/<id>\.md" AGENTS.md README.md CLAUDE.md .devfoundry specs\templates -g "*.md"
```

Expected result: no matches.

## Status Values
Confirm status guidance includes the lifecycle statuses, including cancelled draft handling:

```powershell
rg "DRAFT|APPROVED|IN PROGRESS|REVISED|COMPLETED|ABANDONED" README.md specs\templates\spec-template.md .devfoundry\skills\technical-spec.md
```

Expected result: each status appears in the appropriate status table, template, or procedure.

## Spec Readiness
Confirm readiness guidance exists in both the spec-generation skill and the spec artifact template:

```powershell
rg "Spec Readiness Checklist|Spec Creation Checklist|No schema changes; rollback is git revert|completed: <YYYY-MM-DD HH:MM>" README.md .devfoundry\skills\technical-spec.md specs\templates\spec-template.md
```

Expected result: all four phrases appear.

## RouteKit ASP Classic Guidance
Confirm ASP Classic framework guidance is discoverable from the agent entry points:

```powershell
rg "RouteKit|asp-classic-framework\.md|core/" AGENTS.md CLAUDE.md .devfoundry\references\asp-classic-framework.md
```

Expected result: `AGENTS.md`, `CLAUDE.md`, and the RouteKit reference match.

## Retrospective Log
Confirm the improvement log keeps append-only entries while allowing the tally table to change:

```powershell
rg "Friction Tally below is the one mutable|LOGGED|ESCALATED|APPLIED" .devfoundry\improvement-log.md
```

Expected result: the mutable-tally rule and retrospective statuses are present.