From archcore
Creates ADR → (optional CPAT) → rule → guide cascade to codify team standards from decisions to enforceable practices and guides. For explicit standard cascade requests.
npx claudepluginhub archcore-ai/plugin --plugin archcoreThis skill uses the workspace's default tool permissions.
Establishes a team standard from decision to enforceable rule to practical how-to. Best for codifying technical decisions into mandatory practices. If the decision represents a code-pattern shift (before/after), a CPAT is offered between ADR and rule.
Creates ADR → rule → guide document chain to establish enforceable team standards for coding practices, conventions, error handling, API versioning, and migrations.
Guides authoring clear, enforceable Architectural Decision Records (ADRs) compatible with AI review systems and human teams. Useful for creating, improving, reviewing ADRs or PRs referencing them.
Generates Architectural Decision Records (ADRs) by detecting project template conventions, assigning sequential numbers, supporting MADR/Nygard/Alexandrian formats, and saving markdown files. Use for documenting technical decisions.
Share bugs, ideas, or general feedback.
Establishes a team standard from decision to enforceable rule to practical how-to. Best for codifying technical decisions into mandatory practices. If the decision represents a code-pattern shift (before/after), a CPAT is offered between ADR and rule.
mcp__archcore__list_documents(types=["adr", "cpat", "rule", "guide"]) — see what exists. If $ARGUMENTS provided, check for duplicates on this topic.
If related documents already exist (e.g., an ADR without a rule), pick up where the chain left off — don't recreate.
Use the AskUserQuestion tool to ask: "What decision was made? Why this approach over alternatives?"
Compose content covering Context, Decision, Alternatives Considered, Consequences. Create via mcp__archcore__create_document(type="adr").
Offer only if the decision clearly represents a code-pattern change (refactor, code-style shift, idiom migration). Otherwise skip to Step 4.
Ask: "Does this decision represent a code-pattern change (before/after code shift)? If yes, I can document the pattern as a CPAT."
If yes:
mcp__archcore__create_document(type="cpat").mcp__archcore__add_relation — cpat implements adr.Use the AskUserQuestion tool to ask: "What are the mandatory behaviors? How should this be enforced?"
Compose content covering Rule (imperative statements), Rationale, Examples (Good/Bad), Enforcement. Create via mcp__archcore__create_document(type="rule").
Add relation: mcp__archcore__add_relation — rule implements adr.
If a CPAT was created in Step 3b, also add: mcp__archcore__add_relation — rule related cpat.
Use the AskUserQuestion tool to ask: "What steps should developers follow? What are common pitfalls?"
Compose content covering Prerequisites, Steps (numbered), Verification, Common Issues. Create via mcp__archcore__create_document(type="guide").
Add relation: mcp__archcore__add_relation — guide related rule.
Check for specs, plans, or other documents that should be linked. Suggest additional add_relation calls.
Three or four linked documents: ADR → [optional CPAT] → rule → guide. Relations: rule implements adr, guide related rule, and if CPAT exists: cpat implements adr, rule related cpat.