myna-dev-coverage

Audit feature specs against skill bodies and generate coverage reports.

8|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/agentflock/myna --skill myna-dev-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myna-dev-coverage
Source: https://github.com/agentflock/myna/tree/main/.claude/skills/myna-dev-coverage
Command: npx skills add https://github.com/agentflock/myna --skill myna-dev-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits Myna skills to verify that every feature described in docs/features/*.md has concrete executable coverage within its owning skill, preventing gaps in implementation.

Core Features & Use Cases

  • Maps feature specifications to corresponding skill bodies by reading executable steps (read/decide/write) across skills.
  • Generates a formal coverage report saved to tmp/reviews/coverage-{NNN}.md for traceability and audits.
  • Supports scoped audits via arguments to include specific paths, or uncommitted changes only, for incremental reviews.

Quick Start

Run the audit across all feature skills to generate a coverage report.

Frequently Asked Questions about myna-dev-coverage

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

FAQPage Schema
How do I audit feature coverage to find missing executable steps in my docs?

Feature coverage auditing maps specifications in docs/features/*.md to executable read/decide/write steps within owning skills, producing a FULL/PARTIAL/NONE graded report to pinpoint missing implementation gaps.

What is a feature coverage report and how does it prevent incomplete implementations?

A feature coverage report verifies that every specification in docs/features/*.md has concrete executable coverage within its owning skill, preventing implementation gaps by flagging missing executable steps.

Can I run a scoped feature coverage audit on uncommitted changes only?

Yes, you can run a scoped feature coverage audit by passing specific path arguments, limiting the review to uncommitted changes or specific feature paths for incremental reviews instead of scanning all features.

What architecture and foundation docs do I need to perform a feature spec audit?

To perform a feature spec audit, you need docs/design/architecture.md, docs/features/*.md, and docs/design/foundations.md parsed alongside all relevant skill bodies to produce a comprehensive coverage map and final report.

Where is the feature coverage report saved for traceability and audits?

The formal feature coverage report is saved to tmp/reviews/coverage-{NNN}.md, providing traceability for audits by documenting the FULL/PARTIAL/NONE grades and the comprehensive coverage map.