skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:spec-criteria

Generate and lock acceptance criteria with sequential AC-IDs into FRD.md.

Updated Mar 26, 2026
Search Tags:#requirements traceability#acceptance criteria#spec generation#E2E planning#FRD#revision management#AC-IDs
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-spec-criteria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:spec-criteria
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/spec-criteria
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-spec-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly turn a feature description into precise, testable acceptance criteria that are uniquely identified with AC-IDs and stored in your FRD.

Core Features & Use Cases

  • Acceptance-criteria generation: Produces a numbered AC table with verb-first, non-overlapping, testable behaviors.
  • AC-ID continuity: Continues from the existing watermark (and preserves retired criteria) to maintain traceability across revisions.
  • Revision-safe approvals: Prompts for user approval, then writes the canonical Acceptance Criteria and changelog sections into FRD.md.

Quick Start

Run the command /spec-criteria user notification preferences to generate and lock acceptance criteria for that feature into docs/{feature}/FRD.md.

Frequently Asked Questions about wa:spec-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate acceptance criteria with unique IDs for my FRD?▼

To generate acceptance criteria with unique IDs, the Skill reads your feature scope from an existing FRD.md, produces a canonical numbered AC table with verb-first testable behaviors, and locks each row with sequential AC-IDs.

How does requirements traceability work when revising existing acceptance criteria?▼

Requirements traceability is maintained by continuing AC-ID sequences from the existing watermark, preserving retired criteria rows, and appending an AC Changelog with revision history updates to prevent ID reuse.

Can I use this to write acceptance criteria if I only have a feature description and no FRD?▼

You need an existing FRD.md artifact defining scope and candidates to use this workflow, as the Skill writes the generated acceptance criteria table and changelog directly into that file during a revision-safe approval process.

What is the best way to lock acceptance criteria for E2E test planning?▼

The best way to lock acceptance criteria for E2E planning is generating non-overlapping, testable behaviors with sequential AC-IDs, prompting for user approval, and then writing the locked canonical table into your FRD.md.

How do I prevent AC-ID reuse when managing multiple feature revisions?▼

AC-ID reuse is prevented by reading the existing revision state and watermark from your FRD.md and optional DISCOVERY.md, then continuing the sequence while preserving retired rows in the updated changelog.

Related Skills

Explore More Product & Management Skills→
jeremy-newhousejeremy-newhouse

wa:spec-questions

Identify and triage specification gaps as blocking or non-blocking questions.

Community
Intermediate
aws-samplesaws-samples
21

test-case-generator

Generate structured test cases from spec.md acceptance criteria with 1:1 traceability.

Official
Intermediate
adolfoaranaes12adolfoaranaes12
2

trace-requirements

Generate bidirectional traceability matrices mapping acceptance criteria to implementation evidence and tests.

Community
Advanced
loianeloiane
50

ears-spec-authoring

Draft stable acceptance criteria using EARS-lite shapes with AC-NNN IDs.

Community
Intermediate