qualia-plan

Generate and validate project phase execution plans with revision cycles.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qualia-plan
Source: https://github.com/Qualiasolutions/qualia-framework/tree/main/skills/qualia-plan
Command: npx skills add https://github.com/Qualiasolutions/qualia-framework --skill qualia-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and agent-driven workflows need a repeatable way to convert a roadmap phase into a concrete, verifiable set of tasks so work can be executed reliably and handoffs don't break the pipeline.

Core Features & Use Cases

  • Planner orchestration: Spawns a planner agent to break a phase into waves and tasks using project and phase context.
  • Plan validation loop: Runs a plan-checker that enforces seven rules with up to three revision cycles and escalates if blocked.
  • Gap-closure mode: Generates targeted surgical fixes for verification FAILs, writing a separate gaps plan.
  • Integrated state & routing: Writes plan files under .planning/, honors locked decisions, and transitions state before routing to build.
  • Use case: Use when preparing a software development phase that requires clear task breakdown, reviewer validation, and no scope creep.

Quick Start

Run /qualia-plan 2 to generate, validate, and save a phase 2 plan as .planning/phase-2-plan.md using the built-in checker and revision loop.

Frequently Asked Questions about qualia-plan

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

FAQPage Schema
How do I break down a project phase into executable tasks for agent orchestration?

Project phase task breakdown is achieved by spawning a planner agent that converts roadmap goals into waves of verifiable tasks and saves the output as a structured markdown plan file.

What is the best way to validate a task breakdown plan and prevent scope creep?

Plan validation runs an automated plan-checker enforcing seven rules with up to three revision cycles, escalating if blocked, ensuring strict scope adherence for development phases.

How do I generate a targeted gap-closure plan for failed verifications?

Gap-closure planning generates surgical fixes for verification failures, writing a separate targeted gaps plan file to resolve specific issues without disrupting broader project scope.

Can I use automated planning to honor locked decisions and transition project state?

Automated planning honors locked decisions, writes plan files under a planning directory, and transitions project state via state helpers before routing execution to build.

Does task breakdown planning support pre-plan research and decision capture?

Task breakdown planning supports optional pre-plan research and decision capture, allowing teams to gather necessary context before generating the final validated execution plan.

What happens when automated plan validation fails after three revision cycles?

When plan validation fails after three revision cycles, the automated checker escalates the blockage, preventing the transition to build until the structural plan issues are resolved.