From sdlc
Shard a monolithic architecture document into 7 focused sub-documents with Mermaid diagrams, gap analysis, and cross-references
npx claudepluginhub nexussema/omg-marketplace --plugin sdlcThis skill uses the workspace's default tool permissions.
**Goal:** Read a monolithic architecture document and produce 7 focused, detailed sub-documents that decompose it by architectural concern. Each output document expands significantly beyond the source with Mermaid diagrams, tables, gap analysis, and cross-references — giving teams independently ownable, implementation-ready architecture artifacts.
references/gap-report-template.mdreferences/mermaid-diagram-standards.mdreferences/output-doc-checklist.mdreferences/output-doc-template.mdreferences/source-mapping-rules.mdreferences/step-01-parse-source.mdreferences/step-02-high-level-design.mdreferences/step-03-tech-stack.mdreferences/step-04-detailed-design.mdreferences/step-05-sequence-diagrams.mdreferences/step-06-deployment.mdreferences/step-07-network.mdreferences/step-08-database-design.mdGuides TDD-style skill creation: pressure scenarios as tests, baseline agent failures, write docs to enforce compliance, verify with RED-GREEN-REFACTOR.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Goal: Read a monolithic architecture document and produce 7 focused, detailed sub-documents that decompose it by architectural concern. Each output document expands significantly beyond the source with Mermaid diagrams, tables, gap analysis, and cross-references — giving teams independently ownable, implementation-ready architecture artifacts.
Your Role: You are an Architecture Document Specialist collaborating with the architect/developer. You bring expertise in C4 modeling, technology assessment, deployment patterns, network topology, database design, and sequence diagram authoring. The user brings context about their system's purpose, constraints, and priorities. Work together to produce sub-documents that directly guide implementation.
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:
Load 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}.
"Shard Mode: Decomposing a monolithic architecture document into 7 focused sub-documents."
Read fully and follow: references/step-01-parse-source.md
Note: All step files are located at ${PLUGIN_ROOT}/skills/architecture/shard/references/