derive-acs

Generate acceptance criteria from specs and build a coverage matrix.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gr8routdoors/lit-sdlc --skill derive-acs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: derive-acs
Source: https://github.com/gr8routdoors/lit-sdlc/tree/main/.claude/skills/agent-os/derive-acs
Command: npx skills add https://github.com/gr8routdoors/lit-sdlc --skill derive-acs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the translation of requirements, architectural design, and user stories into precise, testable acceptance criteria, reducing manual effort and miscommunication.

Core Features & Use Cases

  • Context loading and mapping: loads specs/SPEC-{NNN}-{slug}/README.md, specs/SPEC-{NNN}-{slug}/design.md, and specs/SPEC-{NNN}-{slug}/stories.yml to understand scope and derive coverage.
  • Story-to-coverage mapping: analyzes each story to determine required coverage (happy path, validation, edge cases, etc.) and validates alignment with scope.
  • AC generation and file creation: produces one or more AC entries per story and saves them under specs/SPEC-{NNN}-{slug}/acs/.
  • Coverage matrix: builds a traceability matrix linking stories to ACs for verification.

Quick Start

Run the derive-acs skill to start generating acceptance criteria from your SPECs.

Frequently Asked Questions about derive-acs

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

FAQPage Schema
How do I automatically generate acceptance criteria from requirements and architectural designs?

You can automatically generate acceptance criteria from requirements by running a process that loads specification files like README.md, design.md, and stories.yml, analyzes story coverage, and saves the derived ACs into dedicated files.

What is requirements traceability and how does it link user stories to acceptance criteria?

Requirements traceability links user stories to acceptance criteria by building a coverage matrix that maps each story to its derived ACs, ensuring verification of happy paths, validations, and edge cases against the original scope.

How do I structure specs for BDD acceptance criteria derivation?

Structure specs for BDD acceptance criteria derivation by organizing files under a specs/SPEC-{NNN}-{slug} directory, including a README.md, design.md, and stories.yml to provide the necessary scope and architectural context.

What's the best way to ensure test coverage for edge cases when deriving acceptance criteria?

The best way to ensure test coverage for edge cases is to analyze each user story to map required coverage scenarios, validating alignment with the overall scope before generating and saving the final acceptance criteria.

Does automated acceptance criteria generation work with existing architectural design documents?

Yes, automated acceptance criteria generation works with existing architectural design documents by loading your design.md file alongside the README and stories to understand the full context and derive accurate coverage.

Why should I automate deriving acceptance criteria instead of writing them manually?

Automating acceptance criteria derivation reduces manual effort and miscommunication by consistently translating requirements, architectural designs, and user stories into precise, testable ACs with a traceability matrix.