research-opportunity-investigator

To draft an RFC for ACP protocol integrations, define a research target, then proceed through scoping, discovery, deep analysis, opportunity assessment, and RFC generation with explicit source grounding and traceability to existing ACP specifications.

The best way to structure ACP research and gap analysis is using a phase-driven workflow that spans scoping, discovery, deep analysis, ACP context summarization, and opportunity assessment to map gaps traceable to existing specification sections.

Yes, you can enforce gate-based user confirmations during the RFC generation process, ensuring each phase of the research workflow receives explicit user approval before advancing to the next stage.

Source-grounded research ensures traceability to the ACP specification by requiring every claim to be explicitly sourced and mapping identified gaps directly to existing spec sections during RFC proposal generation.

Deliverables from a structured ACP research workflow include an ACP context summary, gap analyses, RFC drafts, and packaged final outputs ready for stakeholder review.

You need a gate-driven workflow for RFC development when performing rigorous research for ACP protocol integration, ensuring every phase from scope definition to deliverables packaging enforces explicit source grounding and traceability.