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/template.md
View on GitHub# Default ADR Template
Use this template when the repository does not already provide an ADR structure.
```markdown
# ADR-NNNN: Decision Title
## Status
Proposed
## Context
Describe the problem, constraints, trade-offs, and any alternatives that influenced this decision.
## Decision
Describe the architectural choice that was made.
## Consequences
Describe what becomes easier, harder, riskier, or more expensive because of this decision.
```
## Default Conventions
- Directory: `docs/architecture/adr`
- Filename: `NNNN-short-kebab-title.md`
- Title format: `ADR-NNNN: Decision Title`
- Starting number: `0001` if no prior ADR exists
## Status Guidance
- `Proposed` — The change is being considered or prepared
- `Accepted` — The team has agreed to the decision
- `Rejected` — The proposed decision was considered and declined
Keep status values simple unless the repository already uses a richer ADR lifecycle.
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: 471k | 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 |