- Rebrand commits already in history (gsd → forge) - Sync pre-existing doc, docker, and CI config updates - All rebrand artifacts verified in place: * Native crates: forge-engine, forge-ast, forge-grep * Log prefixes: [forge] across 22+ files * Binary: ~/bin/sf-run * Workspace scopes: @sf-run/*, @singularity-forge/* * Nix flake: Rust toolchain ready System ready for: nix develop && bun run build:native Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.9 KiB
Captures & Triage
Introduced in v2.19.0
Captures let you fire-and-forget thoughts during auto-mode execution. Instead of pausing auto-mode to steer, you can capture ideas, bugs, or scope changes and let SF triage them at natural seams between tasks.
Quick Start
While auto-mode is running (or any time):
/gsd capture "add rate limiting to the API endpoints"
/gsd capture "the auth flow should support OAuth, not just JWT"
Captures are appended to .gsd/CAPTURES.md and triaged automatically between tasks.
How It Works
Pipeline
capture → triage → confirm → resolve → resume
- Capture —
/gsd capture "thought"appends to.gsd/CAPTURES.mdwith a timestamp and unique ID - Triage — at natural seams between tasks (in
handleAgentEnd), SF detects pending captures and classifies them - Confirm — the user is shown the proposed resolution and confirms or adjusts
- Resolve — the resolution is applied (task injection, replan trigger, deferral, etc.)
- Resume — auto-mode continues
Classification Types
Each capture is classified into one of five types:
| Type | Meaning | Resolution |
|---|---|---|
quick-task |
Small, self-contained fix | Inline quick task executed immediately |
inject |
New task needed in current slice | Task injected into the active slice plan |
defer |
Important but not urgent | Deferred to roadmap reassessment |
replan |
Changes the current approach | Triggers slice replan with capture context |
note |
Informational, no action needed | Acknowledged, no plan changes |
Automatic Triage
Triage fires automatically between tasks during auto-mode. The triage prompt receives:
- All pending captures
- The current slice plan
- The active roadmap
The LLM classifies each capture and proposes a resolution. Plan-modifying resolutions (inject, replan) require user confirmation.
Manual Triage
Trigger triage manually at any time:
/gsd triage
This is useful when you've accumulated several captures and want to process them before the next natural seam.
Dashboard Integration
The progress widget shows a pending capture count badge when captures are waiting for triage. This is visible in both the Ctrl+Alt+G dashboard and the auto-mode progress widget.
Context Injection
Capture context is automatically injected into:
- Replan-slice prompts — so the replan knows what triggered it
- Reassess-roadmap prompts — so deferred captures influence roadmap decisions
Worktree Awareness
Captures always resolve to the original project root's .gsd/CAPTURES.md, not the worktree's local copy. This ensures captures from a steering terminal are visible to the auto-mode session running in a worktree.
Commands
| Command | Description |
|---|---|
/gsd capture "text" |
Capture a thought (quotes optional for single words) |
/gsd triage |
Manually trigger triage of pending captures |