alanshurafa
UserStructured refinement of any document between AI agents. Two agent roles bounce a file back and forth using disagreement markers until it converges. Open source, agent-agnostic, runs from any terminal.
Categories
Indexed Skills (3)
co-evolution
General-purpose co-evolution for questions, ideas, drafts, plans, specs, arguments, and markdown documents. Composes or bounces content between agents using [CONTESTED]/[CLARIFY] markers until it converges. Triggers on "co-evolution", "co-evolve", "co evolve", "bounce", "bounce document", "agent bouncer", "refine with another agent", "cross-AI refinement", "stress test this", "have two AIs review this", "adversarial review", and "red team this".
codex-build
Orchestrate Codex to BUILD code in the background while this Claude Code session (typically Opus) plans and reviews — never babysitting. The session composes the implementation plan, kicks the dev-review runner detached via a background Bash task with --preset codex-build, ENDS ITS TURN, and is woken on exit to run a schema-bound review gate (ACCEPT / REVISE / ESCALATE, max 2 rounds). Use when the user wants to "build with codex", "have codex build", "have codex implement", "orchestrate codex", "kick off codex in the background", "let codex grind", or "codex builds while I review". For an interactive single-session compose-bounce-execute loop with no detach, use /dev-review. For non-code document refinement, use /co-evolution.
dev-review
Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the designated agent executes the code. Replaces manual copy-paste between Claude Code and Codex desktops. Triggers on "dev review", "dev-review", "code review loop", "plan then execute", "have codex implement", "have codex review this diff", "developer reviewer loop", "compose execute verify", and explicit /dev-review requests. Generic co-evolution, bounce, cross-AI refinement, document refinement, and stress-test requests should use /co-evolution instead.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.