Qsummary

Generate Haiku-style session summaries from QE state and task files.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qsummary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qsummary
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qsummary
Command: npx skills add https://github.com/inho-team/qe-framework --skill qsummary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarizes a session's work into a compact, high-clarity status report to inform users and future agents about progress and momentum.

Core Features & Use Cases

  • High-density session summaries generated in Haiku-style length (5-7 lines) to convey achievements, architectural shifts, and next steps.
  • Reads from .qe/state/unified-state.json, .qe/tasks/completed, and .qe/context/sessions/{sid}/SNAPSHOT_SUMMARY.md to capture token usage, completed tasks, and current vibe.
  • Ideal for wrap-ups, handoffs, or daily standups to maintain momentum and shared context.

Quick Start

Instruct the system to produce a Haiku-style 5-7 line summary for the current session using the latest state and task data.

Frequently Asked Questions about Qsummary

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

FAQPage Schema
How do I generate a concise session summary for agent handoff?

A session summary aggregates state, completed tasks, and context data to produce a compact status report. It captures progress and momentum to inform users and future agents during wrap-ups or handoffs.

What is the best way to create a brief status report for a QE session wrap-up?

The best way to create a brief status report is aggregating token usage, completed tasks, and current vibe into a high-density summary. It reflects the technical state to maintain momentum and shared context for daily standups.

How does a Haiku-style session summary work?

A Haiku-style session summary works by constraining output to 5-7 lines. It aggregates data from unified state, completed tasks, and snapshot summaries to convey achievements, architectural shifts, and next steps within the length limit.

Do I need a specific state file format to generate a context handoff summary?

Generating a context handoff summary requires specific state files. The system reads from a unified state JSON file, a completed tasks directory, and a snapshot summary markdown file to capture the current technical state and vibe.

Are there limitations to the length of a generated session state summary?

The length of a generated session state summary is limited to 5-7 lines. It adheres to a strict Haiku-based output format, ensuring the summary remains a highly compact and high-clarity status report.