qualia

Route project state and recommend the next CLI command for the current development phase.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The qualia skill eliminates uncertainty about what to do next by reading local project state and conversation context and recommending a single clear command or action to move your workflow forward.

Core Features & Use Cases

  • Smart routing: Classifies project status (no-project, handoff, mid-work, ready-to-plan/build/verify, blocked, shipped) and maps each situation to the precise framework command to run next.
  • Context-aware escalation: Detects persistent failure patterns or gap limits and suggests escalation paths or re-planning for team members.
  • Developer-facing UI guidance: Uses banner and next helpers to display the recommended command, alternative options, and explicit next steps.
  • Use Case: When you type /qualia or ask "what next", qualia inspects state.js, git status, and handoff files, then returns the single best command and rationale so you can continue immediately.

Quick Start

Type "what next" or "/qualia" to have qualia read the project state and tell you the exact next command to run.

Frequently Asked Questions about qualia

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

FAQPage Schema
How do I figure out what CLI command to run next in my development workflow?

To determine the next CLI command for your development workflow, qualia reads local repository state, git status, handoff files, and conversation context to map your current phase to a single recommended framework command.

What is project state routing and how does it detect workflow blockers?

Project state routing classifies your repository status into categories like mid-work, ready-to-plan, blocked, or shipped, detecting handoffs, uncommitted changes, and verification gaps to identify persistent failure patterns and suggest escalation paths.

How do I get the next command for my project phase using a CLI assistant?

You get the next command by typing /qualia or asking "what next" within your Claude-assisted local repository, prompting the skill to inspect state.js and git status before returning the exact command and rationale.

Can I use workflow routing to detect uncommitted changes and handoff files in local repositories?

Yes, you can use workflow routing in local repositories to detect uncommitted changes and handoff files, consuming state.js output and git status to classify your project situation and recommend the precise next action.

What's the best way to handle project phase transitions and verification gaps?

The best way to handle project phase transitions and verification gaps is to let a routing skill analyze your state.js output and conversation context, mapping situations to framework commands and UI banners that display explicit next steps.

Why does my development workflow get blocked during handoffs and how do I escalate?

Development workflows get blocked during handoffs due to persistent failure patterns or gap limits, and you escalate by using context-aware routing to suggest re-planning paths or escalation suggestions for team members.