Track status
Agent OS is a management layer for complex, multi-agent AI projects. Instead of letting agents get lost in endless conversational loops, it enforces a disciplined workflow: upfront planning, shared context, scoped work tracks, and strict quality gates — so every agent stays focused, coordinated, and aligned from start to finish.
npx -y skills add designgrappler/agent-os --skill track-statusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Shows a one-screen summary of all tracks — ID, description, status, and flags. Read-only.
SKILL.md
0.9 KB, as published. Nobody here has run it
Instructions
Read docs/context/tracks.md.
If the file does not exist or has no tracks, output:
No tracks found. Run
/start-sprintto open a sprint first.
Otherwise, produce this summary:
## Track Status
| Track | Description | Status | Flags |
|-------|-------------|--------|-------|
| <ID> | <task name> | <status> | <exit record notes or —> |
- Read status directly from the
Status:field in each track entry. Do not infer. - Flags: if the Exit Record has a filled
What happened:orNext steps:field, include a one-word summary (e.g. "blocked", "deferred"). Otherwise use—. - No writes. No edits. Read only.