mspec-design

Generate and validate mspec design documentation artifacts against the Constitution.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/tubone24/mspec --skill mspec-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mspec-design
Source: https://github.com/tubone24/mspec/tree/main/.claude/skills/mspec-design
Command: npx skills add https://github.com/tubone24/mspec --skill mspec-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the mspec design workflow, ensuring that developers can write comprehensive design.md, design-rationale.md, and architecture-overview.md artifacts with a full Constitution Check in place.

Core Features & Use Cases

  • Structured Artifacts: Automates the creation of structured design.md, design-rationale.md, and architecture-overview.md documents based on templates.
  • Full Constitution Check: Ensures compliance with all necessary specifications and best practices.
  • Use Case: When starting a new feature development, use this Skill to generate the necessary design documentation and rationale, facilitating a standardized development process.

Quick Start

Run /mspec:design to initiate the design workflow for your mspec project.

Frequently Asked Questions about mspec-design

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

FAQPage Schema
How do I generate structured mspec design documentation for a new feature?

To generate mspec design documentation, you can use this Skill to automate the creation of structured design.md, design-rationale.md, and architecture-overview.md artifacts based on templates.

What is a Constitution Check in mspec specification compliance?

A Constitution Check in mspec specification compliance ensures that your design documentation adheres to all necessary mspec specifications and best practices for code and spec consistency.

When do I need to write design rationale and architecture overview documents?

You need to write design rationale and architecture overview documents when starting a new feature development to facilitate a standardized development process and ensure specification compliance.

Does this mspec design workflow require any external dependencies?

No, this mspec design workflow does not require external dependencies, allowing you to directly generate and validate structured documentation artifacts without prerequisite tools.

What's the best way to ensure code and spec consistency in mspec projects?

The best way to ensure code and spec consistency in mspec projects is to automate the design workflow with a full Constitution Check that validates your structured documentation artifacts against best practices.

How do I start the mspec design workflow using scripts and references?

You can start the mspec design workflow by running the /mspec:design command, which initiates the automated generation and validation of your design documentation using the provided scripts and references.