aidd-rlm

Preload canonical RLM evidence workflows for subagent role tasks.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-rlm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-rlm
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/aidd-rlm
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-rlm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The aidd-rlm skill provides a shared, preload-only workflow for RLM evidence that ensures subagents operate against a canonical set of evidence operations, avoiding drift between roles.

Core Features & Use Cases

  • Preload matrix roles for common RLM tasks (slice, build, verify, finalize, pack) to ensure consistent behavior.
  • Centralizes RLM evidence handling and pack generation across agents, reducing duplication.
  • Use Case: Before executing a task in a multi-agent cycle, preload the aidd-rlm workspace so all agents share the same evidence workflow.

Quick Start

Load the shared RLM workflow for subagents and call the canonical entrypoints to perform slice, build, verify, finalize, and pack operations.

Frequently Asked Questions about aidd-rlm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize RLM evidence workflows across multiple subagents?

To standardize RLM evidence workflows across subagents, you preload a shared workspace using canonical Python entrypoints. This ensures agents operate against consistent slice, build, verify, finalize, and pack operations without role drift.

What is the best way to manage subagent roles like analyst and planner in an automation workflow?

Managing subagent roles like analyst and planner in an automation workflow is done by preloading a canonical matrix of roles. This centralizes evidence handling and pack generation to reduce duplication across agents.

How do I execute slice, build, and verify tasks consistently in a multi-agent cycle?

You execute slice, build, and verify tasks consistently by calling shared Python-based entrypoints like rlm_slice.py, rlm_nodes_build.py, and rlm_verify.py. These runtime scripts enforce consistent payload schemas and packaging conventions across agents.

Do I need specific dependencies to run RLM finalize and pack operations?

No specific dependencies are required to run RLM finalize and pack operations. The environment operates preload-only, utilizing built-in Python entrypoints like rlm_finalize.py and reports_pack.py to handle evidence packaging.

Why does subagent behavior drift when handling evidence in multi-agent cycles?

Subagent behavior drifts when handling evidence in multi-agent cycles due to the lack of a canonical RLM evidence workflow. Preloading a shared workspace before executing tasks ensures all agents share the same evidence operations and payload schemas.