Menú
Propagate specification changes across related documents through structured 4-step workflow
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 | spec/propagate |
| description | Propagate specification changes across related documents through structured 4-step workflow |
| disable-model-invocation | true |
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.
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.
This workflow uses a micro-file architecture with the following design principles:
Each step is a self-contained markdown file in ${PLUGIN_ROOT}/skills/spec/propagate/references/. Files are small, focused, and independently loadable. This keeps context windows lean and instructions precise.
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.
Steps must be completed in order: diff → scan → review → apply. Never skip steps. Never go backwards unless explicitly restarting.
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.
When processing any step file:
${PLUGIN_ROOT}/.claude-plugin/config.json.${PLUGIN_ROOT}/skills/spec/propagate/references/step-01-diff.md to begin.