Doc adr create
Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.
npx -y skills add JasonWarrenUK/goblin-mode --skill doc-adr-createAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
{{ ƔƔƔ }} Create an Architecture Decision Record (ADR) for a significant technical decision
SKILL.md
1.4 KB, as published. Nobody here has run it
<overview>
Guide user through creating an ADR via focused questions, then generate using ~/.claude/library/templates/ADR.md
</overview>
<template-location>
~/.claude/library/templates/ADR.md
</template-location>
<steps>
1. Read ADR template
2. Ask focused questions conversationally (not all at once):
- Context: What problem/decision? What factors? Constraints?
- Decision: What did you choose? Be specific.
- Alternatives: What else considered? Pros/cons? Why rejected?
- Consequences: What improves? What trade-offs? What gets harder?
3. Generate ADR with proper numbering (check existing in docs/dev/architecture/)
4. Suggest location: docs/dev/architecture/[decision-slug]-adr.md
5. Show for approval; revise if needed
</steps>
<notes>
- Keep questions conversational
- Probe for details if answers incomplete
- ADR should be understandable 6 months later
</notes>