skills.rest
tikazyq
tikazyqCOMMUNITY
Explore all skills by this author →
GitHub

vs-coverage-check

Audit User Stories coverage by Visual Specifications in design documents.

5|1|Updated Jan 3, 2026
Search Tags:#design#requirements#validation#traceability#coverage#us-vs
One-click install
npx skills add https://github.com/tikazyq/agentic-spec-forge --skill vs-coverage-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vs-coverage-check
Source: https://github.com/tikazyq/agentic-spec-forge/tree/main/AGENTIC_SPEC_FORGE/spec_stage_skill/design/vs-coverage-check
Command: npx skills add https://github.com/tikazyq/agentic-spec-forge --skill vs-coverage-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly rework and failed验收 by ensuring that every User Story (US) has a corresponding Visual Specification (VS) before the CONSTRAINT acceptance phase.

Core Features & Use Cases

  • Automated Coverage Auditing: Scans requirements and design documents to identify missing VS for US.
  • Gap Identification: Generates a clear list of US without corresponding VS.
  • Actionable Recommendations: Provides suggestions for creating the necessary VS.
  • Use Case: Before submitting your design for CONSTRAINT acceptance, run this skill to confirm that all user stories have been translated into visual specifications, avoiding last-minute rejections.

Quick Start

Run the vs-coverage-check skill to audit the coverage of user stories by visual specifications.

Frequently Asked Questions about vs-coverage-check

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

FAQPage Schema
How do I check User Story to Visual Specification coverage before acceptance?▼

To check User Story to Visual Specification coverage, run an automated audit that scans design documents to identify missing VS and generates a coverage report with repair suggestions.

How do I find missing Visual Specifications for my User Stories?▼

You can find missing Visual Specifications by auditing design documents to identify US lacking corresponding VS, which generates a gap list and actionable recommendations to create the necessary VS.

Why do I need to validate US to VS traceability before CONSTRAINT acceptance?▼

Validating US to VS traceability prevents costly rework and failed acceptance by ensuring every User Story has a corresponding Visual Specification before entering the CONSTRAINT acceptance phase.

What is the best way to ensure 100% requirements coverage in design documents?▼

The best way to ensure 100% requirements coverage is to run an automated auditing process that scans requirements and design documents, identifies gaps where US lack VS, and provides repair suggestions.

When should I run a User Story coverage audit in my design workflow?▼

You should run a User Story coverage audit after design document creation and before CONSTRAINT acceptance to confirm all user stories have been translated into visual specifications.

Can I get repair suggestions for User Stories lacking Visual Specifications?▼

Yes, auditing US to VS coverage generates a report that not only identifies US lacking corresponding VS but also provides actionable recommendations for creating the necessary visual specifications.

Related Skills

Explore More Design & Creative Skills→
wahabmalikwahabmalik

bmad-create-epics-and-stories

Decompose product requirements into detailed epics and user stories.

Community
Advanced
tikazyqtikazyq
5

entry-point-check

Validate VS entry_points against SPEC_PRJ_ENTRYPOINTS and report missing entries.

Community
Intermediate
apokamoapokamo
12

issue-review-code

Enforce design-consistent code reviews with lint, mypy, and pytest validation.

Community
Advanced
gotalabgotalab
406

notion-spec-to-implementation

Transforms Notion spec documents into actionable implementation plans and tasks with progress tracking.

Community
Basic