moonspec-verify

Verify Moon Spec implementations against specs, plans, and test evidence.

12|5|Updated Jan 14, 2025
One-click install
npx skills add https://github.com/MoonLadderStudios/MoonMind --skill moonspec-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moonspec-verify
Source: https://github.com/MoonLadderStudios/MoonMind/tree/main/.agents/skills/moonspec-verify
Command: npx skills add https://github.com/MoonLadderStudios/MoonMind --skill moonspec-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, read-only verification workflow to determine whether a completed Moon Spec implementation fulfills the original request, single-story spec, plan, tasks, constitution rules, and required tests so teams can confidently close a spec or identify remaining work.

Core Features & Use Cases

  • Requirement-to-code verification: Cross-check FR-, SCN-, SC-, and DESIGN-REQ- items against production code, wiring, and test evidence.
  • Test and evidence audit: Inspect unit and integration test suites, record which commands were run or skipped, and classify each requirement as VERIFIED, PARTIAL, MISSING, CONFLICT, or NO_DETERMINATION.
  • Hook awareness and conservative verdicts: Detect and report optional or mandatory pre/post verify hooks, require .specify/memory/constitution.md, and prefer conservative verdicts when evidence is incomplete.
  • Use case: Final audit before merging a feature branch to ensure all acceptance scenarios and constitution MUSTs are satisfied.

Quick Start

Run a read-only verification of the feature at path /path/to/feature/spec.md and produce a concise MoonSpec Verification Report with verdict, confidence, and actionable gaps.

Frequently Asked Questions about moonspec-verify

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

FAQPage Schema
How do I verify code implementation against original specifications and requirements?

To verify code implementation against specifications, cross-check requirement items against production code and test evidence, then classify each requirement as VERIFIED, PARTIAL, MISSING, CONFLICT, or NO_DETERMINATION.

What is a specification verification audit for feature branch merging?

A specification verification audit inspects repository files read-only to determine whether a completed implementation fulfills its original spec, plan, tasks, and constitution rules before merging a feature branch.

How do I audit test coverage and evidence for integration tests?

Audit test coverage and evidence by inspecting unit and integration test suites, recording which documented test commands were run or skipped, and matching the results to requirement mappings.

Does specification verification require a constitution file to run?

Yes, specification verification requires the `.specify/memory/constitution.md` file to be present to check implementation completeness against constitution MUSTs and mandatory pre/post verify hooks.

Can I run test commands during a read-only code review verification?

You can optionally execute safe, documented test commands during a read-only code review verification, but the process prefers conservative verdicts like NO_DETERMINATION when evidence is incomplete.

What are the limitations when verification evidence is incomplete or conflicting?

When verification evidence is incomplete or conflicting, the limitation is a conservative classification into PARTIAL, MISSING, CONFLICT, or NO_DETERMINATION rather than a passing verdict.