DevFoundry/specs/archive/SPEC-003-process-hardening.md

SPEC-003: Process Hardening

• Status: COMPLETED
• Stack: DevFoundry process documentation
• Target Files: CLAUDE.md, README.md, specs/.spec-counter, specs/templates/spec-template.md, .devfoundry/skills/technical-spec.md, docs/process-checks.md

---

1. Business Context & Goal

The DevFoundry workflow is usable, but the latest repo review identified several small hardening changes that would make spec creation, framework guidance, no-schema-change handling, abandoned specs, and repeatable process verification clearer. These updates are documentation/template-only and do not affect application code.

No other active specs exist, so there are no target-file conflicts.

2. Acceptance Criteria (Given / When / Then)

• AC-1: Given an agent creates a new spec, when it uses spec-template.md, then the spec artifact itself includes a Spec Creation Checklist.
• AC-2: Given an agent reads operational directives before ASP Classic work, when it checks CLAUDE.md, then it sees the sanctioned RouteKit Classic ASP framework exception/reference.
• AC-3: Given a docs-only, UI-only, or otherwise non-schema spec is drafted, when the agent fills the template, then the template provides an explicit no-schema-change rollback pattern.
• AC-4: Given a draft spec is cancelled, when an agent reads the process docs, then there is an explicit ABANDONED status and abandonment procedure that preserves the spec ID.
• AC-5: Given an agent wants to verify process docs after an update, when it reads docs/process-checks.md, then it has repeatable rg checks for naming, status, checklist, timestamp, and RouteKit guidance.

3. Technical Design & Contracts

• Data Model / Schema Changes: None. Rollback is a git revert of documentation changes.
• Functions / APIs / Interfaces: None.
• Architecture: Documentation-only process update.
• Error Handling Strategy: Preserve existing safety gates and avoid weakening any rule. New guidance must be consistent with existing lifecycle and counter rules.

4. Implementation Plan (Atomic Steps, TDD-ordered)

• Step 1 (verification authoring): Write this spec and verification checklist before modifying process docs — files: specs/active/SPEC-003-process-hardening.md, specs/.spec-counter — completed: 2026-08-19 22:42
• Step 2 (implementation): Add spec creation checklist and no-schema rollback pattern — files: specs/templates/spec-template.md — completed: 2026-08-19 22:44
• Step 3 (implementation): Add RouteKit operational guidance and abandoned-spec process — files: CLAUDE.md, README.md, .devfoundry/skills/technical-spec.md — completed: 2026-08-19 22:44
• Step 4 (implementation): Add repeatable process verification checklist — files: docs/process-checks.md, README.md — completed: 2026-08-19 22:44
• Step 5 (verification): Run repeatable checks and confirm acceptance criteria — files: listed target files — completed: 2026-08-19 22:45

5. Verification & Regression Plan

• Verify AC-1 by confirming spec-template.md includes a Spec Creation Checklist section.
• Verify AC-2 by confirming CLAUDE.md references RouteKit and .devfoundry/references/asp-classic-framework.md.
• Verify AC-3 by confirming spec-template.md includes the exact no-schema rollback pattern.
• Verify AC-4 by confirming README and technical-spec document ABANDONED without reusing IDs.
• Verify AC-5 by confirming docs/process-checks.md exists and contains repeatable rg checks.

6. Retrospective

Filled by the Process Improver per .devfoundry/skills/process-retrospective.md, after QA approval and before archiving.

• What worked: The new docs/process-checks.md made verification straightforward, and the checks caught one small regex mismatch before closeout.
• Friction (rule/reference/interview gap, or none): none
• Logged in .devfoundry/improvement-log.md: yes