spec-play-coverage

Opens a browser playground visualizing spec-to-code coverage from @spec anchor grep data.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-play-coverage-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-play-coverage
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-play-coverage
Command: npx skills add https://github.com/julien-m/livespec --skill spec-play-coverage-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams using spec-driven development lose visibility into which requirements are actually implemented in code. This Skill launches an interactive coverage playground that greps the codebase for @spec anchors and displays which functional requirements are mapped and which are unmapped. ## Core Features & Use Cases - Automatic Feature Resolution: Resolves the target feature from a command argument, the current git branch, or an interactive selection prompt. - Source Directory Detection: Scans common source directories (app/, src/, lib/, packages/) and picks the one containing the most @spec anchor matches. - Live Coverage Playground: Runs a shell script that greps anchors, encodes the results, and opens a browser-based coverage matrix showing mapped and unmapped requirements. - Use Case: After implementing a feature, run the command to instantly see which functional requirements lack @spec anchors in the source code, then add the missing traceability links. ## Quick Start Ask the AI to run /spec-play-coverage for your current feature to open the spec coverage playground in a browser with live anchor data.

Frequently Asked Questions about spec-play-coverage

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

FAQPage Schema
How do I check spec-to-code coverage for a feature?

Run /spec-play-coverage with an optional feature name. It resolves the feature directory, greps the source tree for @spec anchors, and opens a browser playground showing which requirements are mapped and which are unmapped.

How does the coverage playground detect the source directory?

It checks common directories like app/, src/, lib/, and packages/ at the project root. If multiple exist, it greps each for @spec FR- anchors and selects the one with the most matches, falling back to the project root if none are found.

Can I run spec coverage without opening a browser?

Yes, in headless environments pass the --no-open flag to skip launching the browser. You can then inspect the generated coverage data manually in the playground/coverage directory.

Why does the coverage playground show unmapped requirements?

Unmapped requirements appear when functional requirements in the spec lack corresponding @spec anchors in the source code. Add @spec anchor comments to the implementing code files to close the traceability gap.

What happens if no feature name is provided to the command?

The command detects the feature from the current git branch name following the feature/NNN-name convention. If that fails, it lists all available features under .specs/features/ and asks you to choose one.