story-traceability

Ensure Acceptance Criteria map to Tasks and Tests for PR-per-story workflow

⭐1stars🔀0forks📁View on GitHub🕐Updated Nov 10, 2025

When & Why to Use This Skill

The Story Traceability skill streamlines the software development lifecycle by ensuring every Acceptance Criterion (AC) is directly mapped to actionable tasks and comprehensive tests. Ideal for teams following a PR-per-story workflow, this tool automates the creation of traceability matrices, guarantees full requirement coverage, and enhances the reviewability of code changes by providing a clear link between user stories and implementation.

Use Cases

  • Automated Coverage Mapping: Generate a comprehensive table linking Acceptance Criteria to tasks and tests, ensuring no requirement is overlooked during the development phase.
  • Documentation Synchronization: Automatically update USER-STORY.md and individual task files with traceability references to maintain a single source of truth for project progress.
  • Pre-Development Gap Analysis: Proactively identify missing test cases or undefined tasks for specific ACs, allowing teams to address requirements gaps before coding starts.
namestory-traceability
descriptionEnsure Acceptance Criteria map to Tasks and Tests for PR-per-story workflow
version0.1.0
tags[planning, QA]

Story Traceability

Purpose

Create a clear AC → Task → Test mapping to guarantee coverage and reviewability.

Behavior

  1. Build a table: AC | Task(s) | Test(s) | Notes.
  2. Insert into USER-STORY.md; add brief references into each TASK-*.md.
  3. Call out missing mappings; propose test names.

Guardrails

  • Every AC must have ≥1 task and ≥1 test.
  • Keep table compact; link file paths precisely.

Integration

  • Project Manager agent; /lazy create-feature output phase.

Example Prompt

Add traceability for US-20251027-001.