Quick project status — active plans, task progress, git state, and session history. Use when resuming work, checking progress, or handing off between sessions. Pass 'recent' to verify each task was actually completed.
From zenflownpx claudepluginhub brewpirate/zen-flow --plugin zenflowThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Show a quick snapshot of where things stand. Reads active plans, task state, git status, and session context to produce a concise status report.
No confirmation needed — this skill runs immediately and reports.
Modes:
/zenflow:status recent) — verifies each task was actually completed by checking the codebase, then stamps the plan with validated frontmattergit status --short
git log --oneline -5
git diff --stat
Report:
Scan resources/plans/ for all plans where frontmatter status is NOT complete. This catches planned, in-progress, and any other non-terminal state:
Use the Glob tool to find plan files, then Read each to check frontmatter. A plan is active if:
status: planned — not startedstatus: in-progress — work underwaystatus field is missing — assumed not completecompleteFor each active plan, report:
- [x] vs - [ ] in the planvalidated field if present (from recent mode)completed date if present (for recently finished plans)Check if any TaskList tasks exist in the current session:
Check the transcript for zen skill invocations:
Read the most recent entry from .claude/journal.jsonl (if it exists):
Triggered by: /zenflow:status recent or when the user asks to verify/validate a plan.
Deep mode is a recent work review habit — it verifies that plans from the last few days were actually completed, so nothing gets overlooked. Run it daily or before handoffs.
Deep mode only verifies plans with recent activity (last 72 hours). It finds them by:
completed date in the last 72hstatus: in-progressvalidated date (never verified)git log --since)Skip plans that already have validated date within the last 72h — they've been checked recently.
This keeps recent mode fast and relevant. Old plans that drifted are someone else's problem — recent mode catches fresh work that might have been missed or half-done.
For each recent plan, verify every task using three signals (most reliable first):
1. Tests (strongest signal) — do the test files exist and pass?
<project-test-command> {test-file-path}
If the plan specifies test files, run them. Passing tests prove the behavior works regardless of how the code evolved.
2. Commits — did the work happen?
git log --oneline --since="72 hours ago" -- {file-paths}
Check that commits exist for the expected files. The commit message doesn't need to match the task name exactly — just confirm the files were touched.
3. Files (weakest signal) — do the expected files exist? Check that files listed as "Create" exist. For "Modify" files, grep for key function names or types mentioned in the task.
Each task gets a verdict:
| Verdict | Meaning |
|---|---|
done | All files exist, changes verified, tests pass |
partial | Some changes present but incomplete |
missing | No evidence the task was implemented |
broken | Files exist but tests fail |
## Deep Verification: 245-realtime-notifications.md
### Task 1: SSE Event Schema — done
✓ packages/core/src/types/schema/sse-events.ts exists
✓ SSEEventSchema exported
✓ tests/unit/types/sse-events.test.ts — 4/4 passing
### Task 2: Stream Handler — partial
✓ packages/server/src/server/routes/sse.ts exists
✗ Missing: reconnection logic (described in step 4)
✓ tests/unit/routes/sse.test.ts — 3/3 passing
### Task 3: Client Subscriber — missing
✗ packages/frontend/src/lib/sse-client.ts does not exist
✗ No related commits found
Summary: 1 done, 1 partial, 1 missing, 0 broken
After recent verification, update the plan's frontmatter:
---
status: complete # or in-progress if tasks are missing/partial
validated: 2026-03-27
validated_summary: "3/5 done, 1 partial, 1 missing"
---
Frontmatter fields added by recent mode:
| Field | Type | Description |
|---|---|---|
validated | date | When recent verification was last run |
validated_summary | string | Quick verdict summary |
Only stamp status: complete if ALL tasks are done. If any are partial, missing, or broken, keep status: in-progress and report what needs attention.
## Status
**Branch:** feature/notifications (3 ahead of main, 2 uncommitted files)
**Active Plans:**
- 245-realtime-notifications.md — 3/5 tasks complete (60%)
- 246-audit-config.md — planned (not started)
**Current Session:**
- Tasks: 2 completed, 1 in progress, 2 pending
- Skills used: zenflow:idea → zenflow:plan → zenflow:dispatch (in progress)
- ⚠️ zenflow:check-work not yet invoked
**Last Journal (2026-03-26):**
- Worked on: SSE notification system
- Blocker: Rate limiting config unclear
/zenflow:status recent to verify everything was actually done