bmad-skills

Plugin bmad-skills from marketplace bmad-skills in bmad-labs/skills. Commands read from the repo's manifest — 4 days ago.

Skills (23)

• architecture-design

  Use when the user asks for a design package, designs folder, detailed design, solution design, or contracts of a system or service before it is built — C4, project structure, module design, ERD or data model, domain events, ingress or egress API (REST, gRPC, Kafka, Pub/Sub, SQL), sequence, class, st

• architecture-viz-studio

  Use when the user wants to visualize, present, "show", animate, or build an interactive web page for a software architecture, system design, technical concept, data model, pipeline, or product story — phrases like "intro page", "architecture visualization", "interactive diagram", "scrollytelling", "

• bmad-leader

  Use when a BMAD project has intent, PRD, architecture and optionally technical design, and the user wants one long-running session to drive implementation of stories or epics through bmad-build subagents ("lead the build", "run epic N", "drive the stories"); also when resuming a build ("resume the l

• book-converter

  Convert EPUB books (.epub) to high-quality formatted Markdown using pandoc and AI-assisted formatting. Use when the user provides an EPUB file path and wants it converted to professionally formatted Markdown (ebook to markdown, epub to md). This skill handles the complete workflow from EPUB extracti

• close-loop-dev-setup

  Use when an agent cannot validate the product the way a human would — no browser or desktop harness, no screenshots, no vision check, or bmad-leader reports a UAT level as NOT RUN; also when the user says "set up screenshot testing", "let the agent see the UI", "drive the app with Playwright" or ask

• create-intent

  Use when turning Jira stories, tickets, or raw requirement notes into business intent documents (intent, functional and non-functional requirements, open questions) before a PRD or design, when requirements are unclear, conflicting, or incomplete and need questions for a PO, or when the user says "c

• github-sync

  Bidirectional sync between BMAD planning artifacts and GitHub Projects v2. Use this skill whenever the user says "sync to github", "push stories", "pull status from github", "set up github project", "github sync", "onboard github project", "create github issues from stories", "update stories from gi

• jira-to-local

  Use when the user wants Jira issues pulled onto disk as local files — "pull PROJ-123", "fetch this story", "get that ticket locally", "download the bug", "save this issue and its comments", "grab the NFR", "read this ticket offline", or a pasted Jira browse URL with nothing else asked of it. Also fo

• load-docs

  Loads documents fully into the main agent's context so the agent can answer questions, summarize, or work with that content in subsequent turns. Use whenever the user wants to ingest, read, absorb, or pull in documents — especially when they say things like "load these docs", "read all of these", "i

• manual-testing

  Use when writing, reviewing, executing, or updating manual test cases or a test plan; when asked 'how should I test this?' or 'what test cases do I need?'; when reviewing test coverage or test quality; when restructuring an existing test suite or its layout; or after implementing a behaviour change

• mcp-builder

  Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

• multi-repo-git-ops

  Manages git operations (branching, committing, pushing, syncing) in multi-repo systems — a parent repo with git submodules or multiple service repos. Use this skill when, in such a project, the user wants to create a feature branch, commit or push changes, sync submodules, update submodule pointers,

• rca-report

  Use when documenting a resolved or contained production incident, outage, near-miss, silent pipeline/service failure, data corruption event, or post-mortem — guides evidence collection while the post-fix state is still observable AND produces a rich, reproducible Root Cause Analysis report. Trigger

• release-please

  Use when the user wants to automate releases, versioning or changelogs with GitHub Actions; set up or configure release-please (pipelines, pre-releases, monorepos); write release-please-compatible Conventional Commits; tag versions or publish to npm, PyPI, crates.io, Maven or Docker automatically; o

• skill-from-book

  Create Claude skills from book content (markdown files). Transforms long-form book knowledge into structured, context-efficient skill packages with granular reference files, workflows, and use-case guidelines. Use this skill when: - Converting a book (markdown) into a reusable Claude skill - Creatin

• slide-maker

  Use when the user wants to brainstorm, build, design, generate, review, or export a slide, deck, presentation, pitch, or company, product or sales deck — including export to editable PPTX, image PPTX, standalone HTML or PDF, applying their own design system or brand tokens to slides, or supplying a

• to-markdown

  Use when converting a PDF, scanned document, slide deck, or DOCX into Markdown that must stay faithful to the source — a paper, thesis, standard, datasheet, SDK guide, or manual that will be read, grepped, cited, or diffed later. Use when the source carries equations, tables, figures with captions,

• to-wiki

  Use when turning a transcribed source — a thesis, paper, standard, manual, or a folder of Markdown chapters under docs/references — into a Karpathy-style LLM wiki knowledge base: interlinked concept, entity, source, and synthesis pages with an index.md, an append-only log.md, and a schema file, wher

• trade-off-analysis

  Create structured technology trade-off analysis documents with scored comparison matrices. Use this skill whenever the user wants to compare technologies, evaluate architectural options, analyze build-vs-buy decisions, assess migration strategies, or produce any decision document that compares multi

• typescript-clean-code

  Use when the user writes, reviews, or refactors TypeScript/JavaScript code, or asks whether code is clean, maintainable, or well-designed; names a smell (Shotgun Surgery, Feature Envy, Data Clumps, Long Method, Divergent Change, Duplicated Code, Large Class, Long Parameter List, Primitive Obsession,

• typescript-e2e-testing

  E2E and integration testing for TypeScript/NestJS projects using Jest, supertest, and real infrastructure via Docker (Kafka, PostgreSQL, MongoDB, Redis) with the Given-When-Then pattern. Use whenever the user is working on `.e2e-spec.ts` files or anything under `test/e2e/`, or asks to set up, write,

• typescript-unit-testing

  Unit testing for TypeScript/NestJS projects using Jest, @golevelup/ts-jest (DeepMocked/createMock), and in-memory databases, with AAA structure. Use whenever the user is working on `.spec.ts` files or asks to set up Jest, write/add tests for a service/usecase/controller/guard/interceptor/pipe/filter

• ultrathink-protocol

  Root-cause investigation protocol for live, complex or multi-layer technical problems. Use when a problem has resisted two or more fix attempts, the root cause is unknown or assumed, you are about to retry a variation of a failed fix, or the user says "ultrathink protocol", "think deeper", "figure o