hadi-planner

Transform feature requests into structured CSV backlogs with verification.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hadi-technology/phased-workflow --skill hadi-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hadi-planner
Source: https://github.com/hadi-technology/phased-workflow/tree/main/skills/hadi-planner
Command: npx skills add https://github.com/hadi-technology/phased-workflow --skill hadi-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of "agent drift" and poor planning in AI-driven development by enforcing a rigorous, two-stage orchestration process that turns fuzzy feature requests into machine-verifiable CSV backlogs.

Core Features & Use Cases

  • Structured Backlog Generation: Automatically decomposes high-level requests into a 14-column CSV backlog with mandatory rigor checks.
  • Independent Verification: Implements a two-pass, fresh-eyes review system that ensures code-intent alignment before any implementation begins.
  • Use Case: Use this skill to plan a complex feature rollout, ensuring that every task has a verified pattern scan, blast radius analysis, and multi-layer validation before handing it off to the Hadi Builder for autonomous execution.

Quick Start

Invoke the hadi-planner skill with your feature description to begin the interactive brainstorming and planning process.

Frequently Asked Questions about hadi-planner

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

FAQPage Schema
How do I turn a high-level software feature request into a machine-verifiable CSV backlog?

To generate a machine-verifiable CSV backlog, decompose high-level feature requests using a multi-stage planning and review orchestration process. This transforms fuzzy requests into a structured 14-column CSV backlog with mandatory rigor checks before autonomous execution.

What is the best way to prevent agent drift in AI-driven software development?

To prevent agent drift in AI-driven development, enforce a rigorous two-stage orchestration process with independent verification. A two-pass, fresh-eyes review system ensures code-intent alignment and structural integrity before any implementation begins.

How do I perform blast radius analysis and scope decomposition for complex feature rollouts?

Perform blast radius analysis and scope decomposition by applying multi-layer validation during backlog generation. This ensures every task within a complex software development workflow undergoes verified pattern scans and rigorous scoping before execution.

Does automated planning support independent verification for codebase mapping tasks?

Automated planning supports independent verification for codebase mapping through a two-pass, fresh-eyes review system. This mechanism ensures code-intent alignment and structural integrity by rigorously checking tasks before autonomous execution begins.

When do I need a structured CSV backlog for autonomous software execution?

You need a structured CSV backlog for autonomous software execution when handling complex software development workflows requiring rigorous scope decomposition. It satisfies requirements for structural integrity, blast radius analysis, and multi-layer validation before handing off to autonomous builders.

What are the limitations of using automated scoping for complex software development workflows?

Automated scoping for complex software development workflows requires a multi-stage planning and review orchestration process. It is limited by the need for independent verification and codebase mapping, meaning fuzzy feature requests must pass multi-layer validation before autonomous execution.