solo-status-reporter

Generates comprehensive project status reports from session logs, decision logs, and workspace artifacts.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-status-reporter-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-status-reporter
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-status-reporter
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-status-reporter-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo developers and small teams lose track of project progress across sessions, phases, and deliverables. This Skill consolidates scattered project information into a single structured status report on demand. ## Core Features & Use Cases - Multi-source aggregation: Collects data from team_plan.md, decision_log.md, session logs, CLAUDE.md, and workspace folders to build a complete picture. - Structured report template: Produces a standardized Markdown report covering current phase, per-phase progress rates, deliverable versions, pending decisions, next todos, and blockers. - Targeted queries: Answers focused questions like current phase, deliverable lists, or next priorities without generating the full report. - Use Case: After a week of work, ask for a status summary and receive a dated report saved to docs/00_관리/status_report_YYYY-MM-DD.md showing Phase progress, artifact versions, and unresolved decisions. ## Quick Start Ask the assistant to show the current project status and it will gather plan, session, and decision data to produce a full status report.

Frequently Asked Questions about solo-status-reporter

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

FAQPage Schema
How do I generate a project status report from session logs?▼

Request a status summary and the Skill reads team_plan.md, the latest session log, decision_log.md, and workspace folders, then produces a structured Markdown report with phase progress, deliverables, and next todos.

What information sources does a project status report need?▼

This report combines five sources: team_plan.md for phase structure, the latest session log for completed work, decision_log.md for open decisions, workspace folder scans for deliverable versions, and CLAUDE.md for team and contract context.

How is phase progress percentage calculated?▼

Phase progress is estimated as completed deliverables divided by expected deliverables. Deliverable status is inferred from file versions: v1.0 or higher means complete, v0.x means in progress, and a missing file means not started.

Can I get only the next tasks instead of a full report?▼

Yes. Asking what to do next returns the Next Todo section with prioritized tasks plus any blockers, without generating the entire report. Similar focused queries work for deliverable lists or the current phase.

Where is the generated status report saved?▼

Reports are saved to docs/00_관리/status_report_YYYY-MM-DD.md, either automatically or when the user requests it. The report reflects the current point in time and should be regenerated as decisions or deliverables change.