尧图网页设计 
Implementation Tasks【免费下载链接】gstackUse Garry Tans exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA项目地址: https://gitcode.com/GitHub_Trending/gs/gstackT1 (P1, human: ~2h / CC: ~15min)— —Surfaced by:—Files:Verify:优先级约定P1 阻塞 shipP2 应落在同一分支P3 是跟进 TODO。若某发现没有可行动任务就不硬造零发现的小节输出 _No new tasks from section._。 JSONL 制品用 jq -nc 逐任务写入绝不手写 echo/printf 拼 JSON bash eval $(~/.claude/skills/gstack/bin/gstack-slug 2/dev/null) TASKS_DIR${HOME}/.gstack/projects/${SLUG:-unknown} mkdir -p $TASKS_DIR TASKS_FILE$TASKS_DIR/tasks-design-review-$(date %Y%m%d-%H%M%S).jsonl # 每个任务一次 jq -nc 调用 # --arg phase design-review --arg id $TASK_ID --arg priority $PRIORITY ... # --argjson files [path/a.ts,path/b.ts] # 字段phase, run_id, branch, commit, id, priority, component, files, # effort_human, effort_cc, title, source_finding零任务时仍要touch该文件——空文件语义是跑了无发现区别于没跑。十二、完成摘要、评审日志与看板Completion Summary是固定表格System Audit、Step 0 初始评分、Pass 1–7 各自的修前 → 修后分数、NOT in scope / What already exists / TODOS 提案数、Approved Mockups生成数/批准数、加入计划的决策数、总体分___/10 → ___/10。若全部 pass ≥8Plan is design-complete. Run /design-review after implementation for visual QA.评审落盘PLAN MODE EXCEPTION — ALWAYS RUN~/.claude/skills/gstack/bin/gstack-review-log {skill:plan-design-review,timestamp:TIMESTAMP,status:STATUS,initial_score:N,overall_score:N,unresolved:N,decisions_made:N,commit:COMMIT}status取clean总分 ≥8 且 0 未解决否则issues_open。此命令写入~/.gstack//ship的评审就绪看板依赖它跳过会破坏看板。Review Readiness Dashboard运行gstack-review-read后解析输出7 天窗口内取每个技能最近一条Design Review 行取plan-design-review完整视觉审计与design-review-lite代码级检查中较新者状态后缀 (FULL)/(LITE)。评审分层Eng Review 是唯一默认强制的 ship 门可全局gstack-config set skip_eng_review true关闭CEO / Design / Outside Voice 为可选从不阻塞 shipAdversarial Review 对所有 diff 常驻。过期检测对 plan 级行含 plan-design-review不适用 worktree 规则——计划级评的是计划文件而非仓库树维持 7 天新鲜度逻辑若有plan_sha256字段可对比当前计划文件哈希并在不匹配时标注plan changed since review。十三、计划文件评审报告与 EXIT PLAN MODE 门审查完成后还要把## GSTACK REVIEW REPORT写进计划文件末尾让任何读计划的人都能看到评审状态。报告表格按技能固定形态## GSTACK REVIEW REPORT | Review | Trigger | Why | Runs | Status | Findings | |--------|---------|-----|------|--------|----------| | Design Review | /plan-design-review | UI/UX gaps | {runs} | {status} | score: {initial}/10 → {overall}/10, {decisions} decisions |【免费下载链接】gstackUse Garry Tans exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA项目地址: https://gitcode.com/GitHub_Trending/gs/gstack创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考 Implementation Tasks
Implementation Tasks【免费下载链接】gstackUse Garry Tans exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA项目地址: https://gitcode.com/GitHub_Trending/gs/gstackT1 (P1, human: ~2h / CC: ~15min)— —Surfaced by:—Files:Verify:优先级约定P1 阻塞 shipP2 应落在同一分支P3 是跟进 TODO。若某发现没有可行动任务就不硬造零发现的小节输出 _No new tasks from section._。 JSONL 制品用 jq -nc 逐任务写入绝不手写 echo/printf 拼 JSON bash eval $(~/.claude/skills/gstack/bin/gstack-slug 2/dev/null) TASKS_DIR${HOME}/.gstack/projects/${SLUG:-unknown} mkdir -p $TASKS_DIR TASKS_FILE$TASKS_DIR/tasks-design-review-$(date %Y%m%d-%H%M%S).jsonl # 每个任务一次 jq -nc 调用 # --arg phase design-review --arg id $TASK_ID --arg priority $PRIORITY ... # --argjson files [path/a.ts,path/b.ts] # 字段phase, run_id, branch, commit, id, priority, component, files, # effort_human, effort_cc, title, source_finding零任务时仍要touch该文件——空文件语义是跑了无发现区别于没跑。十二、完成摘要、评审日志与看板Completion Summary是固定表格System Audit、Step 0 初始评分、Pass 1–7 各自的修前 → 修后分数、NOT in scope / What already exists / TODOS 提案数、Approved Mockups生成数/批准数、加入计划的决策数、总体分___/10 → ___/10。若全部 pass ≥8Plan is design-complete. Run /design-review after implementation for visual QA.评审落盘PLAN MODE EXCEPTION — ALWAYS RUN~/.claude/skills/gstack/bin/gstack-review-log {skill:plan-design-review,timestamp:TIMESTAMP,status:STATUS,initial_score:N,overall_score:N,unresolved:N,decisions_made:N,commit:COMMIT}status取clean总分 ≥8 且 0 未解决否则issues_open。此命令写入~/.gstack//ship的评审就绪看板依赖它跳过会破坏看板。Review Readiness Dashboard运行gstack-review-read后解析输出7 天窗口内取每个技能最近一条Design Review 行取plan-design-review完整视觉审计与design-review-lite代码级检查中较新者状态后缀 (FULL)/(LITE)。评审分层Eng Review 是唯一默认强制的 ship 门可全局gstack-config set skip_eng_review true关闭CEO / Design / Outside Voice 为可选从不阻塞 shipAdversarial Review 对所有 diff 常驻。过期检测对 plan 级行含 plan-design-review不适用 worktree 规则——计划级评的是计划文件而非仓库树维持 7 天新鲜度逻辑若有plan_sha256字段可对比当前计划文件哈希并在不匹配时标注plan changed since review。十三、计划文件评审报告与 EXIT PLAN MODE 门审查完成后还要把## GSTACK REVIEW REPORT写进计划文件末尾让任何读计划的人都能看到评审状态。报告表格按技能固定形态## GSTACK REVIEW REPORT | Review | Trigger | Why | Runs | Status | Findings | |--------|---------|-----|------|--------|----------| | Design Review | /plan-design-review | UI/UX gaps | {runs} | {status} | score: {initial}/10 → {overall}/10, {decisions} decisions |【免费下载链接】gstackUse Garry Tans exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA项目地址: https://gitcode.com/GitHub_Trending/gs/gstack创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考