d4767ac2e0
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
4.3 KiB
4.3 KiB
UI 品牌规范
面向用户的 GSD 输出的视觉模式。编排器通过 @ 引用此文件。
阶段横幅
用于主要工作流过渡。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GSD ► {阶段名称}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
阶段名称（大写）：
QUESTIONING（提问）RESEARCHING（研究）DEFINING REQUIREMENTS（定义需求）CREATING ROADMAP（创建路线图）PLANNING PHASE {N}（规划阶段 {N}）EXECUTING WAVE {N}（执行波次 {N}）VERIFYING（验证）PHASE {N} COMPLETE ✓（阶段 {N} 完成）MILESTONE COMPLETE 🎉（里程碑完成）
检查点框
需要用户操作。62 字符宽度。
╔══════════════════════════════════════════════════════════════╗
║ CHECKPOINT: {类型} ║
╚══════════════════════════════════════════════════════════════╝
{内容}
──────────────────────────────────────────────────────────────
→ {操作提示}
──────────────────────────────────────────────────────────────
类型：
CHECKPOINT: 需要验证→→ 输入 "approved" 或描述问题CHECKPOINT: 需要决策→→ 选择: option-a / option-bCHECKPOINT: 需要操作→→ 完成后输入 "done"
状态符号
✓ 完成 / 通过 / 已验证
✗ 失败 / 缺失 / 阻塞
◆ 进行中
○ 待处理
⚡ 自动批准
⚠ 警告
🎉 里程碑完成（仅在横幅中）
进度显示
阶段/里程碑级别：
进度: ████████░░ 80%
任务级别：
任务: 2/4 完成
计划级别：
计划: 3/5 完成
生成指示器
◆ 正在生成研究员...
◆ 并行生成 4 个研究员...
→ 技术栈研究
→ 功能研究
→ 架构研究
→ 陷阱研究
✓ 研究员完成: STACK.md 已写入
下一步区块
始终在主要完成后。
───────────────────────────────────────────────────────────────
## ▶ 下一步
**{标识符}: {名称}** — {单行描述}
`{可复制粘贴的命令}`
<sub>`/clear` 优先 → 全新上下文窗口</sub>
───────────────────────────────────────────────────────────────
**也可选：**
- `/gsd-alternative-1` — 描述
- `/gsd-alternative-2` — 描述
───────────────────────────────────────────────────────────────
错误框
╔══════════════════════════════════════════════════════════════╗
║ ERROR ║
╚══════════════════════════════════════════════════════════════╝
{错误描述}
**修复方法:** {解决步骤}
表格
| 阶段 | 状态 | 计划 | 进度 |
|------|------|------|------|
| 1 | ✓ | 3/3 | 100% |
| 2 | ◆ | 1/4 | 25% |
| 3 | ○ | 0/2 | 0% |
反模式
- 变化的框/横幅宽度
- 混合横幅样式（
===、---、***） - 横幅中缺少
GSD ►前缀 - 随机 emoji（
🚀、✨、💫） - 完成后缺少下一步区块