Menú
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
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)
Reconcile the ADR index against a DELETED ADR file or relation line by dropping and rebuilding adr-patterns + adr-edges from scratch (scripts/reindex.mjs). Use when adr-index alone leaves stale rows behind.
Review code changes against accepted ADRs for compliance violations
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
Run an Anthropic Claude Managed Agent — a cloud agent harness (container + filesystem + tools), the cloud counterpart of the local wasm-agent runtime
| name | adr-create |
| description | Create a new Architecture Decision Record with sequential numbering and AgentDB registration |
| argument-hint | <title> |
| allowed-tools | mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-store mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-query mcp__plugin_ruflo-core_ruflo__agentdb_causal-edge mcp__plugin_ruflo-core_ruflo__memory_store mcp__plugin_ruflo-core_ruflo__memory_search Bash Read Write Edit Grep Glob |
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.
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.
Slugify title -- Convert the title argument to a lowercase, hyphen-separated slug (e.g., "Use PostgreSQL for persistence" becomes use-postgresql-for-persistence).
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
Store in AgentDB -- Call mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-store with:
adr/ADR-NNN{ "id": "ADR-NNN", "title": "<title>", "status": "proposed", "date": "<today>", "file": "docs/adr/ADR-NNN-<slug>.md" }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 found, add them to the Links section and create causal edges with relation depends-on.
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.
Report -- Output the created file path, ADR number, and any related ADRs found.