mo-requirement-design

Generates requirements.md and design.md drafts for Monica module proposals.

13|6|Updated Feb 19, 2025
One-click install
npx skills add https://github.com/Tairitsua/Monica --skill mo-requirement-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mo-requirement-design
Source: https://github.com/Tairitsua/Monica/tree/main/.claude/skills/mo-requirement-design
Command: npx skills add https://github.com/Tairitsua/Monica --skill mo-requirement-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a structured, repeatable process to turn brief feature ideas into well-scoped requirements and concrete architectural designs for Monica modules, reducing ambiguity and speeding up implementation planning.

Core Features & Use Cases

  • Guided requirements gathering: Initializes a numbered .pending/{NNN}-{name} folder and generates a requirements.md from a template, then iteratively refines it through focused questions.
  • Architectural design generation: Analyzes existing Monica modules and produces a design.md with module placement, interface definitions, directory layout, and implementation steps using a standard template.
  • Workflow for teams: Useful for engineers and technical product managers who need consistent, traceable requirement artifacts and design plans for new Monica features or module extensions.

Quick Start

Initiate a new requirement by providing a short idea and asking the assistant to create a numbered .pending/NNN-brief-name/requirements.md and populate the overview using the requirements template.

Frequently Asked Questions about mo-requirement-design

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

FAQPage Schema
How do I turn feature ideas into Monica module requirements and designs?

To turn feature ideas into Monica module requirements, you provide a brief concept to initialize a numbered .pending folder, generate a requirements.md from a template, and iteratively refine the details through focused clarifying questions.

What is the workflow for structured requirement gathering in Monica?

Structured requirement gathering in Monica involves creating a .pending/{NNN}-{name} directory, populating a requirements.md template with an overview, and iteratively refining the scope through eliciting clarifying questions.

How do I generate an architectural design for a new Monica module?

You generate an architectural design for a Monica module by analyzing existing modules and producing a design.md artifact that defines module placement, interfaces, directory layout, and a stepwise implementation plan.

Can I use this process to plan directory layouts and interface definitions for feature proposals?

Yes, the process applies to creating and refining feature proposals by satisfying conventions for module placement decisions, interface definitions, directory layout planning, and stepwise implementation plans.

What is the best way to reduce ambiguity when planning Monica feature extensions?

The best way to reduce ambiguity is using a structured, repeatable process that iteratively elicits clarifying questions and generates concrete requirements.md and design.md artifacts for well-scoped Monica features.