mcpField
A
adr-create

adr-create

github.com/ruvnetDevelopment80.0k741 installsUpdated today
Repository

About adr-create

A skill for creating numbered Architecture Decision Records and registering them in AgentDB. It also searches for related decisions and links them in both the ADR and the graph.

Key features

  1. 01Assign the next ADR number
  2. 02Create an ADR from a template
  3. 03Register decisions in AgentDB
  4. 04Search for related ADRs
  5. 05Link related decisions

Use cases

  1. 01Record a cross-cutting architecture choice
  2. 02Document technology or API decisions
  3. 03Connect a new decision to prior ADRs

MCP support

Uses MCP tools to store ADR data in AgentDB, search related decisions, add causal edges, and save patterns for later search.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ruvnet/ruflo --skill adr-create

After installing, type/adr-createin Claude Code to confirm it loaded.

Details

From the project README

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:

    # 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
-

### Neutral
-

## Links

  4. Store in AgentDB -- Call mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-store with:

    • key: mem:ADR-NNN
    • tier: semantic
    • value: a JSON-encoded string: { "id": "ADR-NNN", "title": "<title>", "status": "proposed", "date": "<today>", "file": "docs/adr/ADR-NNN-<slug>.md" }

  5. Find related ADRs -- Call mcp__plugin_ruflo-core_ruflo__memory_search with the title as query in namespace adr-patterns to find related decisions. If matches are found, add them to the Links section and call mcp__plugin_ruflo-core_ruflo__agentdb_causal-edge for each relationship with:

    • sourceId: mem:ADR-NNN
    • targetId: mem:ADR-RELATED
    • relation: depends-on

  6. Store pattern -- Call mcp__plugin_ruflo-core_ruflo__memory_store in namespace adr-patterns with key ADR-NNN and the title + context as value for future semantic search.

  7. Report -- Output the created file path, ADR number, and any related ADRs found.

Comments

Markdown supported