![[Feature Area Name]](http://pic.xiahunao.cn/yaotu/[Feature Area Name])
[Feature Area Name]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-doneRequirements[Non-negotiable design decisions from MANIFEST.md Requirements section that apply to this feature area. These MUST be honored in the real build. E.g., Must use streaming JSON output, Must support reconnection.]How to Build It[Step-by-step: what to install, how to configure, what code pattern to use. Include key code snippets extracted from the spike source. This is the proven approach — not theory, but tested and working code.]What to Avoid[Things that look right but arent. Gotchas. Anti-patterns discovered during spiking. Dead ends that were tried and failed.]Constraints[Hard facts: rate limits, library limitations, version requirements, incompatibilities]OriginSynthesized from spikes: NNN, NNN, NNN Source files available in: sources/NNN-spike-name/, sources/NNN-spike-name/五个章节各有明确职责 | 章节 | 回答的问题 | 素材来源 | |------|-----------|----------| | Requirements | 必须无条件遵守的硬性设计决策是什么 | MANIFEST.md 的 Requirements 段按功能域裁剪 | | How to Build It | 怎么一步步搭起来 | spike 源码中提取的可运行代码片段 | | What to Avoid | 哪些坑看起来对其实不对 | 实验中的反模式与失败路线 | | Constraints | 有哪些硬性限制 | 速率限制、库的限制、版本要求、不兼容项 | | Origin | 这份结论从哪来、证据在哪 | 对应 spike 编号与 sources/ 目录 | ### 3.8 编写 SKILL.mdwrite_skill 创建或更新生成技能的 SKILL.md它是技能的门面与索引。完整模板 markdown --- name: spike-findings-[project-dir-name] description: Implementation blueprint from spike experiments. Requirements, proven patterns, and verified knowledge for building [project-dir-name]. Auto-loaded during implementation work. --- context ## Project: [project-dir-name] [One paragraph from MANIFEST.md describing the overall idea] Spike sessions wrapped: [date(s)] /context requirements ## Requirements [Copied directly from MANIFEST.md Requirements section. These are non-negotiable design decisions that emerged from the users choices during spiking. Every feature area reference must honor these.] - [requirement 1] - [requirement 2] /requirements findings_index ## Feature Areas | Area | Reference | Key Finding | |------|-----------|-------------| | [Name] | references/[name].md | [One-line summary] | ## Source Files Original spike source files are preserved in sources/ for complete reference. /findings_index metadata ## Processed Spikes [List of spike numbers wrapped up] - 001-spike-name - 002-spike-name /metadata注意几个关键设计frontmatter 的description明确写着 Auto-loaded during implementation work是技能被自动加载的触发声明requirements直接照抄 MANIFEST.md 的 Requirements 段——非协商性设计决策被原样固化所有功能域参考文件都必须遵守findings_index是功能域→参考文件的导航表一行一个功能域及其关键结论metadata的processed_spikes列表就是下一轮 wrap-up 去重过滤的依据见 3.2 步形成增量处理闭环。3.9 编写规划摘要write_summary向.planning/spikes/WRAP-UP-SUMMARY.md写入项目历史摘要# Spike Wrap-Up Summary **Date:** [date] **Spikes processed:** [count] **Feature areas:** [list] **Skill output:** ./.claude/skills/spike-findings-[project]/ ## Processed Spikes | # | Name | Type | Verdict | Feature Area | |---|------|------|---------|--------------| ## Key Findings [consolidated findings summary]这份摘要留在.planning/spikes/中供项目历史追踪与后续检索使用是技能面向 Agent 自动加载、摘要面向人类快速回顾的双轨设计。3.10 更新项目 CLAUDE.mdupdate_claude_md在项目根目录的CLAUDE.md不存在则创建中加入一条自动加载路由行- **Spike findings for [project]** (implementation patterns, constraints, gotchas) → Skill(spike-findings-[project-dir-name])若该行已存在追加模式保持不变。正是这一行让技能在未来构建会话中按需自动加载——Agent 读取 CLAUDE.md 时就能发现并调用spike-findings-*技能。注意对 spike 技能的非致命探测还受到专门的回归测试保护tests/bug-3072-optional-sketch-findings-guard.test.cjs它断言ui-phase.md、plan-phase.md、discuss-phase.md、new-project.md等流程中对spike-findings-*/SKILL.md的 bash 探测都必须带|| true非致命守卫避免因技能目录不存在而中断流程。3.11 生成或更新 CONVENTIONS.mdgenerate_conventions分析所有已处理的 spike找出跨实验反复出现的模式写入.planning/spikes/CONVENTIONS.md。这份文件的定位是告诉未来的 spike 会话我们是怎么做 spike 的——沉淀的是栈、结构与模式的既有约定。通读所有 spike 源码与 README寻找栈选择Stack choices——哪种语言/框架/运行时在多个 spike 中反复出现结构模式Structure patterns——常见的文件布局、端口号、命名规范反复出现的方法Recurring approaches——认证怎么做、样式怎么处理、数据怎么服务工具与库Tools libraries——反复出现且版本可用的包。写入或更新.planning/spikes/CONVENTIONS.md# Spike Conventions Patterns and stack choices established across spike sessions. New spikes follow these unless the question requires otherwise. ## Stack [What we use for frontend, backend, scripts, and why — derived from what repeated across spikes] ## Structure [Common file layouts, port assignments, naming patterns] ## Patterns [Recurring approaches: how we handle auth, how we style, how we serve, etc.] ## Tools Libraries [Preferred packages with versions that worked, and any to avoid]纳入门槛只收录出现在 2 个以上 spike中、或由用户明确选择的模式——单一实验的偶发选择不足以成为约定追加模式更新若CONVENTIONS.md已存在用新模式更新各章节并删除被更新的 spike 证伪的旧条目。有趣的是CONVENTIONS.md 不是 wrap-up 的专利——spike 主工作流 在每次 spike 会话结束时也会执行Update Conventions步骤两条工作流共享同一份文件、互相衔接spike 负责实时增量更新wrap-up 负责全量重审收敛。3.12 提交产物commit当COMMIT_DOCS为true时按规范提交所有产物gsd-sdk query commit docs(spike-wrap-up): package [N] spike findings into project skill --files .planning/spikes/WRAP-UP-SUMMARY.md .planning/spikes/CONVENTIONS.md提交消息遵循docs(spike-wrap-up): ...类型化规范与 spike 会话的docs(spike-NNN): [VERDICT]提交风格见 get-shit-done/workflows/spike.md#L335-L338一致。若commit_docs为false或.planning/被 gitignore则跳过提交规划产物仅保留在本地。3.13 报告与下一步report / whats_next流程收尾输出完成报告━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GSD ► SPIKE WRAP-UP COMPLETE ✓ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **Processed:** {N} spikes **Feature areas:** {list} **Skill:** ./.claude/skills/spike-findings-[project]/ **Conventions:** .planning/spikes/CONVENTIONS.md **Summary:** .planning/spikes/WRAP-UP-SUMMARY.md **CLAUDE.md:** routing line added The spike-findings skill will auto-load in future build conversations.随后给出下一步选项引导用户继续探索## ▶ Next Up **Explore frontier spikes** — see what else is worth spiking based on what weve learned /gsd:spike (run with no argument — its frontier mode analyzes the spike landscape and proposes integration and frontier spikes) **Also available:** - /gsd:plan-phase — start planning the real implementation - /gsd:spike [idea] — spike a specific new idea - /gsd:explore — continue exploring - Other【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-done创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
[Feature Area Name]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-doneRequirements[Non-negotiable design decisions from MANIFEST.md Requirements section that apply to this feature area. These MUST be honored in the real build. E.g., Must use streaming JSON output, Must support reconnection.]How to Build It[Step-by-step: what to install, how to configure, what code pattern to use. Include key code snippets extracted from the spike source. This is the proven approach — not theory, but tested and working code.]What to Avoid[Things that look right but arent. Gotchas. Anti-patterns discovered during spiking. Dead ends that were tried and failed.]Constraints[Hard facts: rate limits, library limitations, version requirements, incompatibilities]OriginSynthesized from spikes: NNN, NNN, NNN Source files available in: sources/NNN-spike-name/, sources/NNN-spike-name/五个章节各有明确职责 | 章节 | 回答的问题 | 素材来源 | |------|-----------|----------| | Requirements | 必须无条件遵守的硬性设计决策是什么 | MANIFEST.md 的 Requirements 段按功能域裁剪 | | How to Build It | 怎么一步步搭起来 | spike 源码中提取的可运行代码片段 | | What to Avoid | 哪些坑看起来对其实不对 | 实验中的反模式与失败路线 | | Constraints | 有哪些硬性限制 | 速率限制、库的限制、版本要求、不兼容项 | | Origin | 这份结论从哪来、证据在哪 | 对应 spike 编号与 sources/ 目录 | ### 3.8 编写 SKILL.mdwrite_skill 创建或更新生成技能的 SKILL.md它是技能的门面与索引。完整模板 markdown --- name: spike-findings-[project-dir-name] description: Implementation blueprint from spike experiments. Requirements, proven patterns, and verified knowledge for building [project-dir-name]. Auto-loaded during implementation work. --- context ## Project: [project-dir-name] [One paragraph from MANIFEST.md describing the overall idea] Spike sessions wrapped: [date(s)] /context requirements ## Requirements [Copied directly from MANIFEST.md Requirements section. These are non-negotiable design decisions that emerged from the users choices during spiking. Every feature area reference must honor these.] - [requirement 1] - [requirement 2] /requirements findings_index ## Feature Areas | Area | Reference | Key Finding | |------|-----------|-------------| | [Name] | references/[name].md | [One-line summary] | ## Source Files Original spike source files are preserved in sources/ for complete reference. /findings_index metadata ## Processed Spikes [List of spike numbers wrapped up] - 001-spike-name - 002-spike-name /metadata注意几个关键设计frontmatter 的description明确写着 Auto-loaded during implementation work是技能被自动加载的触发声明requirements直接照抄 MANIFEST.md 的 Requirements 段——非协商性设计决策被原样固化所有功能域参考文件都必须遵守findings_index是功能域→参考文件的导航表一行一个功能域及其关键结论metadata的processed_spikes列表就是下一轮 wrap-up 去重过滤的依据见 3.2 步形成增量处理闭环。3.9 编写规划摘要write_summary向.planning/spikes/WRAP-UP-SUMMARY.md写入项目历史摘要# Spike Wrap-Up Summary **Date:** [date] **Spikes processed:** [count] **Feature areas:** [list] **Skill output:** ./.claude/skills/spike-findings-[project]/ ## Processed Spikes | # | Name | Type | Verdict | Feature Area | |---|------|------|---------|--------------| ## Key Findings [consolidated findings summary]这份摘要留在.planning/spikes/中供项目历史追踪与后续检索使用是技能面向 Agent 自动加载、摘要面向人类快速回顾的双轨设计。3.10 更新项目 CLAUDE.mdupdate_claude_md在项目根目录的CLAUDE.md不存在则创建中加入一条自动加载路由行- **Spike findings for [project]** (implementation patterns, constraints, gotchas) → Skill(spike-findings-[project-dir-name])若该行已存在追加模式保持不变。正是这一行让技能在未来构建会话中按需自动加载——Agent 读取 CLAUDE.md 时就能发现并调用spike-findings-*技能。注意对 spike 技能的非致命探测还受到专门的回归测试保护tests/bug-3072-optional-sketch-findings-guard.test.cjs它断言ui-phase.md、plan-phase.md、discuss-phase.md、new-project.md等流程中对spike-findings-*/SKILL.md的 bash 探测都必须带|| true非致命守卫避免因技能目录不存在而中断流程。3.11 生成或更新 CONVENTIONS.mdgenerate_conventions分析所有已处理的 spike找出跨实验反复出现的模式写入.planning/spikes/CONVENTIONS.md。这份文件的定位是告诉未来的 spike 会话我们是怎么做 spike 的——沉淀的是栈、结构与模式的既有约定。通读所有 spike 源码与 README寻找栈选择Stack choices——哪种语言/框架/运行时在多个 spike 中反复出现结构模式Structure patterns——常见的文件布局、端口号、命名规范反复出现的方法Recurring approaches——认证怎么做、样式怎么处理、数据怎么服务工具与库Tools libraries——反复出现且版本可用的包。写入或更新.planning/spikes/CONVENTIONS.md# Spike Conventions Patterns and stack choices established across spike sessions. New spikes follow these unless the question requires otherwise. ## Stack [What we use for frontend, backend, scripts, and why — derived from what repeated across spikes] ## Structure [Common file layouts, port assignments, naming patterns] ## Patterns [Recurring approaches: how we handle auth, how we style, how we serve, etc.] ## Tools Libraries [Preferred packages with versions that worked, and any to avoid]纳入门槛只收录出现在 2 个以上 spike中、或由用户明确选择的模式——单一实验的偶发选择不足以成为约定追加模式更新若CONVENTIONS.md已存在用新模式更新各章节并删除被更新的 spike 证伪的旧条目。有趣的是CONVENTIONS.md 不是 wrap-up 的专利——spike 主工作流 在每次 spike 会话结束时也会执行Update Conventions步骤两条工作流共享同一份文件、互相衔接spike 负责实时增量更新wrap-up 负责全量重审收敛。3.12 提交产物commit当COMMIT_DOCS为true时按规范提交所有产物gsd-sdk query commit docs(spike-wrap-up): package [N] spike findings into project skill --files .planning/spikes/WRAP-UP-SUMMARY.md .planning/spikes/CONVENTIONS.md提交消息遵循docs(spike-wrap-up): ...类型化规范与 spike 会话的docs(spike-NNN): [VERDICT]提交风格见 get-shit-done/workflows/spike.md#L335-L338一致。若commit_docs为false或.planning/被 gitignore则跳过提交规划产物仅保留在本地。3.13 报告与下一步report / whats_next流程收尾输出完成报告━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GSD ► SPIKE WRAP-UP COMPLETE ✓ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ **Processed:** {N} spikes **Feature areas:** {list} **Skill:** ./.claude/skills/spike-findings-[project]/ **Conventions:** .planning/spikes/CONVENTIONS.md **Summary:** .planning/spikes/WRAP-UP-SUMMARY.md **CLAUDE.md:** routing line added The spike-findings skill will auto-load in future build conversations.随后给出下一步选项引导用户继续探索## ▶ Next Up **Explore frontier spikes** — see what else is worth spiking based on what weve learned /gsd:spike (run with no argument — its frontier mode analyzes the spike landscape and proposes integration and frontier spikes) **Also available:** - /gsd:plan-phase — start planning the real implementation - /gsd:spike [idea] — spike a specific new idea - /gsd:explore — continue exploring - Other【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-done创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
