explore-critique-implement

Coordinates iterative explore-critique-implement cycles for uncertain problem-solving with adversarial validation.

Updated May 4, 2026
One-click install
npx skills add https://github.com/xaionaro/.config-codex --skill explore-critique-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-critique-implement
Source: https://github.com/xaionaro/.config-codex/tree/main/skills/explore-critique-implement
Command: npx skills add https://github.com/xaionaro/.config-codex --skill explore-critique-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solve complex, uncertain problems by orchestrating a persistent explorer to surface options, adversarially critique them via separate critic agents, then loop (implement → critique) until the critic finds nothing.

Core Features & Use Cases

  • End-to-end problem solving: explore multiple options, critique them, implement refinements, and re-iterate until maturity.
  • Adversarial critique: separated critic roles validate options, improving reliability and reducing bias.
  • Context-led iterations: maintain a project-understanding ledger and clear handoffs between roles to ensure traceability.

Quick Start

Initiate an Explore-Critique-Implement cycle for your current uncertain problem and observe how explorer options are produced and evaluated.

Frequently Asked Questions about explore-critique-implement

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

FAQPage Schema
How do I coordinate adversarial critique when solving complex problems with uncertain solution spaces?

Adversarial critique for uncertain problem spaces is coordinated by concurrently exploring options via dedicated agents, validating them through separate critic roles, and implementing refinements in iterative cycles until maturity is reached.

What is the best way to validate multiple plausible approaches for non-trivial software engineering problems?

Validating multiple plausible approaches requires a persistent explorer to surface options, followed by adversarial critique from separated roles to reduce bias, and iterative refinement loops to ensure traceable and auditable decisions.

How do I implement iterative exploration with explicit blocker handling for traceable decisions?

Iterative exploration with traceable decisions is implemented by maintaining a project-understanding ledger, enforcing structured agent roles, and handling explicit blockers during the explore, critique, and implement loop.

Does iterative exploration with adversarial critique require any specific dependencies or environment setup?

Iterative exploration with adversarial critique requires no external dependencies or environment setup, relying entirely on internal agent coordination to manage the persistent context and structured handoffs.

When should I use an explore-critique-implement cycle instead of standard problem solving?

An explore-critique-implement cycle should be used for non-trivial problems with uncertain solution spaces where multiple plausible approaches must be weighed, validated, and refined through persistent context and adversarial critique.