gsd-status-mod
Reviewed
at commit a058b57
For GSD projects: shows where work stopped and a STATE.md drift warning above the prompt, adds the handoff's next action to the hint line, and offers the…
0 upvotes
Log in to upvote or save- Made by
- Helen Kwok
- Pinned commit
-
a058b579baee5c0ed147aa9c33a52e20d4f38259 - What we checked
-
Shows a live pane and a status line for projects that use GSD, built from the .planning folder, the git reflog, your subagents and session usage. It only reads: it never writes project files, runs no programs and makes no network calls. It suggests the next GSD command in the prompt box (nothing runs until you press Enter) and keeps agent timing history in the plugin store.
Review details
Static review of the source at the pinned commit; not run. Registers session.start (commands /gsd-status and /gsd-board, opens the pane, one prompt suggestion), command.run, turn.start (keeps the typed prompt text, whitespace-collapsed, in an in-memory pane log unless it starts with '<'), tool.call (always calls next first, then only notes edited file names and errors), agent.spawn, turn.step, turn.complete, ui.close and ui.render for Pane, ToolUse, AssistantMessage, AbovePrompt and PromptHint. File access goes through $.fs.read/list/stat only: .planning/STATE.md, ROADMAP.md, HANDOFF.json, phase and stream folders, .git/logs/HEAD and, in a linked worktree, the main checkout's .planning and git logs found through the .git pointer file. The markdown reader opens only paths under .planning and checks the resolved real path stays inside .planning's real location, so symlinks cannot lead out; reply-mentioned .md names are mapped to existing .planning files only (absolute paths are ignored). Links in shown files open only in the reader and only when they are relative .md links inside .planning; other links are ignored. Uses $.session.root and usage (cost, context, rate limits), $.agent.list, $.clock, $.store.get/set (per-project agent run history: timestamps, agent type, phase, duration, token counts, model name; no text), $.ui.toast (optional toasts, user config), $.ui.open/scroll/invalidate, $.prompt.suggest. No fetch, process, model, env or eval use found; state-line.ts, history.ts, panel.ts and types.ts are pure and have type-only imports. Changes since the previous review (75219c5) are mainly a TypeScript conversion plus a work-streams, reader and forecast feature set, all within the same read-only footprint; the whole plugin was reviewed again. The README, tests and docs were not read; npm devDependencies are for tests and linting only and are not part of the plugin.
- What it uses
-
- Reads your prompts: yes
- Sees tool calls: yes
- Blocks or changes tool calls: no
- Reads or writes files: yes
- Runs programs on your machine: no
- Calls the model (uses tokens): no
- Sends data over the network: no
- Stores data: yes
- Shows something on screen: yes
A Claude Code mod for GSD projects: a live pane (roadmap, agent tree with forks, cost and context, work streams, session log, pace and fit forecast, timeline, trends, a markdown reader) plus a status band, a next-action hint and /gsd-status, read from .planning/.
Made this mod? Add a badge to your README
Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.
[](https://modsforclaude.com/mods/gsd-status-mod/)