SkillsAdd

modelscope.cn

bmad

BMad Method v6: workflow-driven agile delivery (track selection, PRD/spec, UX, architecture, epics/stories).

Installation

$ npx skills add https://modelscope.cn
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from modelscope.cn · top by installs.

npx skills add https://modelscope.cn
skill-creator 2K frontend-design 1.9K pptx-generator 1.3K minimax-docx 1.2K find-skills 1.1K minimax-xlsx 1.2K minimax-pdf 1.2K docx 942 self-improvement 932 pdf 914

Browse all from modelscope.cn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,146 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

BMad Method (BMAD) v6

Source: https://github.com/bmad-code-org/BMAD-METHOD

When to use

Use BMAD for structured, end-to-end delivery when the request is broad enough to need planning artifacts and a workflow.

Typical triggers:

  • Track selection (Quick vs Method vs Enterprise).
  • Planning artifacts (tech spec, PRD, UX, architecture).
  • Turning requirements into epics/stories and sprint execution.
  • “What should we do next?” workflow guidance.

Core concepts

Workflows, not ad-hoc prompts

BMAD v6 is organized around workflows run by specialized agents. Common entry points:

  • workflow-init to analyze the project and choose a track.
  • workflow-status when unsure what’s next.

Tracks (planning depth)

  • Quick Flow: fast path; typically a tech spec; small changes/features.
  • BMad Method: fuller planning; PRD + optional UX + architecture.
  • Enterprise Method: extended planning; higher governance/compliance/testing needs.

Lifecycle

  • Analysis (optional): brainstorm/research/brief.
  • Planning (required): PRD (Method/Enterprise) or tech spec (Quick).
  • Solutioning (track-dependent): architecture, then epics/stories.
  • Implementation (required): sprint plan → story → implement → review → repeat.

Context rule

Prefer fresh chats per workflow to reduce context bleed.

Lightweight playbook (in chat)

  1. Establish context (greenfield/brownfield, outcomes/users, constraints).
  2. Recommend a track and why.
  3. Outline the minimum artifacts for that track.
  4. Drive the next workflow step explicitly (workflow-init or workflow-status).

Activation cues

  • "BMAD" / "BMad Method" / "BMAD v6"
  • "workflow-init" / "workflow-status" / "track selection"
  • "PRD" / "tech spec" / "UX" / "architecture"
  • "epics and stories" / "sprint planning" / "dev-story"
  • "greenfield" / "brownfield"

Non-goal

If the user only wants a narrow A-vs-B technology comparison (TCO/lock-in/etc.) without delivery workflow, use a dedicated decision framework instead.