kn-verify

Run SDD validation and generate coverage status reports with warnings and fixes.

234|50|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/knowns-dev/knowns --skill kn-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kn-verify
Source: https://github.com/knowns-dev/knowns/tree/main/.agent/skills/kn-verify
Command: npx skills add https://github.com/knowns-dev/knowns --skill kn-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The kn-verify skill streamlines SDD verification and coverage reporting by providing an integrated workflow to validate specs, link tasks to specs, and surface coverage gaps within a project.

Core Features & Use Cases

  • Validate SDD compliance: run sdd-aware validation to measure specs and task alignment.
  • Generate a Coverage Report: produce a consolidated view of specs, tasks, status, and warnings.
  • Guided remediation: present actionable fixes and steps to improve coverage.

Quick Start

Run the verification workflow using the CLI: knowns validate --sdd --plain or via MCP calls to generate a status report and suggested actions.

Frequently Asked Questions about kn-verify

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

FAQPage Schema
How do I validate SDD compliance and check task alignment for my specs?

To validate SDD compliance, you can run the `knowns validate --sdd` command to measure spec and task alignment, which generates a detailed status report highlighting coverage gaps and warnings.

What is the best way to generate a coverage report for spec-driven development?

Generating a coverage report for spec-driven development involves running an SDD-aware validation workflow that produces a consolidated view of specs, tasks, statuses, and actionable warnings for remediation.

Can I get guided remediation suggestions for missing spec coverage?

Yes, SDD verification workflows provide guided remediation by surfacing coverage gaps and presenting actionable fixes and steps to improve spec coverage directly within the status report.

How does SDD validation handle unlinked tasks within a project?

SDD validation links tasks to specs and surfaces coverage gaps within the project, identifying unlinked tasks in the status report and suggesting targeted fixes to ensure full alignment.

Do I need MCP calls to run SDD verification, or can I use the CLI?

You do not need MCP calls exclusively; you can run SDD verification using the CLI with `knowns validate --sdd --plain` or execute the workflow via MCP calls to generate the status report.