0 Fork 0

mirror of https://github.com/garrytan/gstack.git synced 2026-11-12 19:44:48 +01:00

Files

T

garrytan c325f5dba1 ship, review, land-and-deploy, landing-report: fix stale cross-references (s06 H1, s06 H2, s06 H3, s06 H4, s06 H5, s06 H8, s06 M6)

- H1: TODOS-format cites /ship Step 14, not 5.5.
- H2: the land readiness review is the checklist /ship applies in Step 9 (there
  is no Step 3.5).
- H3: the Apple adapter names the no-credential-talk rule by location instead
  of 'line 14' (it renders at line 16).
- H4: greptile triage diffs against origin/<base> from the caller's detected
  base, not origin/main.
- H5: the land Important Rules recap matches the steps (4-minute CI rounds in
  Step 3; 30 seconds for merge readback and deploy status).
- H8: landing-report calls the util once per bump level (four), and drops the
  unsupported 'cached by bun' claim.
- M6: landing-report says what its base detection does instead of claiming
  it matches other skills.
No test pins the removed text. expected red until the regeneration commit

2026-10-03 00:14:50 +00:00

1.6 KiB

Raw Blame History

TODOS.md Format Reference

Shared reference for the canonical TODOS.md format. Referenced by /ship (Step 14) and /plan-ceo-review (TODOS.md updates section) to ensure consistent TODO item structure.

File Structure

# 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:

### <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:

**Completed:** vX.Y.Z (YYYY-MM-DD)

1.6 KiB Raw Blame History