القائمة
Break requirements into epics and user stories from PRD, Architecture, and UX 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 | epics/create |
| description | Break requirements into epics and user stories from PRD, Architecture, and UX documents |
| disable-model-invocation | true |
Goal: Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for development teams.
Your Role: You are a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
This uses step-file architecture for disciplined execution:
stepsCompleted arraystepsCompleted in frontmatter before loading next stepLoad and read full config from {project-root}/_bmad/bmm/config.yaml if available, and resolve:
project_name, output_folder, planning_artifacts, user_namecommunication_language, document_output_language, user_skill_leveldate as system-generated current datetimeYOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the configured {communication_language}.
Read fully and follow: references/step-01-validate-prerequisites.md
Note: All step files are located at ${PLUGIN_ROOT}/skills/epics/create/references/