skills.rest
Honigbart
HonigbartCOMMUNITY
Explore all skills by this author →
GitHub

brainstorm-critique

Critique planning artifacts with Codex CLI and write codex_critique.md.

1|Updated Apr 6, 2026
Search Tags:#automation#planning#review#artifact#critique#codex-cli
One-click install
npx skills add https://github.com/Honigbart/honeyflow --skill brainstorm-critique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorm-critique
Source: https://github.com/Honigbart/honeyflow/tree/main/brainstorm-critique
Command: npx skills add https://github.com/Honigbart/honeyflow --skill brainstorm-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, skepticism-driven critique of planning artifacts using Codex CLI, helping teams surface gaps, risks, and improvements before execution.

Core Features & Use Cases

  • Critique planning artifacts via Codex CLI to surface weaknesses and risk factors.
  • Supports both claude_brainstorm.md and evolution_plan.md as input and writes codex_critique.md; optionally emits ollama_critique.md when a local reviewer is available.

Quick Start

Use this skill by supplying a planning artifact in .ai/plans/<slug>/claude_brainstorm.md or evolution_plan.md and running Codex CLI to generate .ai/plans/<slug>/codex_critique.md.

Frequently Asked Questions about brainstorm-critique

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

FAQPage Schema
How do I critique a planning artifact to surface risks before execution?▼

You can critique a planning artifact by running Codex CLI as a skeptical external reviewer. This generates a dedicated critique file highlighting gaps, weaknesses, and risk factors to address before moving into execution.

What planning file formats can I use as input for a Codex CLI critique?▼

The critique process accepts claude_brainstorm.md and evolution_plan.md as input artifacts. These files must be located within the .ai/plans/<slug>/ directory to be processed by Codex CLI.

Does the critique process modify existing plan files or state?▼

No, the critique process preserves existing artifacts and does not modify plan state files. It operates within the namespace plan layout to safely output new critique files without altering your original planning documents.

Can I use a local Ollama reviewer alongside Codex CLI for plan critiques?▼

Yes, if a local Ollama reviewer is available, the process optionally emits an ollama_critique.md file alongside the standard codex_critique.md. This provides dual perspectives on your planning artifacts.

How do I generate a codex_critique.md file for my brainstorming plan?▼

Place your claude_brainstorm.md file inside the .ai/plans/<slug>/ directory and run Codex CLI. The tool analyzes the artifact and automatically writes the codex_critique.md output in the same directory.

What is the best way to review an evolution plan for structural weaknesses?▼

Using skepticism-driven critique via Codex CLI is an effective way to review an evolution plan. It evaluates the evolution_plan.md artifact and produces a structured critique document identifying potential weaknesses and improvements.

Related Skills

Explore More Product & Management Skills→
HonigbartHonigbart
1

brainstorm

Generate a structured brainstorming artifact from an initial idea.

Community
Intermediate
HonigbartHonigbart
1

quick-critique

Critique final_plan.md files with Codex CLI and write critique reports.

Community
Intermediate
breakcafebreakcafe
1

add-ollama-tool

Integrate an Ollama MCP server to list models and generate outputs in NanoClaw.

Official
Advanced
Lev-itLev-it

swot-analysis

Conduct SWOT analysis to identify strengths, weaknesses, opportunities, and threats.

Official
Intermediate