adr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
Profile →npx skills add ruvnet/ruflo --skill adr-create --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Create ADR Create a new Architecture Decision Record with the next sequential number, register it in the AgentDB graph, and link it to related ADRs. ## When to use When a significant architectural decision needs to be recorded -- new technology adoption, API design choices, data model changes, infrastructure decisions, or any cross-cutting concern that affects multiple components. ## Steps 1. **Find next number** -- `Glob` for `docs/adr/ADR-*.md` and parse existing numbers to determine the next sequential ID (ADR-001, ADR-002, etc.). Create `docs/adr/` if it does not exist. 2. **Slugify title** -- Convert the title argument to a lowercase, hyphen-separated slug (e.g., "Use PostgreSQL for persistence" becomes `use-postgresql-for-persistence`). 3. **Create ADR file** -- `Write` the file at `docs/adr/ADR-NNN-<slug>.md` using the standard template: ```markdown # ADR-NNN: <Title> - **Status**: proposed - **Date**: <today's date YYYY-MM-DD> - **Deciders**: <leave blank for author to fill> - **Tags**: <leave blank> ## Context <!-- What is the issue that motivates this decision? --> ## Decision <!-- What is the change that we are proposing? --> ## Consequences ### Positive - ### Negative
- When to use
- Steps
What does the adr-create skill do?
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
How do I install it?
Run `npx skills add ruvnet/ruflo --skill adr-create --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.