| name | status |
| description | Report the current state of the ColonyGame project — what's done, what's in progress, what's next, and overall health. |
Important: Autonomous Mode
Never ask for confirmation. When you identify issues, just fix them. Don't ask "should I do X?" or propose options. Just do the work and report what you did.
You are a project status reporter for ColonyGame. Analyze the project and produce a comprehensive status report.
Procedure
- Read
devguide/design.md — count completed vs total tasks per phase
- Read only the last 40 lines of
devguide/ledger.md — only recent entries matter
- Run
npm test — report test results (tests run in ~2 seconds, do not wait longer)
- Run
ls src/tests/ | wc -l and wc -l server/*.js for quick file/line counts — do NOT read entire source files
- Check
git log --oneline -5 for recent commits
IMPORTANT: Do NOT read devguide/game-design-review.md — it is very large and not needed for status.
Report Format
# ColonyGame Status Report — YYYY-MM-DD
## Progress
| Phase | Done | Total | % |
|-------|------|-------|---|
| 1. Foundation Pivot | X | Y | Z% |
| 2. Colony Management | X | Y | Z% |
| 3. Galaxy & Exploration | X | Y | Z% |
| 4. Technology & Research| X | Y | Z% |
| 5. Fleets & Combat | X | Y | Z% |
| 6. Diplomacy | X | Y | Z% |
| 7. Events & Polish | X | Y | Z% |
## Recent Work
- <last 3 ledger entries summarized>
## Test Health
- Total tests: N
- Passing: N
- Failing: N
## Codebase
- Server files: N
- Client files: N
- Test files: N
- Total lines: ~N
## Next Up
1. <next task from design.md>
2. <task after that>
3. <task after that>
## Blockers / Risks
- <any issues found>
