haejwo-plan

Validate software development plans through independent reviewer critique and consensus.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/jungzuna/haejwo --skill haejwo-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: haejwo-plan
Source: https://github.com/jungzuna/haejwo/tree/main/haejwo/codex-skills/haejwo-plan
Command: npx skills add https://github.com/jungzuna/haejwo --skill haejwo-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in achieving pre-implementation consensus by involving an independent reviewer, ensuring that plans are thoroughly debated and validated before execution.

Core Features & Use Cases

  • Pre-Implementation Consensus: Engage an independent reviewer to debate and validate plans before any code is written.
  • Plan Drafting: Assist in drafting plans with goals, key decisions, alternatives, risks, and implementation checklists.
  • Reviewer Critique: Facilitate a structured review process with evidence-based rebuttals.
  • Disagreement Ledger: Track and resolve objections in a ledger, ensuring all issues are addressed.
  • Consensus or Escalation: Converge on a plan or escalate to a deadlock resolution if needed.
  • Consolidation and Reporting: Present the agreed plan and its implementation checklist in a concise format.

Quick Start

Use the haejwo-plan skill to initiate a planning session for a new feature, including drafting a plan and engaging an independent reviewer.

Frequently Asked Questions about haejwo-plan

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

FAQPage Schema
How do I validate a software development plan before implementation?

Pre-implementation plan validation is achieved by engaging an independent reviewer to debate and validate your drafted plan with evidence-based critiques. This process ensures goals, alternatives, and risks are thoroughly evaluated before execution begins.

What is the best way to draft a software plan with risk assessment?

Drafting a software plan with risk assessment involves creating a structured document covering goals, key decisions, alternatives, and implementation checklists. An independent reviewer then critiques the draft to ensure all potential risks are identified and addressed.

How do you resolve disagreements during plan review?

Disagreements during plan review are resolved using a disagreement ledger to track and address objections. If issues persist, the process supports escalating to a deadlock resolution to converge on a final consensus.

Can I use an independent reviewer for feature planning consensus?

Yes, initiating a planning session for a new feature engages an independent reviewer to validate the drafted plan. The reviewer provides structured critiques and evidence-based rebuttals to ensure consensus is reached before execution.

What should a pre-implementation plan checklist include?

A pre-implementation plan checklist should include goals, key decisions, alternatives, and identified risks. The consolidated checklist is finalized after an independent reviewer validates the plan and all objections in the disagreement ledger are resolved.

When do I need an independent review for software planning?

An independent review for software planning is needed for workflows requiring thorough validation before execution. It ensures plans are debated with evidence-based critiques, preventing costly implementation errors and unresolved objections.