aidd-stage-research

Define stage-specific research contracts for subagent evidence reading and handoff.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This stage defines stage-specific research contracts that govern subagent content reading and handoff, ensuring consistent orchestration across the research pipeline.

Core Features & Use Cases

  • Stage contracts establish clear boundaries between stage orchestration and content updates.
  • They specify how subagents read evidence and hand off results to upstream stages.
  • Use Case: when you need deterministic stage behavior around evidence handling and handoff in RLM pipelines.

Quick Start

Configure the aidd-stage-research stage to enforce stage-specific evidence reading and handoff rules for subagents.

Frequently Asked Questions about aidd-stage-research

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

FAQPage Schema
How do I separate orchestration from content updates in a research pipeline?

Stage research contracts separate orchestration from content updates by specifying policy details and interfaces for stage runtime, ensuring subagent evidence reading and handoff remain deterministic.

What are subagent research contracts and when do I need them?

Subagent research contracts are stage-specific policies that govern evidence reading and handoff triggers. You need them when you require deterministic stage behavior around evidence handling in RLM-enabled research pipelines.

How do I coordinate ticket-level evidence flow between pipeline stages?

You coordinate ticket-level evidence flow by applying stage research contracts to the RLM-enabled pipeline, which specify interfaces for handoff triggers and govern how subagents read evidence and pass results upstream.

How do I enforce deterministic stage behavior for subagent handoffs?

You enforce deterministic stage behavior by configuring stage research contracts that specify policy details and interfaces for stage runtime, governing exactly how subagents read evidence and execute handoff triggers.

Does this stage research approach work without external dependencies?

Yes, this stage research approach operates without external dependencies, relying entirely on its internal policy details and interfaces to govern subagent evidence reading and handoff within the RLM pipeline.

What are the limitations of using stage contracts for subagent orchestration?

Stage contracts are limited to governing evidence reading and handoff boundaries within RLM-enabled pipelines; they do not manage content updates directly, requiring orchestration to remain separate from content modifications.