moonspec-specify

Convert natural language requests into single-story Moon Spec specifications with DESIGN-REQ mappings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts informal feature requests or referenced declarative designs into a single, testable Moon Spec specification and a ready feature directory, removing ambiguity and preserving source requirements for verification.

Core Features & Use Cases

  • One-story spec generation: Produce exactly one independently testable user story with measurable success criteria and acceptance scenarios.
  • Source-backed requirement mapping: Read referenced design artifacts, extract concrete DESIGN-REQ-* items, and map them to functional requirements with scope annotations.
  • Repository scaffolding and validation: Initialize a specs/ feature directory, copy the spec template, write .specify/feature.json, and create a requirements quality checklist for iterative validation and post-spec hooks.
  • Use Case: Turn a product manager's natural language request or a contract section into a validated spec.md and checklist, ready for planning and verification.

Quick Start

Use the moonspec-specify skill to create a single-story Moon Spec spec from the provided feature request or referenced design.

Frequently Asked Questions about moonspec-specify

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

FAQPage Schema
How do I convert a natural language feature request into testable acceptance criteria?

To convert a natural language feature request into testable acceptance criteria, you can generate a single-story Moon Spec specification that extracts concrete requirements with measurable success criteria and acceptance scenarios.

How do I map design artifacts to functional requirements for a user story?

Mapping design artifacts to functional requirements involves reading referenced source files, extracting concrete DESIGN-REQ IDs, and linking them to testable requirements with scope annotations within a populated spec template.

What is the best way to scaffold a feature directory for specification validation?

Scaffolding a feature directory for specification validation is done by initializing a specs/ folder, copying the spec template, writing a .specify/feature.json file, and producing a requirements quality checklist.

Can I create a single independently testable user story from a contract section?

Yes, you can create a single independently testable user story from a contract section by applying specification generation to the referenced declarative design while preserving original input and source mappings.

Why does my feature specification need a requirements quality checklist?

A requirements quality checklist is needed to provide iterative validation for your feature specification, ensuring that the generated user story and acceptance scenarios remain testable and aligned with source artifacts.

Does specification generation work without referenced design source files?

Specification generation works with direct natural language feature requests, but when referenced design source files are available, it reads them to extract concrete DESIGN-REQ items and preserve source mappings.