Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Create a new Architecture Decision Record with sequential numbering and AgentDB registration
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | -39% | 0% |
| case-11 | ✗→✓ | ▲ Improved | -41% | 0% |
| case-12 | ✗→✓ | ▲ Improved | -42% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-14 | ✗→✓ | ▲ Improved | -10% | 0% |
Create a new Architecture Decision Record with the next sequential number, register it in the AgentDB graph, and link it to related ADRs.
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.
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.use-postgresql-for-persistence).Write the file at docs/adr/ADR-NNN-<slug>.md using the standard template:markdown # ADR-NNN: <Title>
## Context
<!-- What is the issue that motivates this decision? -->
## Decision
<!-- What is the change that we are proposing? -->
## Consequences
### Positive -
### Negative -
### Neutral -
## Links
mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-store with:mem:ADR-NNNsemantic{ "id": "ADR-NNN", "title": "<title>", "status": "proposed", "date": "<today>", "file": "docs/adr/ADR-NNN-<slug>.md" }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:mem:ADR-NNNmem:ADR-RELATEDdepends-onmcp__plugin_ruflo-core_ruflo__memory_store in namespace adr-patterns with key ADR-NNN and the title + context as value for future semantic search.Other measured skills in the registry, with their headline benchmark lift.