create-adr
Create a new Architecture Decision Record. Use when documenting significant technical decisions with context, options, and rationale.
What this skill does
# Create Architecture Decision Record
Create a new ADR documenting a significant technical decision.
## Process
### 1. Parse Arguments
Extract from user input:
- **Title**: Decision topic (required) - e.g., "Use PostgreSQL for primary database"
- **Status**: `proposed`, `accepted`, `deprecated`, `superseded` (default: `proposed`)
- **Template**: `basic` (Nygard), `madr`, or `extended` (default: `madr`)
### 2. Determine ADR Number
1. Find existing ADRs in the project:
```text
Look in: docs/decisions/, docs/adr/
Pattern: ADR-*.md, [0-9][0-9][0-9][0-9]-*.md
```
2. Calculate next number:
- If no ADRs exist, start at 001
- Otherwise, increment highest existing number
### 3. Gather Context
If context is not provided, prompt for or infer:
1. **Problem Statement**: What issue motivated this decision?
2. **Constraints**: What limitations affect the decision?
3. **Options Considered**: What alternatives exist?
4. **Decision Drivers**: What factors are most important?
### 4. Load Skill and Generate
1. Load the `enterprise-architecture:adr-management` skill for templates and guidance
2. Select template based on `template` argument
3. Generate ADR content with:
- Proper frontmatter/header
- All required sections
- Placeholder guidance for sections needing human input
### 5. Create File
Determine file location based on project conventions:
```text
Priority order:
1. docs/decisions/ADR-{number}-{slug}.md (if docs/decisions/ exists)
2. docs/adr/ADR-{number}-{slug}.md (if docs/adr/ exists)
4. docs/decisions/ADR-{number}-{slug}.md (create directory)
```
Slug format: lowercase, hyphens, from title
Example: "Use PostgreSQL" → `ADR-001-use-postgresql.md`
### 6. Update Index
If an ADR index/registry exists, add entry:
- Add to ADR-INDEX.md or README.md in decisions folder
- Include: number, title, status, date
## Output Content
### Basic Template (Nygard)
```markdown
# ADR-{NUMBER}: {TITLE}
## Status
{STATUS}
## Context
[What is the issue that we're seeing that is motivating this decision?]
## Decision
[What is the change that we're proposing and/or doing?]
## Consequences
[What becomes easier or more difficult to do because of this change?]
```
### MADR Template
```markdown
# ADR-{NUMBER}: {TITLE}
## Status
{STATUS}
Date: {YYYY-MM-DD}
## Context and Problem Statement
[Describe the context and problem statement]
## Decision Drivers
* [Driver 1]
* [Driver 2]
## Considered Options
1. [Option 1]
2. [Option 2]
3. [Option 3]
## Decision Outcome
**Chosen option:** "[Option X]", because [justification].
### Consequences
**Good:**
* [Positive consequence]
**Bad:**
* [Negative consequence]
## Pros and Cons of Options
### [Option 1]
* Good, because [argument]
* Bad, because [argument]
### [Option 2]
* Good, because [argument]
* Bad, because [argument]
```
### Extended Template
Include additional sections:
- Executive Summary
- Constraints and Assumptions
- Trade-offs table
- Implementation action items
- Validation criteria
- Related decisions
- References
## Example Invocations
```text
/create-adr "Use PostgreSQL for primary database"
→ Creates ADR-XXX-use-postgresql.md with MADR template, status=proposed
/create-adr "Switch to event sourcing" status=accepted template=extended
→ Creates ADR-XXX-switch-to-event-sourcing.md with extended template
/create-adr "Deprecate REST API v1" status=deprecated
→ Creates ADR-XXX-deprecate-rest-api-v1.md marking v1 as deprecated
```
## Post-Creation Guidance
After creating the ADR, remind user to:
1. **Fill in placeholders** marked with `[brackets]`
2. **Add specific options** with pros/cons
3. **Document the actual decision** once made
4. **Link related ADRs** if applicable
5. **Update status** when decision is finalized
6. **Get review** from stakeholders
## Quality Criteria
Generated ADR must:
- [ ] Have unique, sequential number
- [ ] Follow project's ADR location conventions
- [ ] Include all required sections for template type
- [ ] Have clear placeholder guidance
- [ ] Be linked from ADR index (if exists)
- [ ] Use consistent date format (ISO 8601)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.