ec7e49a64c
* test(#3576): gate shipped reference citations on the canonical resolvable form Failing-first gate for #3576: a backticked bare references/<name>.md cite resolves from no install location (agents, workflows, and references all install where a bare relative references/ path is dead). The gate walks the runtime-loaded trees the issue prescribes, strips @~/ include tokens PER-TOKEN (a line-skip guard would miss a bare cite sharing a line with an include — the issue-named trap), pins the genuinely relative ../ href and canonical forms as non-offenders, and checks canonical cite targets exist. 43 offenders today across 19 files. * fix(#3576): repair all 43 dead references/ cites to the canonical resolvable form Every backticked bare references/<name>.md cite across the 19 shipped files rewritten to gsd-core/references/<name>.md — the form every required_reading block and @~/ include already uses, and the only form that resolves from any install location. All 20 cited targets verified to exist; the one genuinely relative href (plan-phase.md's ../references/mvp-concepts.md) is untouched (the repair is backtick-anchored). Growth acks: new fragment for the three first-time paths, #3206-pattern appends to the five fragments already naming the other grown files (two ack sources may never name the same path). execute-phase.md lands at 93,391/93,400 and gsd-executor.md at 49,150/49,152 — exactly the issue's projections; every repair fits. * fix(#3576): drop stale default.md growth ack (nested modes file is hash-attributed, not growth-ratcheted) Review finding: the emitted-attribution ratchet covers only top-level workflows/ + agents/ files; discuss-phase/modes/default.md's delta is source-attributed, so acknowledging its growth is a stale entry the differential lane fails on. * chore(#3576): add changeset fragment * chore(#3576): backfill changeset pr number --------- Co-authored-by: sim <sim@local>
104 lines
3.9 KiB
Markdown
104 lines
3.9 KiB
Markdown
# Gate Prompt Patterns
|
|
|
|
Reusable prompt patterns for structured gate checks in workflows and agents.
|
|
|
|
**For checkpoint box format details, see `gsd-core/references/ui-brand.md`** -- checkpoint boxes use double-line border drawing with 62-character inner width.
|
|
|
|
## Rules
|
|
|
|
- `header` must be max 12 characters
|
|
- `multiSelect` is always `false` for gate checks
|
|
- Always handle the "Other" case (user typed a freeform response instead of selecting)
|
|
- Max 4 options per prompt -- if more are needed, use a 2-step flow
|
|
|
|
---
|
|
|
|
## Pattern: approve-revise-abort
|
|
3-option gate for plan approval, gap-closure approval.
|
|
- question: "Approve these {noun}?"
|
|
- header: "Approve?"
|
|
- options: Approve | Request changes | Abort
|
|
|
|
## Pattern: yes-no
|
|
Simple 2-option confirmation for re-planning, rebuild, replace plans, commit.
|
|
- question: "{Specific question about the action}"
|
|
- header: "Confirm"
|
|
- options: Yes | No
|
|
|
|
## Pattern: stale-continue
|
|
2-option refresh gate for staleness warnings, timestamp freshness.
|
|
- question: "{Artifact} may be outdated. Refresh or continue?"
|
|
- header: "Stale"
|
|
- options: Refresh | Continue anyway
|
|
|
|
## Pattern: yes-no-pick
|
|
3-option selection for seed selection, item inclusion.
|
|
- question: "Include {items} in planning?"
|
|
- header: "Include?"
|
|
- options: Yes, all | Let me pick | No
|
|
|
|
## Pattern: multi-option-failure
|
|
4-option failure handler for build failures.
|
|
- question: "Plan {id} failed. How should we proceed?"
|
|
- header: "Failed"
|
|
- options: Retry | Skip | Rollback | Abort
|
|
|
|
## Pattern: multi-option-escalation
|
|
4-option escalation for review escalation (max retries exceeded).
|
|
- question: "Phase {N} has failed verification {attempt} times. How should we proceed?"
|
|
- header: "Escalate"
|
|
- options: Accept gaps | Re-plan (via /gsd:plan-phase) | Debug (via /gsd:debug) | Retry
|
|
|
|
## Pattern: multi-option-gaps
|
|
4-option gap handler for review gaps-found.
|
|
- question: "{count} verification gaps need attention. How should we proceed?"
|
|
- header: "Gaps"
|
|
- options: Auto-fix | Override | Manual | Skip
|
|
|
|
## Pattern: multi-option-priority
|
|
4-option priority selection for milestone gap priority.
|
|
- question: "Which gaps should we address?"
|
|
- header: "Priority"
|
|
- options: Must-fix only | Must + should | Everything | Let me pick
|
|
|
|
## Pattern: toggle-confirm
|
|
2-option confirmation for enabling/disabling boolean features.
|
|
- question: "Enable {feature_name}?"
|
|
- header: "Toggle"
|
|
- options: Enable | Disable
|
|
|
|
## Pattern: action-routing
|
|
Up to 4 suggested next actions with selection (status, resume workflows).
|
|
- question: "What would you like to do next?"
|
|
- header: "Next Step"
|
|
- options: {primary action} | {alternative 1} | {alternative 2} | Something else
|
|
- Note: Dynamically generate options from workflow state. Always include "Something else" as last option.
|
|
|
|
## Pattern: scope-confirm
|
|
3-option confirmation for quick task scope validation.
|
|
- question: "This task looks complex. Proceed as quick task or use full planning?"
|
|
- header: "Scope"
|
|
- options: Quick task | Full plan (via /gsd:plan-phase) | Revise
|
|
|
|
## Pattern: depth-select
|
|
3-option depth selection for planning workflow preferences.
|
|
- question: "How thorough should planning be?"
|
|
- header: "Depth"
|
|
- options: Quick (3-5 phases, skip research) | Standard (5-8 phases, default) | Comprehensive (8-12 phases, deep research)
|
|
|
|
## Pattern: context-handling
|
|
3-option handler for existing CONTEXT.md in discuss workflow.
|
|
- question: "Phase {N} already has a CONTEXT.md. How should we handle it?"
|
|
- header: "Context"
|
|
- options: Update it | View it | Skip
|
|
|
|
## Pattern: gray-area-option
|
|
Dynamic template for presenting gray area choices in discuss workflow.
|
|
- question: "{Gray area title}"
|
|
- header: "Decision"
|
|
- options: {Option 1} | {Option 2}
|
|
- Note: Options generated at runtime. Present real choices only — do NOT include a
|
|
"skip" or "you decide" option (the user ran discuss-phase to decide). An "Other"
|
|
free-text escape hatch may be offered per modes/default.md, but never a
|
|
"Let Claude decide" cop-out.
|