giuseppe-trisciuoglio/developer-kit / plugins/developer-kit-core/skills/adr-drafting
adr-drafting
VerifiedCreates new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.3 KB |
| references/examples.md | markdown | 1.6 KB |
| references/template.md | markdown | 931 B |
references/examples.md
View on GitHub# ADR Examples
## Example 1
**Path:** `docs/architecture/adr/0003-adopt-postgresql-for-primary-database.md`
```markdown
# ADR-0003: Adopt PostgreSQL for the Primary Database
## Status
Accepted
## Context
The application has outgrown SQLite for concurrent writes and operational visibility. We need stronger transactional guarantees, better backup tooling, and a database that can support production traffic growth.
## Decision
Adopt PostgreSQL as the primary relational database for all new production deployments.
## Consequences
PostgreSQL improves concurrency, operational tooling, and long-term scalability. It also introduces additional infrastructure and migration complexity compared with SQLite.
```
## Example 2
**Path:** `docs/architecture/adr/0004-introduce-event-driven-order-processing.md`
```markdown
# ADR-0004: Introduce Event-Driven Order Processing
## Status
Proposed
## Context
Synchronous order processing is increasing latency in the checkout flow and makes retries difficult when downstream services are degraded.
## Decision
Introduce an event-driven workflow for order fulfillment so checkout can publish an order event and downstream processors can handle fulfillment asynchronously.
## Consequences
This change should reduce user-facing latency and improve resilience. It also adds messaging infrastructure, operational monitoring needs, and eventual-consistency trade-offs.
```
## Naming Tips
- Prefer action-oriented titles such as "Adopt", "Introduce", "Standardize", or "Migrate"
- Keep filenames short but descriptive
- Reuse the repository's numbering pattern if ADRs already exist
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |