mm-brief

Create structured Markdown briefs for ideas and feature requests.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mm-brief
Source: https://github.com/mikkeymoo/claude-solo/tree/main/mm-skills/mm-brief
Command: npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Facilitates the clear and concise documentation of ideas or feature requests into a structured format.

Core Features & Use Cases

  • Structured Briefing: Guides users in structuring their thoughts on a new idea or feature request.
  • Problem-Solution Mapping: Assists in defining the problem and the intended solution in a succinct manner.
  • Use Case: Ideal for product managers or developers when defining the scope of a new project.

Quick Start

Use the /mm-brief [idea or feature description] command to create a structured brief.

Frequently Asked Questions about mm-brief

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

FAQPage Schema
What is a structured product brief for feature requests?

A structured product brief is a formatted document that organizes feature requests into defined sections like problem, goal, scope, and constraints to ensure clear communication in collaborative environments.

How do I write a structured document for a new idea or feature request?

You can write a structured feature request by using Markdown formatting to map the problem-solution scope, define target users, and list open questions for collaborative review.

Can I use Markdown formatting to organize my product management documentation?

Yes, this approach uses Markdown formatting to structure your product management documentation, allowing you to clearly organize constraints, goals, and open questions for feature requests.

Does this structured briefing method work for defining project scope?

Yes, structured briefing is ideal for product managers or developers defining new project scope, guiding users to succinctly document the problem, intended solution, and relevant user constraints.

What is the best way to capture open questions and constraints for a feature request?

The best way to capture open questions is to map them within a structured Markdown document, ensuring that problem-solution mapping, scope, and constraints are clearly recorded for team collaboration.