moonspec-plan

Generate implementation plans and design artifacts from single-story feature specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a single-story feature specification into a defensible, repository-aligned implementation plan and the Phase 0/1 design artifacts required to hand off to engineers while validating constitution gates and resolving technical unknowns.

Core Features & Use Cases

  • Plan generation: Populate plan.md from the repository template, record branch and spec inputs, and produce a concise summary, technical context, and project structure.
  • Research and design artifacts: Produce research.md, data-model.md, contracts/, and quickstart.md to resolve unknowns, define testing strategy, and document public interfaces.
  • Governance and validation: Run constitution gate checks, track justified violations in complexity tracking, and surface errors when multiple stories or unresolved clarifications block planning.
  • Use Case: Use when a product or engineering lead needs a TDD-first, testable implementation plan for a single user story before generating tasks.

Quick Start

Run the moonspec-plan skill to generate plan.md, research.md, and supporting design artifacts for the active single-story feature spec.

Frequently Asked Questions about moonspec-plan

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

FAQPage Schema
How do I convert a feature specification into an implementation plan?

To convert a feature specification into an implementation plan, the system parses a single-story spec to generate plan.md, research.md, and data-model.md artifacts while validating constitution gates and resolving technical unknowns.

What is TDD-first implementation planning for a single user story?

TDD-first implementation planning for a single user story is the process of generating design artifacts and test strategies from one independently testable spec, ensuring readiness for task generation before coding begins.

How do I generate data models and contracts from a feature spec?

You generate data models and contracts from a feature spec by validating a single-story specification and outputting data-model.md and contracts directories that document public interfaces alongside the implementation plan.

Does this planning workflow support feature specs with multiple stories?

This planning workflow does not support feature specs with multiple stories. It validates that the specification contains exactly one independently testable user story and surfaces errors if multiple stories or unresolved clarifications block planning.

Can I use this to resolve technical unknowns before generating implementation tasks?

Yes, you can use this to resolve technical unknowns before generating implementation tasks. It identifies unresolved technical questions within the spec and documents their resolutions in a dedicated research.md artifact.

What limitations exist when validating constitution gates for implementation plans?

A key limitation when validating constitution gates is that justified violations must be tracked in complexity tracking, and the planning process halts with errors if multiple stories or unresolved clarifications are detected in the feature spec.