Keysat
b7625c4e83
Promote STATUS.md from an opt-in offer to standard behavior: every /roundup run now writes the report to ~/Projects/standards/STATUS.md (overwritten), shows it inline, and commits + pushes only that file so the portfolio state is diffable over time — the same durability reflex as /capture. STATUS.md remains the only file roundup writes; all project repos stay read-only. Updates guide (new Phase 4), wrapper, ROADMAP item 2, README, and Current state.
1.2 KiB
description, argument-hint, allowed-tools
| description | argument-hint | allowed-tools | ||
|---|---|---|---|---|
| Cross-project status roundup — read every repo's AGENTS.md/ROADMAP.md plus the inbox, compile one priority-grouped to-do list across all projects, and write it to a tracked STATUS.md snapshot in the standards repo |
|
Bash, Read, Grep, Glob, Agent, Write |
Produce a portfolio-wide status roundup across all my projects under ~/Projects.
Optional focus from me (may be empty): $ARGUMENTS
Your complete orchestration guide — how to discover repos, the read-only reader you fan out per repo, the inbox pass, and the report format — is at:
~/Projects/standards/guides/roundup.md
Read it in full first, then follow it exactly. If you cannot read that file, stop and report precisely that — do not improvise the roundup.
Write exactly one file — the STATUS.md snapshot in the standards repo (committed + pushed
so it's tracked and diffable over time); every project repo stays read-only. Don't decide for
me: gather and group by the priorities you find, but do not rank the projects against each
other or tell me what to work on — deciding the best use of time is mine. After you present
the report, help me reason about ordering only if I ask.