ac-lock
Phase 4.0 — Acceptance Criteria lock checkpoint before implementation. Consolidates all ACs from PRD, TechSpec, and Tasks, presents to user for confirmation, and saves the locked AC list to accepted-criteria.md. Implementation only starts after explicit user confirmation.
npx skills add majiayu000/claude-skill-registry --skill ac-lock --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AC Lock Checkpoint Runs **automatically as Phase 4.0**, after Tasks Validation and before the first implementation task. Purpose: give the user one final explicit confirmation that the Acceptance Criteria represent what they actually want — before any implementation begins. ## Position in flow ``` [Tasks Validation] ↓ [AC Lock Checkpoint] ← THIS SKILL ↓ Per-Task: implementation ``` ## Entry conditions - `prd.md`, `techspec.md`, and `tasks.md` must exist in `tasks/prd-{slug}/` - Generates `accepted-criteria.md` in `.claude/feature-state/{slug}/` - If `accepted-criteria.md` already exists (resume case): skip extraction, ask user to confirm current locked ACs or unlock to re-confirm - Implementation **must not start** until this file is saved --- ## Step 1: Extract and Consolidate ACs ### Sources Read ACs from all three documents: **From `prd.md`:** - "Goals" or "Objectives" section (functional success criteria) - "Acceptance Criteria" section (if present) - "Success Metrics" section (if present) **From `techspec.md`:** - "Validation & Testing Plan" section - "Acceptance Criteria" section (if present) - Non-functional requirements that can be verified **From `tasks.md`:** - "Accepta
- Position in flow
- Entry conditions
- Step 1: Extract and Consolidate ACs
- Sources
- Deduplication
- Classification
- Step 2: Present to User
- Step 3: Interactive Adjustment
- "adjust N" — edit one AC
- "add" — add a missing AC
- "remove N" — remove an AC
- "show-sources" — show provenance
- Step 4: Lock and Persist
- Step 5: PR Coverage Verification
What does the ac-lock skill do?
Phase 4.0 — Acceptance Criteria lock checkpoint before implementation. Consolidates all ACs from PRD, TechSpec, and Tasks, presents to user for confirmation, and saves the locked AC list to accepted-criteria.md. Implementation only starts after explicit user confirmation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ac-lock --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.