fix(ux): operator command-surface friction - #5
Merged
Conversation
Operator command surface friction: status dumped full archive and stale in-progress headers; bare /do-work suggested capture on drained projects; capture/go fallbacks used non-actionable next-step copy; help opened on a 25-row command wall without a primary loop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Frictions (this PR)
1. Status dumps full archive
Flow:
/do-work status(idle project) Severity: S1 Type: Extra work / Feedback gapExpected: Situation room shows live work (and a short recent-done tail).
Actual: ~300-line table of every archived REQ; unusable scan.
Change: Cap unscoped archive rows to 15 (newest); totals still count all; note how to scope. Idle cue when backlog+working empty.
Evidence after: Unscoped status is 25 lines with "… and 279 more archived"; tests case
archive-cap.2. Archived REQs show stale
in-progressFlow: status on archived REQ with stale header Severity: S1 Type: Confusion
Expected: Archive location means done.
Actual: Status column echoed file header (
in-progress).Change: Archive bucket always renders Status
done.Evidence after:
REQ-089on UR-024 showsdone; testarchive-status-done.3. Help suggests capture on drained projects
Flow: bare
/do-workwith empty backlog + archive Severity: S1 Type: ConfusionExpected: Start new work / status (or capture only for zero-REQ URs).
Actual: "URs exist but backlog empty" always suggested capture.
Change: Help distinguishes zero-REQ URs vs archive-drained idle.
Evidence after:
agents/help.mdbranches A/B.4. Vague next-step copy after capture / go
Flow: capture/go when
next_steps.enabledfalse Severity: S2 Type: DiscoverabilityExpected: Copy-pasteable
/do-work go UR-NNN/ status.Actual: "run verify… or run the loop"; go printed nothing.
Change: Concrete commands in capture.md and go.md.
5. Help opens on full command wall
Flow: bare
/do-workfirst screen Severity: S2 Type: ConfusionExpected: Primary loop (start/go/status) first.
Actual: 25-row Quick Reference only.
Change: SKILL.md Primary loop section above full table.
Verification
/do-work statusunscoped + scoped UR-024/UR-045bash lib/tests/synth-status.test.sh— 10 cases, 0 failuresResiduals
proven=0for pre-proof-era REQs — needs product decision on historical rollup (not a local copy fix).Requirements preserved
No auth/ACL/validation gates weakened; status remains read-only; archive files on disk unchanged.