
Adr Drafting
This does one thing well: it creates new Architecture Decision Records with the standard Status, Context, Decision, and Consequences sections. Before writing anything, it checks your repo for existing ADR conventions (numbering, location, filename patterns) and matches them, or defaults to docs/architecture/adr with zero-padded filenames like 0001-use-postgresql.md. It asks you to confirm the decision details up front, shows you a preview, and only writes the file after you approve. The focus is narrow by design. It won't update existing ADRs or manage supersession links, just draft new records so you actually document architectural choices instead of letting them live in Slack threads.
- skills.sh installs
- 3.6K
- GitHub stars
- 369
- last updated
- Aug 21, 2026
Install
$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill adr-drafting --agent claude-codeInstalls into .claude/skills of the current project.
Files
ADR Drafting
Creates new Architecture Decision Record (ADR) documents for major architectural choices so teams can keep a clear history of why important technical decisions were made.
Overview
This skill helps create a new ADR from discovery to final markdown file. It confirms the decision details, inspects the repository for any existing ADR conventions, and drafts a new ADR with the standard sections Title, Status, Context, Decision, and Consequences.
When the repository does not already have an ADR convention, default to storing ADRs in docs/architecture/adr and use a zero-padded filename such as 0001-use-postgresql-for-primary-database.md.
See references/template.md for the default ADR template and references/examples.md for example ADRs and naming patterns.
When to Use
Use this skill when a user or agent has decided on a meaningful architectural change and needs to document the rationale, chosen direction, and trade-offs in a new Architecture Decision Record. It fits requests such as creating an ADR, documenting an architecture decision, writing a decision record, or preserving the project history behind an important technical choice.
Sponsors
Details
- Repository
- github.com/giuseppe-trisciuoglio/developer-kit
- Categories
- Code Review & Quality, AI & Agent Building, Productivity & Planning
- First seen
- May 16, 2026
More from giuseppe-trisciuoglio/developer-kit
All 102- Gemini3.6K
- Copilot Cli3.6K
- Codex3.5K
- Wiremock Standalone Docker3.5K
- Aws Cdk3.5K
- Learn3.5K
- Qwen Coder3.4K
- Bug Fix Brief3.1K
- Knowledge Graph1.9K
- Specs Code Cleanup1.8K
- Ralph Loop1.7K
- Create Pr From Spec1.5K
- Constitution1.4K
- Task Quality Kpi532
- Claude Md Management320
- Shadcn Ui22.7K
- Tailwind Css Patterns18K
- Drizzle Orm Patterns5.7K
- Nextjs Performance5K
- Unit Test Bean Validation5K
- React Patterns4.9K
- Tailwind Design System4.7K
- React Code Review4.5K
- Spring Boot Test Patterns4.4K