Convert user requirements into a formal constraint set during RPI Research.
npx skills add https://github.com/1molchuan/oh-my-ccg --skill oh-my-ccg-research
Please help me install this Agent Skill. Skill: oh-my-ccg-research Source: https://github.com/1molchuan/oh-my-ccg/tree/main/skills/oh-my-ccg-research Command: npx skills add https://github.com/1molchuan/oh-my-ccg --skill oh-my-ccg-research
Converts user requirements into a formal constraint set during the RPI Research phase.
Describe your requirement to start the RESEARCH phase.
High-intent search queries and answers about installing and using this skill.
To convert user requirements into verifiable constraints, you start the RPI Research phase to orchestrate codebase exploration and parallel analysis across Codex and Gemini, producing a unified constraint set.
Yes, the RPI Research workflow supports state persistence by retrieving the current RPI state for safe transitions and saving progress, allowing you to resume the constraint synthesis workflow after a session clear.
Yes, you can use OpenSpec integration during constraint analysis to optionally create or attach an OpenSpec change, ensuring requirements artifacts are tracked throughout the parallel Codex and Gemini exploration.
The best way to derive hard and soft constraints is by inspecting the codebase to surface relevant patterns and interfaces, then running parallel constraint exploration across Codex and Gemini to synthesize verification criteria.
To start the RESEARCH phase for formal constraint set generation, you simply describe your requirement, which triggers state restoration, codebase exploration, and parallel analysis to merge insights into unified constraints.
1molchuanVerify MCP, Codex, and Gemini endpoints and initialize RPI state.
rpelizzaCoordinate multiple AI agents for parallel tasks with adversarial verification.
arestivoGenerate OpenSpec implementation artifacts in dependency order from a change.
BellaBeIdentify and classify constraints as hard, soft, or unknown into guardrails.
