Agent skill
aidd-stage-research
Defines stage-specific research contract for subagent evidence reading and handoff behavior. Use when researcher subagent stage rules are needed.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/aidd-stage-research
SKILL.md
Scope
- Preload-only reference for
feature-dev-aidd:researchersubagent. - Defines stage behavior for research content work in the RLM-only pipeline.
- Keeps stage rules separate from the user-invocable
researchercommand skill.
Stage contract
skills/researcher/SKILL.mdowns orchestration only (state sync, pipeline run, explicit subagent call, handoff).agents/researcher.mdowns content updates (aidd/docs/research/<ticket>.md) based on existing evidence.- Subagent must not run shared RLM owner internals directly (
rlm_nodes_build.py,rlm_links_build.py,rlm_finalize.py). - Stage runtime may run bounded canonical finalize recovery once in
--automode; manual recovery paths remain outside subagent scope.
Command contracts
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_slice.py
- When to run: for bounded evidence lookup during researcher subagent analysis.
- Inputs: ticket/query tuple for targeted code-artifact context extraction.
- Outputs: slice evidence blocks suitable for research document updates.
- Failure mode: non-zero exit on missing pack/worklist artifacts or invalid query.
- Next action: surface blocker and handoff to RLM owner flow, then rerun slice when artifacts are ready.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_finalize.py
- When to run: handoff-only path when stage runtime reports pending RLM readiness after bounded auto recovery.
- Inputs:
--ticket <ticket>from deterministic pending output. - Outputs: finalized RLM readiness state (
readyor pending with reason code). - Failure mode: non-zero exit when upstream targets/manifest/worklist integrity is broken.
- Next action: resolve upstream integrity issues and rerun finalize via shared owner flow.
Evidence policy
- Read pack-first:
aidd/reports/research/<ticket>-rlm.pack.json. - If pack is missing, read
*-rlm.worklist.pack.jsonand return BLOCKED with explicit handoff. - Use slice for targeted evidence only:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_slice.py --ticket <ticket> --query "<token>".
- Avoid full JSONL scans unless pack/worklist is insufficient.
Handoff policy
- When
rlm_statusis not ready, return BLOCKED with deterministic next action:python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_finalize.py --ticket <ticket>.
- Pending output must include deterministic
reason_code+next_actionand append research handoff tasks. - When evidence is ready, update research document and return READY with next stage command hint.
Additional resources
- Stage command owner: ../researcher/SKILL.md (when: researcher stage orchestration order is unclear; why: keep stage entrypoint behavior aligned with no-fork command contract).
- Shared RLM owner: ../aidd-rlm/SKILL.md (when: pending/finalize ownership boundaries are unclear; why: enforce explicit handoff from stage to shared RLM runtime owner).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?