status

Read project artifacts to report status, blockers, and next commands.

6|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill status-duongmquang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/status
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill status-duongmquang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides quick, session-aware project status updates that resume context across visits and sessions.

Core Features & Use Cases

  • Scan feature plans and read STATUS.md to surface current milestone status, blockers, and next actions.
  • Support multi-feature projects by aggregating PROGRESS.md and ROADMAP.md to produce a unified view.
  • Provide resume context for the next session, including last action and suggested next command.

Quick Start

Invoke /qf:status to generate the current project status report for the active feature.

Frequently Asked Questions about status

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

FAQPage Schema
How do I generate a project status report that resumes context from a previous session?

To generate a session-aware project status report, invoke the /qf:status command. This scans your project artifacts like STATUS.md and PROGRESS.md to surface current milestones, blockers, and the next suggested action.

How does project status tracking aggregate milestones across multiple features?

Project status tracking aggregates milestones across multiple features by reading PROGRESS.md and ROADMAP.md. This mechanism produces a unified view of your ongoing project, highlighting version details and current blockers.

Can I use session-aware status reporting for multi-feature roadmaps?

Yes, session-aware status reporting supports ongoing multi-feature projects with milestones and plans. It aggregates data from CONTEXT.md, PROGRESS.md, STATUS.md, and ROADMAP.md to provide a unified status view.

What is the best way to track project blockers and next actions using markdown artifacts?

The best way to track project blockers and next actions using markdown artifacts is to scan feature plans and read STATUS.md. This surfaces current milestone status and provides next-action guidance via /qf commands.

Does session-resume status reporting work without external dependencies?

Yes, session-resume status reporting works without external dependencies. It relies entirely on reading internal project markdown artifacts like CONTEXT.md, PROGRESS.md, STATUS.md, and ROADMAP.md to present current status.

Why does my project status report show suggested next commands instead of just milestones?

Your project status report shows suggested next commands to provide resume context for the next session. By reading project artifacts, it identifies your last action and offers next-action guidance via /qf commands to continue work.