issue-plan-codex

Plan complex development work into debate-driven implementation issues with verification commands.

2|2|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/NavarrePratt/claude-settings --skill issue-plan-codex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-plan-codex
Source: https://github.com/NavarrePratt/claude-settings/tree/main/skills/issue-plan-codex
Command: npx skills add https://github.com/NavarrePratt/claude-settings --skill issue-plan-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables structured, debate-driven planning for complex software work by converting collaborative analysis into actionable issues and roadmaps, ensuring thorough discovery before execution.

Core Features & Use Cases

  • Phase 1: Discovery involving Claude Explore Agents and Codex cross-reference to map codebase, architecture, and risks
  • Phase 2: Planning with collaborative debate to synthesize a concrete implementation plan and create deferred issues
  • Phase 3: Discovery synthesis and final verification artifacts, including exact commands for linting, testing, and E2E checks

Quick Start

Activate the issue-plan-codex skill to generate a discovery-driven plan and create deferred implementation issues for the target feature.

Frequently Asked Questions about issue-plan-codex

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

FAQPage Schema
How do I turn AI debate analysis into actionable project issues?▼

To turn AI debate analysis into actionable project issues, this Skill decomposes complex development work into structured, debate-driven issues through multi-round analysis, ensuring thorough discovery before execution.

What is the best way to plan large-scale architectural software changes?▼

Planning large-scale architectural software changes requires a debate-driven approach that maps codebase risks, synthesizes discovery, and creates deferrable implementation issues with exact verification commands.

How do I break down complex development work into deferred implementation issues?▼

Breaking down complex development work into deferred implementation issues involves a discovery phase mapping architecture, a collaborative planning phase for iterative critique, and a final synthesis generating exact linting and testing commands.

Can I use collaborative debate to map codebase architecture and risks before execution?▼

Yes, you can use collaborative debate to map codebase architecture and risks before execution by applying discovery agents and cross-reference checks to synthesize a concrete implementation plan.

Does issue planning work for cross-team coordination on complex software efforts?▼

Issue planning works for cross-team coordination on complex software efforts by enforcing iterative critique and discovery synthesis, which generates deferrable implementation issues tailored for multi-round analysis.

Why does architectural planning require multi-round analysis before creating issues?▼

Architectural planning requires multi-round analysis because deep discovery and collaborative critique are necessary to synthesize defensible implementation roadmaps and generate exact verification commands before execution.