Agent skill
adr
Architecture Decision Records management. Actions: create (new ADR), list (show all), search (find by keyword). Use when: (1) making architecture decisions, (2) choosing between technologies, (3) documenting trade-offs. Triggers: /adr, 'architecture decision', 'decision record', 'document decision'.
Install this agent skill to your Project
npx add-skill https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/adr
SKILL.md
ADR — Architecture Decision Records v3.0
Document architecture decisions with context, options, and rationale.
Actions
/adr create <title>
- Create numbered ADR file:
docs/decisions/NNNN-<slug>.md - Fill template with: Status, Context, Decision, Consequences
- Link to related ADRs if they exist
/adr list
List all ADRs with status (proposed, accepted, deprecated, superseded).
/adr search <query>
Search ADR titles and content for relevant decisions.
Template
# ADR-NNNN: <Title>
**Status**: Proposed | Accepted | Deprecated | Superseded by ADR-XXXX
**Date**: YYYY-MM-DD
**Deciders**: <who was involved>
## 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
### Positive
- ...
### Negative
- ...
### Neutral
- ...
## Alternatives Considered
| Option | Pros | Cons | Why Not |
|---|---|---|---|
Integration
- Orchestrator Step 3 (PLAN): for complexity >= 7, suggest creating an ADR
- Vault (Item 8): ADRs feed into vault/projects/{project}/decisions/
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
browser-test
Browser testing using Chrome DevTools MCP and Playwright for visual verification. Start dev server, navigate, screenshot, Lighthouse audit, console errors, network check. Use when: (1) verifying frontend changes, (2) accessibility auditing, (3) performance testing, (4) visual regression. Triggers: /browser-test, 'test in browser', 'visual test', 'lighthouse audit'.
crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
stop-slop
A skill for removing AI-generated writing patterns ('slop') from prose. Eliminates telltale signs of AI writing like filler phrases, excessive hedging, overly formal language, and mechanical sentence structures. Use when: writing content that should sound human and natural, editing AI-generated drafts, cleaning up prose for publication, or any content that needs to sound authentic rather than AI-generated. Triggers: 'stop-slop', 'remove AI tells', 'clean up prose', 'make it sound human', 'edit AI writing'.
bugs
Bug hunting with Codex CLI Use when: (1) /bugs is invoked, (2) task relates to bugs functionality.
adversarial
Multi-Agent Adversarial Analysis System for code security
senior-software-engineer
Global skill enforcing senior software engineering best practices
Didn't find tool you were looking for?