Help us improve
Share bugs, ideas, or general feedback.
From contributor-writing
Creates and validates Shopware Architecture Decision Records (ADRs) interactively with YAML frontmatter, structure selection, guided content, and checks for coverage, style, and conventions.
npx claudepluginhub shopwarelabs/ai-coding-tools --plugin contributor-writingHow this skill is triggered — by the user, by Claude, or both
Slash command
/contributor-writing:adr-writingopusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Creation**: "create", "write", "new", "draft"
Generates Architectural Decision Records (ADRs) in MADR, Nygard, Alexandrian, or project formats. Researches directory for conventions, gathers context, numbers sequentially, validates, and saves. Use for documenting technical decisions.
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.
Writes Architectural Decision Records (ADRs) using the MADR template and verifies completeness with Definition of Done (E.C.A.D.R.) criteria. Use when documenting architectural decisions from meetings or PR discussions.
Share bugs, ideas, or general feedback.
---
title: Short descriptive title
date: YYYY-MM-DD
area: core
tags: [relevant, tags]
---
title (required): Short, descriptive. Do NOT repeat as a Markdown # headingdate (required): YYYY-MM-DDarea (required): One of: core, checkout, admin, storefront, inventory, framework, discovery, infrastructure, processtags (required): Lowercase technical terms, YAML arrayauthors, status (optional)Every ADR must address all 8 items:
Load references/writing-style.md for voice examples, table/diagram guidance
AskUserQuestion to collect: topic/title, area (present enum), tags, scope (single vs multi-domain).
If topic already provided, infer what you can before asking.
Load references/structure-patterns.md for templates and examples
Single domain → Context / Decision / Consequences:
## Context
[Problem, background, constraints — problem before solution]
## Decision
[What was decided, pseudocode, public API definitions]
## Consequences
[Developer impact, backward compatibility, migration path]
Multi-domain → Domain-by-domain:
## heading per domainAdditional sections when appropriate: Extendability, Considered Alternatives, Backward Compatibility, Security Considerations.
date +%Y-%m-%d via Bash)references/code-in-adrs.md when writing code sectionsreferences/shopware-patterns.md for feature flags, cross-references, audience-specific consequencesreferences/writing-rules-anti-ai-slop.md to internalize style constraints and anti-slop rulesVerify all 8 required coverage items are addressed. If gaps exist, ask user for missing information.
Also ask about optional concerns: feature flag gating, backward compatibility implications, alternative approaches considered, related ADRs to cross-reference.
references/writing-rules-anti-ai-slop.md, then check the draft literally (not from memory):
YYYY-MM-DD-kebab-case-title.mdadr/ directory if it exists, otherwise ask user for target directoryRead file, parse YAML front matter, identify ## section headings.
Verify: title present, date valid YYYY-MM-DD, area from allowed enum, tags lowercase array, no # heading duplicating title.
Load references/validation-checklist.md for detailed criteria
Load references/writing-rules-anti-ai-slop.md for anti-slop checks
Check all 8 required coverage items, structure compliance, writing style, anti-slop rules, code quality, Shopware-specific patterns.
ADR Validation Report
=====================
File: [filename]
Title: [title]
Front Matter: [✓/✗]
[issues if any]
Required Coverage: [✓/⚠/✗]
[per-item breakdown]
Structure: [✓/⚠]
[type detected, issues]
Style: [✓/⚠]
[issues if any]
Anti-Slop: [✓/⚠]
[issues if any]
Shopware Patterns: [✓/⚠]
[issues if any]
Recommendations:
1. [actionable items]