بنقرة واحدة
loop-worker
Run Ruflo background workers using Claude Code native /loop scheduling
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run Ruflo background workers using Claude Code native /loop scheduling
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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.
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
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
| name | loop-worker |
| description | Run Ruflo background workers using Claude Code native /loop scheduling |
| argument-hint | <worker-name> |
| allowed-tools | Bash(npx *) mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch mcp__plugin_ruflo-core_ruflo__hooks_worker-status ScheduleWakeup |
Use /loop for in-session periodic workers. Cache-aware delays keep prompt cache warm:
min(270, cache_ttl * 0.9) -- default 270sDispatch a worker via MCP: mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch({ trigger: "WORKER_NAME" })
Then schedule the next iteration: ScheduleWakeup({ delaySeconds: 270, reason: "next WORKER_NAME iteration" })
| Worker | Interval | Description |
|---|---|---|
| audit | 270s | Security analysis |
| optimize | 270s | Performance optimization |
| consolidate | 600s | Memory consolidation |
| predict | 270s | Predictive preloading |
| map | 600s | Codebase mapping |
| testgaps | 270s | Test coverage analysis |
| document | 600s | Auto-documentation |
| benchmark | 600s | Performance benchmarking |
MCP tool responses include [LOOP_SUGGESTION] and [CRON_SUGGESTION] hints -- follow them.