mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-02 11:45:20 +02:00
Garry Tan
41141007c1
* fix: log non-ENOENT errors in ensureStateDir() instead of silently swallowing
Replace bare catch {} with ENOENT-only silence. Non-ENOENT errors (EACCES,
ENOSPC) are now logged to .gstack/browse-server.log. Includes test for
permission-denied scenario with chmod 444.
* feat: merge TODO.md + TODOS.md into unified backlog with shared format reference
Merge TODO.md (roadmap) and TODOS.md (near-term) into one file organized by
skill/component with P0-P4 priority ordering and Completed section. Add shared
review/TODOS-format.md for canonical format. Add static validation tests.
* feat: add 2-tier Greptile reply system with escalation detection
Add reply templates (Tier 1 friendly, Tier 2 firm), explicit escalation
detection algorithm, and severity re-ranking guidance to greptile-triage.md.
* feat: cross-skill TODOS awareness + Greptile template refs in all skills
/ship Step 5.5: auto-detect completed TODOs, offer reorganization.
/review Step 5.5: cross-reference PR against open TODOs.
/plan-ceo-review, /plan-eng-review: TODOS context in planning.
/retro: Backlog Health metric. /qa: bug TODO context in diff-aware mode.
All Greptile-aware skills now reference reply templates and escalation detection.
* chore: bump version and changelog (v0.3.8)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: update CONTRIBUTING.md for v0.3.8 changes
Clarify test tier cost table (Tier 3 standalone vs combined), add TODOS.md
to "Things to know", mention Greptile triage in ship workflow description.
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
63 lines
1.6 KiB
Markdown
63 lines
1.6 KiB
Markdown
# TODOS.md Format Reference
|
|
|
|
Shared reference for the canonical TODOS.md format. Referenced by `/ship` (Step 5.5) and `/plan-ceo-review` (TODOS.md updates section) to ensure consistent TODO item structure.
|
|
|
|
---
|
|
|
|
## File Structure
|
|
|
|
```markdown
|
|
# TODOS
|
|
|
|
## <Skill/Component> ← e.g., ## Browse, ## Ship, ## Review, ## Infrastructure
|
|
<items sorted P0 first, then P1, P2, P3, P4>
|
|
|
|
## Completed
|
|
<finished items with completion annotation>
|
|
```
|
|
|
|
**Sections:** Organize by skill or component (`## Browse`, `## Ship`, `## Review`, `## QA`, `## Retro`, `## Infrastructure`). Within each section, sort items by priority (P0 at top).
|
|
|
|
---
|
|
|
|
## TODO Item Format
|
|
|
|
Each item is an H3 under its section:
|
|
|
|
```markdown
|
|
### <Title>
|
|
|
|
**What:** One-line description of the work.
|
|
|
|
**Why:** The concrete problem it solves or value it unlocks.
|
|
|
|
**Context:** Enough detail that someone picking this up in 3 months understands the motivation, the current state, and where to start.
|
|
|
|
**Effort:** S / M / L / XL
|
|
**Priority:** P0 / P1 / P2 / P3 / P4
|
|
**Depends on:** <prerequisites, or "None">
|
|
```
|
|
|
|
**Required fields:** What, Why, Context, Effort, Priority
|
|
**Optional fields:** Depends on, Blocked by
|
|
|
|
---
|
|
|
|
## Priority Definitions
|
|
|
|
- **P0** — Blocking: must be done before next release
|
|
- **P1** — Critical: should be done this cycle
|
|
- **P2** — Important: do when P0/P1 are clear
|
|
- **P3** — Nice-to-have: revisit after adoption/usage data
|
|
- **P4** — Someday: good idea, no urgency
|
|
|
|
---
|
|
|
|
## Completed Item Format
|
|
|
|
When an item is completed, move it to the `## Completed` section preserving its original content and appending:
|
|
|
|
```markdown
|
|
**Completed:** vX.Y.Z (YYYY-MM-DD)
|
|
```
|