bs-methodology

Generate MVP-ready artifacts from initial ideas into a standardized brainstorm directory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-methodology
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/brainstorming/skills/bs-methodology
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, repeatable process to turn loose ideas, inherited repositories, or production issues into organized MVP-ready artifacts and actionable handoffs, reducing scattered notes and inconsistent spec formats.

Core Features & Use Cases

  • Agent orchestration & assessment: runs an operational scorecard, activates the right specialist agents, and creates a tracked brainstorm/ workspace.
  • Templates & artifact mapping: generates JTBD, hypothesis templates, MoSCoW prioritization, UX flows, architecture records, and maps outputs to dev-methodology specs for smooth handoff.
  • Onboarding & specialist analysis: supports repo cartography, security/performance/accessibility checks, and produces changelog and status tracking for downstream implementation.

Quick Start

Start a structured brainstorm for a new project by asking the assistant to initialize the brainstorm, run the assessment, produce three concepts, a JTBD, MoSCoW scope, UX flows, and an architecture draft mapped to dev-methodology specs.

Frequently Asked Questions about bs-methodology

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

FAQPage Schema
How do I structure brainstorming to produce MVP-ready specs from a rough idea?

Structured brainstorming for MVP specs turns loose ideas into organized artifacts by running an operational scorecard, activating specialist agents, and generating prioritized scope, UX flows, and architecture drafts in a tracked workspace.

What is the best way to onboard and triage an inherited repository for product discovery?

Repository onboarding for product discovery uses agent orchestration to perform repo cartography, run security and performance checks, and produce assessment scorecards with mapped changelog tracking for downstream implementation.

Can I automate MVP scope prioritization and artifact generation?

Automated MVP scope prioritization supports --auto runs and agent orchestration to generate JTBD templates, MoSCoW prioritization, and architecture records mapped directly to dev-methodology specs.

How does agent orchestration work for early-stage product ideation?

Agent orchestration for product ideation activates specialized agents that assess the initial idea, generate problem framing and market research, and output standardized brainstorm directories with templates and status tracking.

Does this methodology require existing dev-methodology specs to map outputs?

Mapping outputs to dev-methodology specs creates standardized handoffs by generating architecture records and MoSCoW scope documents that align directly with downstream implementation workflows.

What templates are generated for MVP-ready product discovery workflows?

Templates for MVP-ready product discovery include JTBD, hypothesis templates, MoSCoW prioritization, UX flows, and architecture records, all stored in a standardized brainstorm directory with changelog and assessment rules.