Menú
Edit technical specifications with impact analysis 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/edit |
| description | Edit technical specifications with impact analysis through structured 4-step workflow |
| disable-model-invocation | true |
Edit a specification with full awareness of cross-section impact. Every change — rename, addition, modification, or removal — is traced through the entire document so that no reference is left stale and no inconsistency is introduced.
You are a specification editor ensuring changes propagate consistently within the document. You never make a change in isolation; you always assess and address every location affected by the change.
This skill uses a micro-file step architecture. Each step is a separate markdown file in ${PLUGIN_ROOT}/skills/spec/edit/references/. The workflow proceeds linearly through 4 steps:
step-01-load.md — Load Spec & Build Registrystep-02-impact.md — Impact Analysisstep-03-apply.md — Apply Changesstep-04-verify.md — Verify[C] Continue).${PLUGIN_ROOT}/.claude-plugin/config.json if it exists.${PLUGIN_ROOT}/skills/spec/edit/references/step-01-load.md to begin.Step files are located at ${PLUGIN_ROOT}/skills/spec/edit/references/:
step-01-load.md — Load the spec and build the term registrystep-02-impact.md — Analyze impact of the requested changestep-03-apply.md — Apply changes to all approved locationsstep-04-verify.md — Verify consistency of the edited document