メニュー
BMAD PRD methodology, quality standards, and reference data for creating, validating, and editing Product Requirements Documents
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create comprehensive architecture decision documents through collaborative 8-step workflow. Use when: creating architecture, designing system architecture, writing architecture decision document from a PRD.
Generate styled draw.io (.drawio) files from architecture shard document content with C4-appropriate shapes, colors, and layout. Use when: generating architecture diagrams, converting architecture to drawio, creating C4 diagrams, generating draw.io files from shard documents.
Shard a monolithic architecture document into 7 focused sub-documents with Mermaid diagrams, gap analysis, and cross-references. Use when: sharding architecture document, decomposing architecture, splitting architecture into sub-documents.
BMAD Architecture methodology, quality standards, and reference data for creating architecture decision documents. Use when: working with architecture documents, checking architecture quality standards, understanding architecture methodology.
Manage Confluence pages at onemount.atlassian.net via the REST API v2. Use this skill whenever the user wants to fetch, view, search, create, edit, or update a Confluence page — including pasting a Confluence URL and asking to edit it, asking about page content, listing pages in a space, or pushing local changes back. Trigger on any mention of Confluence pages, Confluence URLs (onemount.atlassian.net/wiki), page IDs, Confluence spaces, or requests like "update the confluence page", "fetch the PRD from confluence", "push my changes to confluence". Also trigger when the user asks to create a new Confluence page or search for existing pages.
Bidirectional sync between local Markdown files and Confluence pages. Use this skill when the user wants to push a .md file to Confluence, pull a Confluence page as .md, batch-push a directory of markdown files, or check sync status. Trigger on requests like "push this doc to Confluence", "pull the PRD from Confluence as markdown", "sync docs to Confluence", "convert this markdown to a Confluence page", or "batch push all docs".
| name | prd/standards |
| description | BMAD PRD methodology, quality standards, and reference data for creating, validating, and editing Product Requirements Documents |
A BMAD PRD serves two audiences simultaneously:
The PRD is the top of the funnel feeding all subsequent product development work. Quality here ripples through every phase.
Every sentence must carry information weight. Eliminate filler, padding, and verbose patterns.
All functional and non-functional requirements must be:
The PRD establishes the chain that all downstream artifacts depend on:
Vision -> Success Criteria -> User Journeys -> Functional Requirements -> (future: User Stories)
Every requirement must trace back to documented user needs and business objectives.
For detailed methodology and rationale, see:
references/prd-purpose.md - Full BMAD PRD methodology, anti-pattern examples, and downstream impact analysisFor project classification and domain-specific requirements, see:
references/project-types.csv - Project type detection signals, key questions, required/skip sections, and innovation signalsreferences/domain-complexity.csv - Domain complexity levels, compliance concerns, required knowledge, and special sections