Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)
Review the instructions the agent will receive before you install.
Persists every ADR under */docs/adr/ or */docs/adrs/ to the adr-patterns namespace and every relationship (supersedes / amends / related / depends-on) to adr-edges. Handles both ADR formats found in the Ruflo monorepo:
# ADR-097: Title heading + **Status**: Proposed lineid: ADR-NNNN, status: Proposed)Implementation is in scripts/import.mjs (one Bash call) rather than dozens of per-ADR MCP tool calls — same effective behavior, materially faster, dual-format-aware, and false-positive-resistant for issue numbers.
Run the importer:
node plugins/ruflo-adr/scripts/import.mjs
Optional env:
IMPORT_FORMAT=json — emit JSON instead of markdownIMPORT_DRY_RUN=1 — parse + summarize, skip persistenceADR_ROOT=/path — scan a different root (default: cwd)Inspect the summary — total ADRs, stored count, by-status breakdown, edge counts, dangling refs, status mismatches.
Verify graph integrity (optional but recommended) via the sibling adr-verify skill, which runs scripts/verify.mjs and exits 1 on cycles.
Search semantically via mcp__plugin_ruflo-core_ruflo__memory_search against the populated namespace:
memory_search --query "federation budget" --namespace adr-patterns
adr-patterns namespace, key <ADR-id>::<basename>, value (text):
<title> — <first paragraph of Context>
file: <relative path>
status: <Proposed|Accepted|Superseded|...>
date: <ISO date>
tags: <comma-separated>
adr-edges namespace, deterministic key <relation>:<FROM>__<TO>, value:
{ "from": "ADR-097", "to": "ADR-086", "relation": "related", "capturedAt": "<ISO>" }
Both ADR records and relationship edges are stored with explicit upsert
semantics. Re-running adr-index refreshes changed metadata in place and does
not create duplicate copies of an unchanged semantic edge.
#1697 / commit abc123 / PR 1234 references inside ADR bodies are stripped before regex extraction so they don't get misread as ADR-1697 etc. See extractAdrRefs() in scripts/import.mjs.
adr-index only ever adds/upserts. If an ADR file was deleted (or a relation line removed from a surviving file), the row it wrote stays forever — adr-verify won't catch it either, since an orphan has no dangling ref and forms no cycle. Use the sibling adr-reindex skill to reconcile a deletion (issue #2666).
adr-create — produces the ADR files this skill consumesadr-review — runs over adr-patterns for compliance checksadr-verify (sibling skill) — runs scripts/verify.mjs for graph-integrity gatingadr-reindex (sibling skill) — drop-and-rebuild reconcile for a deleted ADR file (this skill can only add, never remove)No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.
Coordinate multiple AI agents by adjusting their communication structure and task assignments as workloads change. The skill describes performance monitoring, switching coordination patterns, forecasting agent capacity, and validating changes with rollback when performance worsens.