SDD — run panel anatomy

The proposed skeleton: header · stepper (status + navigation) · action zone (pinned to the true position) · document viewer (the hero) · on-demand drawer. Three states below.

Chip states — the whole vocabulary. Done and unlit derive from files; active from position; running from the live agent. Nothing else exists.
✓ done← artifact exists active← the position ◐ running← agent drafting now unlit← artifact missing · Start available ✓ viewing← outlined = document on screen
1 · Position: design — viewing requirements via chip navigation. The action zone stays pinned to the true position; browsing never moves the primary button.
AB#48213
Reopen an approved spec phase
.local-workflows/specs/reopen-approved-spec-phase/
✓ requirements› design› tasks› implement
starting design approves requirements.md
requirements.md PreviewEdit

Introduction

Reopening lets a person withdraw a phase's approval after later phases have run, without discarding any work already done…

Requirements

1. Reopen an approved phase

User Story: As a developer, I want to reopen requirements after tasks started, so that…

  1. WHEN a phase is reopened THEN the system SHALL mark downstream phases stale
  2. IF a task is mid-run THEN the system SHALL let it finish before marking it stale

Assumptions

· Reopen never deletes files — git is the undo · Stale phases stay openable…

▸ history & transcript  ·  2 attempts  ·  drafted 2h ago  ·  session: requirements
2 · Blocked — the only hard gate. The document leads with its questions; the primary action is disabled with the reason; Save & Revise is the way through.
requirements› design› tasks› implement
⏸ blocked — 2 unanswered questions in requirements.md
requirements.md PreviewEdit

Open Questions

  1. Should a reopened phase keep its previous approval timestamp, or reset it?
    → answer here…
  2. Is reopening allowed while a task is running?

Introduction

Reopening lets a person withdraw a phase's approval…

▸ history & transcript  ·  1 attempt  ·  drafted 10m ago
3 · Tasks — a document phase like requirements and design: same review loop, same Revise, same questions rule. Checkboxes render but are inert here; starting implement is what approves the plan.
✓ requirements› ✓ design› tasks› implement
Plan drafted — approve it by starting its first task in implement
tasks.md PreviewEdit

☐  1. Add Stale status to step model

· touches RunStore, DefaultRunner  _Requirements: 1.1, 1.2_

☐  2. Persist reopen decision in RunStore

☐  3. Invalidate downstream steps on reopen

☐  3.1 Cascade to expanded task nodes

☐  4. Re-arm gate on reopened phase

▸ history & transcript  ·  1 attempt  ·  drafted 5m ago  ·  session: tasks
4 · Implement — pure execution, no editing. ▶ opens a fresh native Copilot agent session with the spec + that one task; the checkbox in tasks.md is the completion state (watched). Git is the record.
✓ requirements› ✓ design› ✓ tasks› implement
2 done · 1 running · 4 queued ▶ opens a fresh Copilot agent session for that one task
tasks.md execution view — edit via Revise
☑1. Add Stale status to step modeldone
☑2. Persist reopen decision in RunStoredone
◐3. Invalidate downstream steps on reopenrunning · ghcp
☐3.1 Cascade to expanded task nodes▶ start
☐4. Re-arm gate on reopened phase▶ start

· touches RunStore, DefaultRunner  _Requirements: 1.1, 1.2_

☐5. Show reopen history in run panel▶ start
▸ task 3 transcript  ·  live  ·  14 files read · 2 written