qualia-resume

Reconstruct paused workflow context and route to the next action.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restore context after a pause in a Qualia workflow by summarizing what was done, what's in progress, and what's next, so you can pick up where you left off.

Core Features & Use Cases

  • Reconstructs session context from .continue-here.md, STATE.md, or Git history to resume planning, building, or verifying stages.
  • Detects incomplete work and flags pending tasks or blockers to maintain continuity.
  • Routes to the correct next action and presents a concise summary to help you decide your next command.

Quick Start

Identify a paused session and trigger resume to continue the workflow.

Frequently Asked Questions about qualia-resume

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

FAQPage Schema
How do I resume a paused workflow and restore context from previous sessions?

To resume a paused workflow, trigger the resume function to reconstruct context from .continue-here.md, STATE.md, or Git history. It extracts previous progress, detects incomplete work, and routes you to the correct next action with a summary and recommended command.

What is the best way to pick up where I left off in a multi-phase planning project?

The best way to pick up where you left off is to trigger a context resume that reads STATE.md or .continue-here.md. It summarizes completed work, flags pending tasks or blockers, and presents a recommended next command to maintain continuity across planning phases.

How does context reconstruction from Git history work for paused sessions?

Context reconstruction from Git history works by analyzing commit records to rebuild session state when explicit state files are missing. It extracts what was done, detects incomplete work, and routes you to the next action needed to continue the paused workflow.

Can I use state management files to detect incomplete work and blockers?

Yes, you can use state management files like STATE.md and .continue-here.md to detect incomplete work. The resume function reads these files, flags pending tasks and blockers, and displays a summary banner to help you decide your next command.

Do I need Git history to resume context if my state files are missing?

You do not strictly need Git history if state files exist, but it serves as a fallback for context reconstruction. When .continue-here.md or STATE.md are unavailable, Git history is analyzed to extract previous progress and route to the next action.

Why does my resumed session show a banner with a recommended next command?

Your resumed session shows a banner with a recommended next command because the context extraction process identifies incomplete work and routes you to the correct action. The summary reveal and banner display help you quickly decide how to proceed after the pause.