gstack/office-hours
Chris Walton 44e2b8d6db fix: office-hours marks sessions "success" without writing design doc
The office-hours skill can complete the final telemetry block and log
`outcome:success` even when Phase 5 (design doc write) was skipped —
e.g., when a session ends early or the conversation pivots to
implementation. The timeline shows `event:completed` with no
corresponding `*-design-*.md` file on disk, silently losing the
artifact that downstream skills (/plan-ceo-review, /plan-eng-review)
depend on.

Fix: add a "Pre-Telemetry: Verify Design Doc Artifact" section that
runs before the preamble's telemetry block. It re-derives SLUG (since
shell state doesn't persist between Bash tool calls), uses the
preamble's `~/.gstack/sessions/$PPID` touch file as a session-start
time reference, and looks for a fresh design doc written after that
point. Emits `ARTIFACT_STATUS: ok` or `no_doc`.

The Important Rules section now instructs Claude to use this result
to drive OUTCOME — never log `success` when `no_doc`.

Repro: observed in apex-coach session 2026-04-12 — timeline logged
`duration_s:"0"`, `session:"unknown"`, `outcome:"success"`, but no
design doc exists in ~/.gstack/projects/apex-coach/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-17 11:22:16 -04:00
..
SKILL.md fix: office-hours marks sessions "success" without writing design doc 2026-04-17 11:22:16 -04:00
SKILL.md.tmpl fix: office-hours marks sessions "success" without writing design doc 2026-04-17 11:22:16 -04:00