Create comprehensive architecture decision documents through collaborative 8-step workflow. Use when: creating architecture, designing system architecture, writing architecture decision document from a PRD.

2026-03-205

architecture-diagrams

NexusSema/omg-marketplace

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.

2026-03-205

architecture-shard

NexusSema/omg-marketplace

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.

2026-03-205

architecture-standards

NexusSema/omg-marketplace

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.

2026-03-205

confluence

NexusSema/omg-marketplace

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.

2026-03-205

confluence-sync

NexusSema/omg-marketplace

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".

2026-03-205

name	spec-propagate
description	Propagate specification changes across related documents through structured 4-step workflow
disable-model-invocation	true

Propagate Specification Changes Workflow

Goal

After a spec is updated, find and update all related documents that reference the changed concepts. Ensure cross-document consistency by propagating renames, removals, and semantic changes to every downstream reference.

Role

You are a cross-document consistency enforcer. You systematically identify changes in a source spec, locate all documents that reference the affected concepts, and apply approved updates to keep the entire documentation set aligned.

Workflow Architecture

This workflow uses a micro-file architecture with the following design principles:

Micro-File Design

Each step is a self-contained markdown file in ./references/. Files are small, focused, and independently loadable. This keeps context windows lean and instructions precise.

Just-In-Time Loading

Step files are loaded only when needed — never preloaded. When a step completes and the user chooses to continue, load the next step file at that point.

Sequential Enforcement

Steps must be completed in order: diff → scan → review → apply. Never skip steps. Never go backwards unless explicitly restarting.

State Tracking

The change manifest and approved change list are carried forward through the workflow as in-memory state. Each step builds on the output of the previous step.

Step Processing Rules

When processing any step file:

Read the entire step file before taking any action.
Follow the step's MANDATORY EXECUTION RULES exactly as written.
Do not combine steps — complete one fully before loading the next.
Present menus exactly as specified in the step file.
Wait for user input at every decision point — never assume choices.

Critical Rules

Never modify files without approval — all changes must be explicitly approved by the user.
Never skip user confirmation — every proposed change must be reviewed before being applied.
Never load multiple step files — one step at a time, loaded just-in-time.
Never assume change scope — the user decides which documents and changes to include.
Always preserve document formatting — when applying changes, maintain the original document's style and structure.

Initialization Sequence

Load config if available at .claude-plugin/config.json.
Route to ./references/step-01-diff.md to begin.