rlm-subagent
Subagent-Driven Execution with Fallback
This skill provides parallel subagent execution for RLM Phase 3 (Implementation), Phase 3.5 (Code Review), and Phase 4 (Testing) with automatic fallback to sequential mode when subagents are unavailable.
Trigger examples
Parallelize Phase 3 across independent sub-phasesDispatch an implementer subagent for each SPRun a separate code-reviewer subagent before Phase 4Subagents aren't available; fall back to sequential mode
Quick Reference
| Scenario | Action |
|---|---|
| Multiple independent sub-phases | Use Parallel Mode (subagents) |
| Single sub-phase or subagents unavailable | Use Sequential Mode (fallback) |
| Code review needed | Use Phase 3.5 (subagent or self-review) |
| Parallel testing | Use Phase 4 parallel dispatch |
More from try-works/rlm-workflow-acp
rlm-tdd
Use when implementing any code in RLM Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first. Trigger phrases: "implement this", "add feature", "fix bug", "write a failing test", "TDD".
3rlm-debugging
Use when RLM requirement involves debugging a bug, test failure, or unexpected behavior. Insert Phase 1.5 between Phase 1 and Phase 2 to perform systematic root cause analysis before attempting any fixes. Trigger phrases: "debug", "investigate", "failing tests", "crash", "root cause".
3rlm-workflow-acp
Orchestrate the RLM repo workflow end to end with strict sequential phase gates, locked artifacts, traceability, TODO discipline, and optional ACP delegation to Kimi via `acpx`. Use for requests like "Implement requirement <run-id>", "Run RLM Phase <N>", "resume requirement", "lock Phase <N>", or "verify locks".
3rlm-worktree
Use when starting any RLM requirement to set up an isolated git worktree. Required before Phase 1. Create an isolated workspace, verify the worktree directory is safe to use, run project setup, confirm a clean test baseline, and prevent direct main/master branch work.
3