Add /roundup cross-project status command
Fans out a read-only reader per repo over AGENTS.md/ROADMAP.md, folds in the standards inbox, and synthesizes one priority-grouped to-do list across all projects (including untriaged inbox items and proposed new projects). Reads and reports only — prioritizing across projects stays with the user.
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
---
|
||||
description: Cross-project status roundup — read every repo's AGENTS.md/ROADMAP.md plus the inbox and compile one priority-grouped to-do list across all projects
|
||||
argument-hint: [optional focus, e.g. "only P0/P1" or a subset of repos]
|
||||
allowed-tools: 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.
|
||||
|
||||
Read and report only: 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.
|
||||
Reference in New Issue
Block a user