[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"similar-rokicool--gsd-opencode":3,"tool-rokicool--gsd-opencode":61},[4,18,26,36,44,53],{"id":5,"name":6,"github_repo":7,"description_zh":8,"stars":9,"difficulty_score":10,"last_commit_at":11,"category_tags":12,"status":17},4358,"openclaw","openclaw\u002Fopenclaw","OpenClaw 是一款专为个人打造的本地化 AI 助手，旨在让你在自己的设备上拥有完全可控的智能伙伴。它打破了传统 AI 助手局限于特定网页或应用的束缚，能够直接接入你日常使用的各类通讯渠道，包括微信、WhatsApp、Telegram、Discord、iMessage 等数十种平台。无论你在哪个聊天软件中发送消息，OpenClaw 都能即时响应，甚至支持在 macOS、iOS 和 Android 设备上进行语音交互，并提供实时的画布渲染功能供你操控。\n\n这款工具主要解决了用户对数据隐私、响应速度以及“始终在线”体验的需求。通过将 AI 部署在本地，用户无需依赖云端服务即可享受快速、私密的智能辅助，真正实现了“你的数据，你做主”。其独特的技术亮点在于强大的网关架构，将控制平面与核心助手分离，确保跨平台通信的流畅性与扩展性。\n\nOpenClaw 非常适合希望构建个性化工作流的技术爱好者、开发者，以及注重隐私保护且不愿被单一生态绑定的普通用户。只要具备基础的终端操作能力（支持 macOS、Linux 及 Windows WSL2），即可通过简单的命令行引导完成部署。如果你渴望拥有一个懂你",349277,3,"2026-04-06T06:32:30",[13,14,15,16],"Agent","开发框架","图像","数据工具","ready",{"id":19,"name":20,"github_repo":21,"description_zh":22,"stars":23,"difficulty_score":10,"last_commit_at":24,"category_tags":25,"status":17},3808,"stable-diffusion-webui","AUTOMATIC1111\u002Fstable-diffusion-webui","stable-diffusion-webui 是一个基于 Gradio 构建的网页版操作界面，旨在让用户能够轻松地在本地运行和使用强大的 Stable Diffusion 图像生成模型。它解决了原始模型依赖命令行、操作门槛高且功能分散的痛点，将复杂的 AI 绘图流程整合进一个直观易用的图形化平台。\n\n无论是希望快速上手的普通创作者、需要精细控制画面细节的设计师，还是想要深入探索模型潜力的开发者与研究人员，都能从中获益。其核心亮点在于极高的功能丰富度：不仅支持文生图、图生图、局部重绘（Inpainting）和外绘（Outpainting）等基础模式，还独创了注意力机制调整、提示词矩阵、负向提示词以及“高清修复”等高级功能。此外，它内置了 GFPGAN 和 CodeFormer 等人脸修复工具，支持多种神经网络放大算法，并允许用户通过插件系统无限扩展能力。即使是显存有限的设备，stable-diffusion-webui 也提供了相应的优化选项，让高质量的 AI 艺术创作变得触手可及。",162132,"2026-04-05T11:01:52",[14,15,13],{"id":27,"name":28,"github_repo":29,"description_zh":30,"stars":31,"difficulty_score":32,"last_commit_at":33,"category_tags":34,"status":17},1381,"everything-claude-code","affaan-m\u002Feverything-claude-code","everything-claude-code 是一套专为 AI 编程助手（如 Claude Code、Codex、Cursor 等）打造的高性能优化系统。它不仅仅是一组配置文件，而是一个经过长期实战打磨的完整框架，旨在解决 AI 代理在实际开发中面临的效率低下、记忆丢失、安全隐患及缺乏持续学习能力等核心痛点。\n\n通过引入技能模块化、直觉增强、记忆持久化机制以及内置的安全扫描功能，everything-claude-code 能显著提升 AI 在复杂任务中的表现，帮助开发者构建更稳定、更智能的生产级 AI 代理。其独特的“研究优先”开发理念和针对 Token 消耗的优化策略，使得模型响应更快、成本更低，同时有效防御潜在的攻击向量。\n\n这套工具特别适合软件开发者、AI 研究人员以及希望深度定制 AI 工作流的技术团队使用。无论您是在构建大型代码库，还是需要 AI 协助进行安全审计与自动化测试，everything-claude-code 都能提供强大的底层支持。作为一个曾荣获 Anthropic 黑客大奖的开源项目，它融合了多语言支持与丰富的实战钩子（hooks），让 AI 真正成长为懂上",153609,2,"2026-04-13T11:34:59",[14,13,35],"语言模型",{"id":37,"name":38,"github_repo":39,"description_zh":40,"stars":41,"difficulty_score":32,"last_commit_at":42,"category_tags":43,"status":17},2271,"ComfyUI","Comfy-Org\u002FComfyUI","ComfyUI 是一款功能强大且高度模块化的视觉 AI 引擎，专为设计和执行复杂的 Stable Diffusion 图像生成流程而打造。它摒弃了传统的代码编写模式，采用直观的节点式流程图界面，让用户通过连接不同的功能模块即可构建个性化的生成管线。\n\n这一设计巧妙解决了高级 AI 绘图工作流配置复杂、灵活性不足的痛点。用户无需具备编程背景，也能自由组合模型、调整参数并实时预览效果，轻松实现从基础文生图到多步骤高清修复等各类复杂任务。ComfyUI 拥有极佳的兼容性，不仅支持 Windows、macOS 和 Linux 全平台，还广泛适配 NVIDIA、AMD、Intel 及苹果 Silicon 等多种硬件架构，并率先支持 SDXL、Flux、SD3 等前沿模型。\n\n无论是希望深入探索算法潜力的研究人员和开发者，还是追求极致创作自由度的设计师与资深 AI 绘画爱好者，ComfyUI 都能提供强大的支持。其独特的模块化架构允许社区不断扩展新功能，使其成为当前最灵活、生态最丰富的开源扩散模型工具之一，帮助用户将创意高效转化为现实。",108322,"2026-04-10T11:39:34",[14,15,13],{"id":45,"name":46,"github_repo":47,"description_zh":48,"stars":49,"difficulty_score":32,"last_commit_at":50,"category_tags":51,"status":17},6121,"gemini-cli","google-gemini\u002Fgemini-cli","gemini-cli 是一款由谷歌推出的开源 AI 命令行工具，它将强大的 Gemini 大模型能力直接集成到用户的终端环境中。对于习惯在命令行工作的开发者而言，它提供了一条从输入提示词到获取模型响应的最短路径，无需切换窗口即可享受智能辅助。\n\n这款工具主要解决了开发过程中频繁上下文切换的痛点，让用户能在熟悉的终端界面内直接完成代码理解、生成、调试以及自动化运维任务。无论是查询大型代码库、根据草图生成应用，还是执行复杂的 Git 操作，gemini-cli 都能通过自然语言指令高效处理。\n\n它特别适合广大软件工程师、DevOps 人员及技术研究人员使用。其核心亮点包括支持高达 100 万 token 的超长上下文窗口，具备出色的逻辑推理能力；内置 Google 搜索、文件操作及 Shell 命令执行等实用工具；更独特的是，它支持 MCP（模型上下文协议），允许用户灵活扩展自定义集成，连接如图像生成等外部能力。此外，个人谷歌账号即可享受免费的额度支持，且项目基于 Apache 2.0 协议完全开源，是提升终端工作效率的理想助手。",100752,"2026-04-10T01:20:03",[52,13,15,14],"插件",{"id":54,"name":55,"github_repo":56,"description_zh":57,"stars":58,"difficulty_score":32,"last_commit_at":59,"category_tags":60,"status":17},4721,"markitdown","microsoft\u002Fmarkitdown","MarkItDown 是一款由微软 AutoGen 团队打造的轻量级 Python 工具，专为将各类文件高效转换为 Markdown 格式而设计。它支持 PDF、Word、Excel、PPT、图片（含 OCR）、音频（含语音转录）、HTML 乃至 YouTube 链接等多种格式的解析，能够精准提取文档中的标题、列表、表格和链接等关键结构信息。\n\n在人工智能应用日益普及的今天，大语言模型（LLM）虽擅长处理文本，却难以直接读取复杂的二进制办公文档。MarkItDown 恰好解决了这一痛点，它将非结构化或半结构化的文件转化为模型“原生理解”且 Token 效率极高的 Markdown 格式，成为连接本地文件与 AI 分析 pipeline 的理想桥梁。此外，它还提供了 MCP（模型上下文协议）服务器，可无缝集成到 Claude Desktop 等 LLM 应用中。\n\n这款工具特别适合开发者、数据科学家及 AI 研究人员使用，尤其是那些需要构建文档检索增强生成（RAG）系统、进行批量文本分析或希望让 AI 助手直接“阅读”本地文件的用户。虽然生成的内容也具备一定可读性，但其核心优势在于为机器",93400,"2026-04-06T19:52:38",[52,14],{"id":62,"github_repo":63,"name":64,"description_en":65,"description_zh":66,"ai_summary_zh":67,"readme_en":68,"readme_zh":69,"quickstart_zh":70,"use_case_zh":71,"hero_image_url":72,"owner_login":73,"owner_name":74,"owner_avatar_url":75,"owner_bio":76,"owner_company":76,"owner_location":77,"owner_email":76,"owner_twitter":76,"owner_website":76,"owner_url":78,"languages":79,"stars":84,"forks":85,"last_commit_at":86,"license":76,"difficulty_score":32,"env_os":87,"env_gpu":88,"env_ram":88,"env_deps":89,"category_tags":94,"github_topics":76,"view_count":32,"oss_zip_url":76,"oss_zip_packed_at":76,"status":17,"created_at":95,"updated_at":96,"faqs":97,"releases":98},7225,"rokicool\u002Fgsd-opencode","gsd-opencode","Get-Shit-Done by TACHES for OpenCode","gsd-opencode 是一款专为 OpenCode 打造的轻量级开发辅助系统，源自著名的 TÂCHES GSD 项目。它的核心目标非常纯粹：帮助开发者通过清晰的规格描述，让 AI 高效、准确地完成代码构建任务，真正践行“把事做完”（Get Shit Done）的理念。\n\n许多现有的规范驱动开发工具往往引入了繁琐的企业级流程，如冲刺会议、故事点评估等，这对于独立开发者或小团队而言过于沉重且脱离实际。gsd-opencode 解决了这一痛点，它将复杂的上下文工程、XML 提示词格式化、子代理编排及状态管理隐藏在幕后，用户只需通过简单的命令即可启动工作流，无需扮演复杂的企业管理角色。\n\n这款工具特别适合希望利用 AI 提升效率的独立开发者、创意程序员以及小型技术团队。如果你不想被冗长的流程束缚，只想专注于产品创意并快速落地，gsd-opencode 是理想的选择。其技术亮点在于强大的元提示（meta-prompting）能力和动态子代理切换机制，能够根据任务需求自动调度不同的 AI 模型协作，并确保 AI 在编码过程中具备自我验证能力。无论是 macOS、Windows 还是 Linux","gsd-opencode 是一款专为 OpenCode 打造的轻量级开发辅助系统，源自著名的 TÂCHES GSD 项目。它的核心目标非常纯粹：帮助开发者通过清晰的规格描述，让 AI 高效、准确地完成代码构建任务，真正践行“把事做完”（Get Shit Done）的理念。\n\n许多现有的规范驱动开发工具往往引入了繁琐的企业级流程，如冲刺会议、故事点评估等，这对于独立开发者或小团队而言过于沉重且脱离实际。gsd-opencode 解决了这一痛点，它将复杂的上下文工程、XML 提示词格式化、子代理编排及状态管理隐藏在幕后，用户只需通过简单的命令即可启动工作流，无需扮演复杂的企业管理角色。\n\n这款工具特别适合希望利用 AI 提升效率的独立开发者、创意程序员以及小型技术团队。如果你不想被冗长的流程束缚，只想专注于产品创意并快速落地，gsd-opencode 是理想的选择。其技术亮点在于强大的元提示（meta-prompting）能力和动态子代理切换机制，能够根据任务需求自动调度不同的 AI 模型协作，并确保 AI 在编码过程中具备自我验证能力。无论是 macOS、Windows 还是 Linux 用户，均可通过一行命令轻松集成，让 AI 成为你值得信赖的编程搭档。","\u003Cdiv align=\"left\">\n\n# GET SHIT DONE for OpenCode. (Based on TÂCHES v1.33.0 - 2026-04-04)\n\n**A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES. (Adapted for OpenCode by rokicool and enthusiasts)**\n\n[TÂCHES Original GitHub Repository](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done)\n\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Fgsd-opencode?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fgsd-opencode)\n[![npm downloads](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002Fgsd-opencode?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fgsd-opencode)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue?style=for-the-badge)](LICENSE)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Frokicool\u002Fgsd-opencode?style=for-the-badge&logo=github&color=181717)](https:\u002F\u002Fgithub.com\u002Frokicool\u002Fgsd-opencode)\n\n---\n\n# (Un)Breaking news\n\nTACHES decided to include support for OpenCode in his own product. That is great news. \n\nHowever, with all due respect, his adaptation for OpenCode is not perfect. So I will continue working on this project and will try to fill the gaps.\n\nThanks to [@dpearson2699](https:\u002F\u002Fgithub.com\u002Fdpearson2699) we have much better adaptation of \u002Fgsd-settings command and (almost)dynamical switch between different LLMs for subagents.\n\n\n-- **Roman** (2026-01-31)\n\n\n[![IMAGE ALT TEXT HERE](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Frokicool_gsd-opencode_readme_7291cd6ca794.jpg)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=zRJ0UWHBjCY)\n\n---\n\n\u003Cbr>\n\n```bash\n$ npx gsd-opencode\n\nor\n\n$ npx gsd-opencode@latest\n\n```\n\n**Works on Mac, Windows, and Linux.**\n\n\u003Cbr>\n\n![GSD Install](assets\u002Fterminal.svg)\n\n\u003Cbr>\n\n*\"If you know clearly what you want, this WILL build it for you. No bs.\"*\n\n*\"I've done SpecKit, OpenSpec and Taskmaster — this has produced the best results for me.\"*\n\n*\"By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally just gets shit done.\"*\n\n\u003Cbr>\n\n**Trusted by engineers at Amazon, Google, Shopify, and Webflow.**\n\n[Why I Built This](#why-i-built-this) · [Distribution System](#distribution-system) · [How It Works](#how-it-works) · [Commands](#commands) · [Why It Works](#why-it-works)\n\n\u003C\u002Fdiv>\n\n---\n\n\n\n## Why I Built This \n\nI'm a solo developer. I don't write code — Claude Code does.\n\nOther spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.\n\nSo I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.\n\nThe system gives Claude Code everything it needs to do the work *and* verify it. I trust the workflow. It just does a good job.\n\nThat's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.\n\n— **TÂCHES**\n\n\n## From translator...\n\nI just love both GSD and OpenCode. I felt like having GSD available only for Claude Code is not fair. \n\n— **Roman**\n\n## Version 1.33.2\n\nAdded support for translating `Agent()` background task calls to OpenCode-compatible `@gsd-\u003Cagent>` shorthand syntax. The new translation rule 21 in `assets\u002Fconfigs\u002Fremove-task.json` dynamically extracts agent names from `skill=\"gsd-\u003Cagent>\"` patterns and converts them to the OpenCode format. This update fixes two `Agent()` calls in `autonomous.md` workflow for plan and execute phase dispatch, ensuring full OpenCode compatibility.\n\n## Version 1.33.0\n\nAgain we keep up with the original GSDv1 [v1.33.0](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done\u002Freleases\u002Ftag\u002Fv1.33.0) (2026-04-04).\n\nAnd locally there are lots of changes. And the most important one - I removed `task()` calls, since they are not supported by OpenCode and replaced them with the direct call to an agent.\n\n## Version 1.30.0\n\nWe are keeping up with original GSDv1 v1.30.0 (2026-03-30)\n\nThere is a controvertial solution I used to support \"skill(skill='command-name')\" syntax. Apart from that everything is expected to be fully functional.\n\n## Version 1.22.1\n\nI decided to add 'mode: subagent' property to all custom agents. It should not affect any GSD functionality. However, it should remove unnecessary agents out of the list, available by Tab.\n\nFeel free to complain if I missed anything.\n\n## Version 1.22.0 - We are catching up with original v1.22.4 (2026-03-03)\n\nAs usual, you can find all changes that TACHES made in the [original CHANGELOG.md v1.20.5 -> v1.22.4](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md)\n\nThe main theme for these changes - the original GSD uses the correct sysntax to execute agents. So, there will be no unexpected stops OR Gsd-Planner remains active after the planning is done.\n\nOn our the side of gsd-opencode there are several fixes and a lot of backend changes.\n\n## Version 1.20.3 - New gsd-opencode model profile system\n\n  I had to give up on supporting original GSD model profile system. Claude Code uses three different models: Opus, Sonnet, and Haiku. In OpenCode we are blessed with dozens of providers and hundreds of models. GSD model profile system is not suitable for us.\n  \n  So, I had to redesign it and call it 'simple|smart|genius' for now. I hope, it will solve unexpected stops.\n\n- `\u002Fgsd-settings` - *Does not make any changes to the model-agent assignment anymore*. It asks about the model profile - but does nothing. You have to execute `\u002Fgsd-set-profile` yourself.\n- `\u002Fgsd-check-profile` - Checks the gsd-opencode config files and informs about issues (if there are any).\n- `\u002Fgsd-set-profile` - You main interface to control what model to use on what stage. Try it! No, really, **Try it!**\n\n## Version 1.20.0 - We are catching up with original v1.20.5\n\nAs usual, you can find all changes that TACHES made in the [original CHANGELOG.md v1.9.4 -> v1.20.5](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md)\n\nAs for our side. We have a lot of small changes and one significant change to the Profile Management. Istead of replicating TACHES\u002FClaude Code approach we use OpenCode relevant.\n\nGSD-OpenCode supports three Profiles:\n\n - Simple (allows to define one model to work for all types of gsd custom agents)\n - Smart  (allows to define two different models to work with gsd custom agents: one for  )\n - Genius (ok, ok. Not exactly genius, but allows to define three different models to work with custom agents)\n\n## Version 1.9.0 - We are catching up with original v1.9.4\n\nYou can find all the changes that TACHES made in the [original CHANGELOG.md v1.6.4 -> v1.9.4](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md).\n\n### Model Profile Management\n\nOpenCode now supports full model profile management via:\n- `\u002Fgsd-settings` — Interactive settings menu for profiles, stage overrides, and workflow toggles\n- `\u002Fgsd-set-profile \u003Cprofile>` — Quick switch between quality\u002Fbalanced\u002Fbudget profiles\n- `\u002Fgsd-set-model \u003Cprofile>` — Configure which models each profile uses\n\nThese commands manage `.planning\u002Fconfig.json` and generate `opencode.json` with agent-to-model mappings. Note: Quit and relaunch OpenCode after changing profiles for changes to take effect.\n\n## Version 1.6.0 - We started using git submodules\n\nIf you clone this repo dont forget to execute the next command after cloning:\n\n```\n$ git submodule update --init --recursive \n```\n\nIt will update\u002Fpopulate .\u002Foriginal\u002Fget-shit-done folder from TÂCHES repo. \n\nHere is a nice compact article about git submodules: [Working with submodules](https:\u002F\u002Fgithub.blog\u002Fopen-source\u002Fgit\u002Fworking-with-submodules\u002F). \nThanks to @borisnaydis for pointing that out.\n\n## Version 1.5.0 - Breaking Change: Command Naming Convention Update\n\n**⚠️ Important: Breaking Change in Command Syntax**\n\nWe've made an update to align GSD's command naming convention with OpenCode's standard `kebab-case` format. Unfortunately, this introduces a breaking change to the visible command syntax that users have been accustomed to.\n\n### What Changed\n\n**Command Naming:** All GSD commands have been updated from the `\u002Fgsd:` prefix to the `\u002Fgsd-` format.\n\n### Why This Change?\n\nThe `gsd-kebab-case` naming convention follows OpenCode's standard command format. This alignment ensures consistency across the ecosystem and improves compatibility.\n**Note:** We understand this is an unfortunate breaking change to the visible command syntax. If\u002Fwhen it becomes possible in the future, we may consider restoring the original `\u002Fgsd:` syntax while maintaining backward compatibility.\n\n### Migration Guide\n\nFor users upgrading to version 1.5.0, simply replace the colon (`:`) in all GSD commands with a hyphen (`-`):\n\n- Old: `\u002Fgsd:plan-phase 1`\n- New: `\u002Fgsd-plan-phase 1`\n\nAll functionality remains the same—only the command prefix has changed.\n\n---\n\nVibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale.\n\nGSD fixes that. It's the context engineering layer that makes OpenCode reliable. Describe your idea, let the system extract everything it needs to know, and let OpenCode get to work.\n\n---\n\n## Who This Is For\n\nPeople who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.\n\n---\n\n## Getting Started\n\n```bash\nnpx gsd-opencode\n\n# OR\n\nnpm install gsd-opencode -g\ngsd-opencode install\n\n```\n\nThat's it. Verify with `\u002Fgsd-help`.\n\n### Staying Updated\n\nGSD evolves fast. Check for updates periodically:\n\n```\n\u002Fgsd-whats-new\n```\n\nUpdate with:\n\n```bash\nnpx gsd-opencode@latest\n\n# OR\n\nnpm install gsd-opencode@latest -g\ngsd-opencode install\n\n```\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Non-interactive Install (Docker, CI, Scripts)\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```bash\nnpx gsd-opencode --global   # Install to ~\u002F.config\u002Fopencode\u002F\nnpx gsd-opencode --local    # Install to .opencode\u002F\n```\n\nUse `--global` (`-g`) or `--local` (`-l`) to skip the interactive prompt.\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Uninstall GSD-OpenCode\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```bash\n# Uninstall (auto-detects global or local installation)\ngsd-opencode uninstall\n\n# Uninstall globally\ngsd-opencode uninstall --global\ngsd-opencode uninstall -g\n\n# Uninstall locally\ngsd-opencode uninstall --local\ngsd-opencode uninstall -l\n\n# Preview what would be removed (dry run)\ngsd-opencode uninstall --dry-run\n```\n\nSee [DISTRIBUTION-MANAGER.md](.\u002FDISTRIBUTION-MANAGER.md) for detailed uninstall options including backup control and safety features.\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Development Installation\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nClone the repository and run the installer locally:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Frokicool\u002Fgsd-opencode.git\ncd gsd-opencode\ngit submodule update --init --recursive \nnode bin\u002Finstall.js --local\n```\n\nInstalls to `.opencode\u002F` for testing modifications before contributing.\n\n\u003C\u002Fdetails>\n\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Alternative: Granular Permissions\u003C\u002Fstrong>\u003C\u002Fsummary>\n\nIf you prefer not to use that flag, add this to your project's `.opencode\u002Fsettings.json`:\n\n```json\n{\n  $schema: https:\u002F\u002Fopencode.ai\u002Fconfig.json,\n  permission: {\n    bash: allow,\n    read: allow,\n    edit: allow,\n    grep: allow,\n    glob: allow,\n    list: allow\n  }\n}\n```\n\n\u003C\u002Fdetails>\n\n---\n\n## Distribution Manager (gsd-opencode specific)\n\nGSD-OpenCode includes a comprehensive package manager for installing, maintaining, and updating the GSD system. Once installed via npm, you have access to a full CLI for managing your GSD installation.\n\n### Quick Reference\n\n| Command | Description |\n|---------|-------------|\n| `gsd-opencode install` | Install GSD (interactive) |\n| `gsd-opencode install --global` \u002F `-g` | Install globally (~\u002F.config\u002Fopencode\u002F) |\n| `gsd-opencode install --local` \u002F `-l` | Install locally (.\u002F.opencode\u002F) |\n| `gsd-opencode list` | Show installation status |\n| `gsd-opencode check` | Verify installation health |\n| `gsd-opencode repair` | Fix broken installation |\n| `gsd-opencode update` | Update to latest version |\n| `gsd-opencode uninstall` | Remove installation |\n\nFor detailed documentation on all commands, options, troubleshooting, and advanced usage, see [DISTRIBUTION-MANAGER.md](.\u002FDISTRIBUTION-MANAGER.md).\n\n---\n\n## How It Works\n\n> **Already have code?** Run `\u002Fgsd-map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `\u002Fgsd-new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.\n\n### 1. Initialize Project\n\n```\n\u002Fgsd-new-project\n```\n\nOne command, one flow. The system:\n\n1. **Questions** — Asks until it understands your idea completely (goals, constraints, tech preferences, edge cases)\n2. **Research** — Spawns parallel agents to investigate the domain (optional but recommended)\n3. **Requirements** — Extracts what's v1, v2, and out of scope\n4. **Roadmap** — Creates phases mapped to requirements\n\nYou approve the roadmap. Now you're ready to build.\n\n**Creates:** `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md`, `.planning\u002Fresearch\u002F`\n\n---\n\n### 2. Discuss Phase\n\n```\n\u002Fgsd-discuss-phase 1\n```\n\n**This is where you shape the implementation.**\n\nYour roadmap has a sentence or two per phase. That's not enough context to build something the way *you* imagine it. This step captures your preferences before anything gets researched or planned.\n\nThe system analyzes the phase and identifies gray areas based on what's being built:\n\n- **Visual features** → Layout, density, interactions, empty states\n- **APIs\u002FCLIs** → Response format, flags, error handling, verbosity\n- **Content systems** → Structure, tone, depth, flow\n- **Organization tasks** → Grouping criteria, naming, duplicates, exceptions\n\nFor each area you select, it asks until you're satisfied. The output — `CONTEXT.md` — feeds directly into the next two steps:\n\n1. **Researcher reads it** — Knows what patterns to investigate (\"user wants card layout\" → research card component libraries)\n2. **Planner reads it** — Knows what decisions are locked (\"infinite scroll decided\" → plan includes scroll handling)\n\nThe deeper you go here, the more the system builds what you actually want. Skip it and you get reasonable defaults. Use it and you get *your* vision.\n\n**Creates:** `{phase}-CONTEXT.md`\n\n---\n\n### 3. Plan Phase\n\n```\n\u002Fgsd-plan-phase 1\n```\n\nThe system:\n\n1. **Researches** — Investigates how to implement this phase, guided by your CONTEXT.md decisions\n2. **Plans** — Creates 2-3 atomic task plans with XML structure\n3. **Verifies** — Checks plans against requirements, loops until they pass\n\nEach plan is small enough to execute in a fresh context window. No degradation, no \"I'll be more concise now.\"\n\n**Creates:** `{phase}-RESEARCH.md`, `{phase}-{N}-PLAN.md`\n\n---\n\n### 4. Execute Phase\n\n```\n\u002Fgsd-execute-phase 1\n```\n\nThe system:\n\n1. **Runs plans in waves** — Parallel where possible, sequential when dependent\n2. **Fresh context per plan** — 200k tokens purely for implementation, zero accumulated garbage\n3. **Commits per task** — Every task gets its own atomic commit\n4. **Verifies against goals** — Checks the codebase delivers what the phase promised\n\nWalk away, come back to completed work with clean git history.\n\n**How Wave Execution Works:**\n\nPlans are grouped into \"waves\" based on dependencies. Within each wave, plans run in parallel. Waves run sequentially.\n\n```\n┌─────────────────────────────────────────────────────────────────────┐\n│  PHASE EXECUTION                                                    │\n├─────────────────────────────────────────────────────────────────────┤\n│                                                                     │\n│  WAVE 1 (parallel)          WAVE 2 (parallel)          WAVE 3       │\n│  ┌─────────┐ ┌─────────┐    ┌─────────┐ ┌─────────┐    ┌─────────┐  │\n│  │ Plan 01 │ │ Plan 02 │ →  │ Plan 03 │ │ Plan 04 │ →  │ Plan 05 │  │\n│  │         │ │         │    │         │ │         │    │         │  │\n│  │ User    │ │ Product │    │ Orders  │ │ Cart    │    │ Checkout│  │\n│  │ Model   │ │ Model   │    │ API     │ │ API     │    │ UI      │  │\n│  └─────────┘ └─────────┘    └─────────┘ └─────────┘    └─────────┘  │\n│       │           │              ↑           ↑              ↑       │\n│       └───────────┴──────────────┴───────────┘              │       │\n│              Dependencies: Plan 03 needs Plan 01            │       │\n│                          Plan 04 needs Plan 02              │       │\n│                          Plan 05 needs Plans 03 + 04        │       │\n│                                                                     │\n└─────────────────────────────────────────────────────────────────────┘\n```\n\n**Why waves matter:**\n- Independent plans → Same wave → Run in parallel\n- Dependent plans → Later wave → Wait for dependencies\n- File conflicts → Sequential plans or same plan\n\nThis is why \"vertical slices\" (Plan 01: User feature end-to-end) parallelize better than \"horizontal layers\" (Plan 01: All models, Plan 02: All APIs).\n\n**Creates:** `{phase_num}-{N}-SUMMARY.md`, `{phase_num}-VERIFICATION.md`\n\n---\n\n### 5. Verify Work\n\n```\n\u002Fgsd-verify-work 1\n```\n\n**This is where you confirm it actually works.**\n\nAutomated verification checks that code exists and tests pass. But does the feature *work* the way you expected? This is your chance to use it.\n\nThe system:\n\n1. **Extracts testable deliverables** — What you should be able to do now\n2. **Walks you through one at a time** — \"Can you log in with email?\" Yes\u002Fno, or describe what's wrong\n3. **Diagnoses failures automatically** — Spawns debug agents to find root causes\n4. **Creates verified fix plans** — Ready for immediate re-execution\n\nIf everything passes, you move on. If something's broken, you don't manually debug — you just run `\u002Fgsd-execute-phase` again with the fix plans it created.\n\n**Creates:** `{phase}-UAT.md`, fix plans if issues found\n\n---\n\n### 6. Repeat → Complete → Next Milestone\n\n```\n\u002Fgsd-discuss-phase 2\n\u002Fgsd-plan-phase 2\n\u002Fgsd-execute-phase 2\n\u002Fgsd-verify-work 2\n...\n\u002Fgsd-complete-milestone\n\u002Fgsd-new-milestone\n```\n\nLoop **discuss → plan → execute → verify** until milestone complete.\n\nEach phase gets your input (discuss), proper research (plan), clean execution (execute), and human verification (verify). Context stays fresh. Quality stays high.\n\nWhen all phases are done, `\u002Fgsd-complete-milestone` archives the milestone and tags the release.\n\nThen `\u002Fgsd-new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.\n\n---\n\n### Quick Mode\n\n```\n\u002Fgsd-quick\n```\n\n**For ad-hoc tasks that don't need full planning.**\n\nQuick mode gives you GSD guarantees (atomic commits, state tracking) with a faster path:\n\n- **Same agents** — Planner + executor, same quality\n- **Skips optional steps** — No research, no plan checker, no verifier\n- **Separate tracking** — Lives in `.planning\u002Fquick\u002F`, not phases\n\nUse for: bug fixes, small features, config changes, one-off tasks.\n\n```\n\u002Fgsd-quick\n> What do you want to do? \"Add dark mode toggle to settings\"\n```\n\n**Creates:** `.planning\u002Fquick\u002F001-add-dark-mode-toggle\u002FPLAN.md`, `SUMMARY.md`\n\n---\n\n## Why It Works\n\n### Context Engineering\n\nOpenCode is incredibly powerful *if* you give it the context it needs. Most people don't.\n\nGSD handles it for you:\n\n| File | What it does |\n|------|--------------|\n| `PROJECT.md` | Project vision, always loaded |\n| `research\u002F` | Ecosystem knowledge (stack, features, architecture, pitfalls) |\n| `REQUIREMENTS.md` | Scoped v1\u002Fv2 requirements with phase traceability |\n| `ROADMAP.md` | Where you're going, what's done |\n| `STATE.md` | Decisions, blockers, position — memory across sessions |\n| `PLAN.md` | Atomic task with XML structure, verification steps |\n| `SUMMARY.md` | What happened, what changed, committed to history |\n| `todos\u002F` | Captured ideas and tasks for later work |\n\nSize limits based on where OpenCode's quality degrades. Stay under, get consistent excellence.\n\n### XML Prompt Formatting\n\nEvery plan is structured XML optimized for OpenCode:\n\n```xml\n\u003Ctask type=\"auto\">\n  \u003Cname>Create login endpoint\u003C\u002Fname>\n  \u003Cfiles>src\u002Fapp\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts\u003C\u002Ffiles>\n  \u003Caction>\n    Use jose for JWT (not jsonwebtoken - CommonJS issues).\n    Validate credentials against users table.\n    Return httpOnly cookie on success.\n  \u003C\u002Faction>\n  \u003Cverify>curl -X POST localhost:3000\u002Fapi\u002Fauth\u002Flogin returns 200 + Set-Cookie\u003C\u002Fverify>\n  \u003Cdone>Valid credentials return cookie, invalid return 401\u003C\u002Fdone>\n\u003C\u002Ftask>\n```\n\nPrecise instructions. No guessing. Verification built in.\n\n### Multi-Agent Orchestration\n\nEvery stage uses the same pattern: a thin orchestrator spawns specialized agents, collects results, and routes to the next step.\n\n| Stage | Orchestrator does | Agents do |\n|-------|------------------|-----------|\n| Research | Coordinates, presents findings | 4 parallel researchers investigate stack, features, architecture, pitfalls |\n| Planning | Validates, manages iteration | Planner creates plans, checker verifies, loop until pass |\n| Execution | Groups into waves, tracks progress | Executors implement in parallel, each with fresh 200k context |\n| Verification | Presents results, routes next | Verifier checks codebase against goals, debuggers diagnose failures |\n\nThe orchestrator never does heavy lifting. It spawns agents, waits, integrates results.\n\n**The result:** You can run an entire phase — deep research, multiple plans created and verified, thousands of lines of code written across parallel executors, automated verification against goals — and your main context window stays at 30-40%. The work happens in fresh subagent contexts. Your session stays fast and responsive.\n\n### Atomic Git Commits\n\nEach task gets its own commit immediately after completion:\n\n```bash\nabc123f docs(08-02): complete user registration plan\ndef456g feat(08-02): add email confirmation flow\nhij789k feat(08-02): implement password hashing\nlmn012o feat(08-02): create registration endpoint\n```\n\n> [!NOTE]\n> **Benefits:** Git bisect finds exact failing task. Each task independently revertable. Clear history for OpenCode in future sessions. Better observability in AI-automated workflow.\n\nEvery commit is surgical, traceable, and meaningful.\n\n### Modular by Design\n\n- Add phases to current milestone\n- Insert urgent work between phases\n- Complete milestones and start fresh\n- Adjust plans without rebuilding everything\n\nYou're never locked in. The system adapts.\n\n---\n\n## Commands\n\n### Core Workflow\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-new-project` | Full initialization: questions → research → requirements → roadmap |\n| `\u002Fgsd-discuss-phase [N]` | Capture implementation decisions before planning |\n| `\u002Fgsd-plan-phase [N]` | Research + plan + verify for a phase |\n| `\u002Fgsd-execute-phase \u003CN>` | Execute all plans in parallel waves, verify when complete |\n| `\u002Fgsd-verify-work [N]` | Manual user acceptance testing ¹ |\n| `\u002Fgsd-audit-milestone` | Verify milestone achieved its definition of done |\n| `\u002Fgsd-complete-milestone` | Archive milestone, tag release |\n| `\u002Fgsd-new-milestone [name]` | Start next version: questions → research → requirements → roadmap |\n\n### Navigation\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-progress` | Where am I? What's next? |\n| `\u002Fgsd-help` | Show all commands and usage guide |\n| `\u002Fgsd-update` | Update GSD with changelog preview |\n| `\u002Fgsd-join-discord` | Join the GSD Discord community |\n\n### Brownfield\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-map-codebase` | Analyze existing codebase before new-project |\n\n### Phase Management\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-add-phase` | Append phase to roadmap |\n| `\u002Fgsd-insert-phase [N]` | Insert urgent work between phases |\n| `\u002Fgsd-remove-phase [N]` | Remove future phase, renumber |\n| `\u002Fgsd-list-phase-assumptions [N]` | See OpenCode's intended approach before planning |\n| `\u002Fgsd-plan-milestone-gaps` | Create phases to close gaps from audit |\n\n### Session\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-pause-work` | Create handoff when stopping mid-phase |\n| `\u002Fgsd-resume-work` | Restore from last session |\n\n### Utilities\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-settings` | Interactive settings: profiles, stage overrides, workflow toggles |\n| `\u002Fgsd-set-profile \u003Cprofile>` | Switch model profile (quality\u002Fbalanced\u002Fbudget) |\n| `\u002Fgsd-set-model [profile]` | Configure models for a profile's stages |\n| `\u002Fgsd-add-todo [desc]` | Capture idea for later |\n| `\u002Fgsd-check-todos` | List pending todos |\n| `\u002Fgsd-debug [desc]` | Systematic debugging with persistent state |\n| `\u002Fgsd-quick` | Execute ad-hoc task with GSD guarantees |\n\n\u003Csup>¹ Contributed by reddit user OracleGreyBeard\u003C\u002Fsup>\n\n---\n\n## Configuration\n\nGSD stores project settings in `.planning\u002Fconfig.json`. Configure during `\u002Fgsd-new-project` or update later with `\u002Fgsd-settings`.\n\n### Core Settings\n\n| Setting | Options | Default | What it controls |\n|---------|---------|---------|------------------|\n| `mode` | `yolo`, `interactive` | `interactive` | Auto-approve vs confirm at each step |\n| `depth` | `quick`, `standard`, `comprehensive` | `standard` | Planning thoroughness (phases × plans) |\n\n### Model Profiles (gsd-opencode specific)\n\n| Profile | Planning | Execution | Verification | \n|---------|---------|---------|------------------|\n| Simple  | First model | First model | First model |\n| Smart   | First model | First model | Second model |\n| Genius  | First model | Second model | Third model |\n\n#### How It Works\n\nGSD uses a **stage-based model assignment** system. Instead of configuring each agent individually, you assign models to three stages:\n\n| Stage | Agents | Purpose |\n|-------|--------|---------|\n| **Planning** | gsd-planner, gsd-plan-checker, gsd-phase-researcher, gsd-roadmapper, gsd-project-researcher, gsd-research-synthesizer, gsd-codebase-mapper | Architecture decisions, research, task design |\n| **Execution** | gsd-executor, gsd-debugger | Code implementation following explicit plans |\n| **Verification** | gsd-verifier, gsd-integration-checker | Checking deliverables against goals |\n\n#### Configuration Files\n\nTwo files manage model assignments:\n\n| File | Purpose |\n|------|---------|\n| `.planning\u002Foc-config.json` | **Source of truth** — stores profiles |\n| `opencode.json` | **Derived config** — agent-to-model mappings read by OpenCode |\n\nWhen you change profiles or models, GSD updates both files. OpenCode reads `opencode.json` at startup.\n\n#### Presets \n\n**Presets** define the base models for each profile:\n\n```json\n{\n  \"profiles\": {\n    \"presets\": {\n      \"genius\": {\n        \"planning\": \"bailian-coding-plan\u002Fqwen3.5-plus\",\n        \"execution\": \"bailian-coding-plan\u002Fkimi-k2.5\",\n        \"verification\": \"bailian-coding-plan\u002FMiniMax-M2.5\"\n      }\n    }\n  },\n  \"current_oc_profile\": \"genius\"\n}\n```\n\n#### First-Run Setup\n\nOn first use (or when running `\u002Fgsd-set-profile` → Reset presets), the **Preset Setup Wizard** runs:\n\n1. Queries `opencode models` to discover available models\n2. Prompts you to select models for each profile\u002Fstage (9 selections total)\n3. Saves configuration to `.planning\u002Foc-config.json`\n4. Generates `opencode.json` with agent mappings\n\nThis ensures your presets use models actually available in your OpenCode installation.\n\n#### Commands\n\n| Command | What it does |\n|---------|--------------|\n| `\u002Fgsd-set-profile` | Full interactive menu: switch profiles, set\u002Fclear overrides, reset presets, toggle workflow agents |\n| `\u002Fgsd-set-profile \u003Cprofile>` | Quick switch between simple\u002Fsmart\u002Fgenius profiles |\n\n\n**Examples:**\n\n```bash\n# Switch to simple profile\n\u002Fgsd-set-profile simple\n\n# Configure balanced profile's models interactively\n\u002Fgsd-set-profile balanced\n\n# Open full settings menu\n\u002Fgsd-settings\n```\n\n#### Profile Philosophy\n\nWhen configuring your presets:\n\n- **simple** — Use your most capable model for all stages. Best for critical architecture work.\n- **smart** — Strong model for planning (decisions matter), mid-tier for execution\u002Fverification (follows instructions).\n- **genius** — Strong model for planning (decisions matter), mid-tier for execution\u002Fverification (follows instructions), lightweight for research\u002Fverification. Best for high-volume work.\n\n#### Important: Restart Required\n\nOpenCode loads `opencode.json` at startup and **does not hot-reload** model assignments. After changing profiles or models:\n\n1. Fully quit OpenCode\n2. Relaunch OpenCode\n\nYour new model assignments will then be active.\n\n### Workflow Agents\n\nThese spawn additional agents during planning\u002Fexecution. They improve quality but add tokens and time.\n\n| Setting | Default | What it does |\n|---------|---------|--------------|\n| `workflow.research` | `true` | Researches domain before planning each phase |\n| `workflow.plan_check` | `true` | Verifies plans achieve phase goals before execution |\n| `workflow.verifier` | `true` | Confirms must-haves were delivered after execution |\n\nUse `\u002Fgsd-settings` to toggle these, or override per-invocation:\n- `\u002Fgsd-plan-phase --skip-research`\n- `\u002Fgsd-plan-phase --skip-verify`\n\n### Execution\n\n| Setting | Default | What it controls |\n|---------|---------|------------------|\n| `parallelization.enabled` | `true` | Run independent plans simultaneously |\n| `planning.commit_docs` | `true` | Track `.planning\u002F` in git |\n\n---\n\n## Troubleshooting\n\n**Commands not found after install?**\n- See the [Distribution System Troubleshooting](#troubleshooting-installation-issues) section for detailed help\n- Verify installation: `gsd-opencode list`\n- Restart OpenCode to reload slash commands\n\n**Permission denied during installation?**\n- See [Troubleshooting Installation Issues](#troubleshooting-installation-issues) for solutions\n\n**Updating to the latest version?**\n```bash\n# Use the built-in update command\ngsd-opencode update\n\n# Or reinstall via npm\nnpx gsd-opencode@latest\n```\n\n**Using Docker or containerized environments?**\n\nSee the [Docker\u002FContainer Usage](#dockercontainer-usage) section for detailed instructions.\n\nIf file reads fail with tilde paths (`~\u002F.config\u002Fopencode\u002F...`), set `OPENCODE_CONFIG_DIR` before installing:\n```bash\nOPENCODE_CONFIG_DIR=\u002Fhome\u002Fyouruser\u002F.config\u002Fopencode npx gsd-opencode --global\n```\nThis ensures absolute paths are used instead of `~` which may not expand correctly in containers.\n\n---\n\n\n## Star History\n\n[![Star History Chart](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Frokicool_gsd-opencode_readme_059bc2fea1d6.png)](https:\u002F\u002Fwww.star-history.com\u002F#rokicool\u002Fgsd-opencode&type=date&legend=top-left)\n\n## License\n\nMIT License. See [LICENSE](LICENSE) for details.\n\n---\n\n\u003Cdiv align=\"center\">\n\n**OpenCode is promising. GSD makes it reliable.**\n\n\u003C\u002Fdiv>\n","\u003Cdiv align=\"left\">\n\n# GET SHIT DONE for OpenCode.（基于 TÂCHES v1.33.0 - 2026-04-04）\n\n**由 TÂCHES 提供的轻量级且功能强大的元提示、上下文工程与规范驱动开发系统，专为 Claude Code 打造。（由 rokicool 及爱好者改编用于 OpenCode）**\n\n[TÂCHES 原始 GitHub 仓库](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done)\n\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Fgsd-opencode?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fgsd-opencode)\n[![npm downloads](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002Fgsd-opencode?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fgsd-opencode)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue?style=for-the-badge)](LICENSE)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Frokicool\u002Fgsd-opencode?style=for-the-badge&logo=github&color=181717)](https:\u002F\u002Fgithub.com\u002Frokicool\u002Fgsd-opencode)\n\n---\n\n# （未）最新消息\n\nTACHES 决定在其产品中加入对 OpenCode 的支持。这无疑是个好消息。\n\n然而，恕我直言，他对 OpenCode 的适配并不完美。因此，我将继续推进这个项目，并努力填补其中的不足。\n\n感谢 [@dpearson2699](https:\u002F\u002Fgithub.com\u002Fdpearson2699)，我们实现了更为出色的 \u002Fgsd-settings 命令适配，以及子代理之间几乎可动态切换的不同 LLM 支持。\n\n—— **Roman**（2026-01-31）\n\n[![IMAGE ALT TEXT HERE](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Frokicool_gsd-opencode_readme_7291cd6ca794.jpg)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=zRJ0UWHBjCY)\n\n---\n\n\u003Cbr>\n\n```bash\n$ npx gsd-opencode\n\n或者\n\n$ npx gsd-opencode@latest\n\n```\n\n**适用于 Mac、Windows 和 Linux。**\n\n\u003Cbr>\n\n![GSD 安装](assets\u002Fterminal.svg)\n\n\u003Cbr>\n\n*\"如果你清楚自己想要什么，它就会为你实现，绝不含糊。\"*\n\n*\"我用过 SpecKit、OpenSpec 和 Taskmaster——但 GSD 给我的效果最好。\"*\n\n*\"迄今为止，它是我使用 Claude Code 最强大的补充工具。没有过度设计，真正做到了高效完成任务。\"*\n\n\u003Cbr>\n\n**受到亚马逊、谷歌、Shopify 和 Webflow 工程师的信赖。**\n\n[我为何构建此项目](#why-i-built-this) · [分发体系](#distribution-system) · [工作原理](#how-it-works) · [命令](#commands) · [成功之道](#why-it-works)\n\n\u003C\u002Fdiv>\n\n---\n\n\n\n## 我为何构建此项目 \n\n我是一名独立开发者。我不写代码——是 Claude Code 在帮我完成。 \n\n市面上已有其他规范驱动的开发工具，比如 BMAD、Speckit 等。但它们要么让流程变得过于复杂（如冲刺仪式、故事点、利益相关者同步会议、回顾会、Jira 工作流），要么缺乏对整体目标的清晰理解。而我并不是一家拥有五十人的软件公司。我不想搞那些企业式的繁文缛节。我只是一个富有创造力的人，只想打造出真正实用的好东西。\n\n于是，我打造了 GSD。复杂性隐藏在系统内部，而非你的工作流程之中。后台涉及上下文工程、XML 提示格式化、子代理编排和状态管理。你看到的只是几个简单好用的命令而已。\n\n该系统为 Claude Code 提供了完成并验证工作的所有必要条件。我对这套流程充满信心，因为它确实行之有效。\n\n这就是它的本质：没有那些企业角色扮演式的废话，只有一套极其高效的系统，帮助你持续地利用 Claude Code 打造酷炫的产品。\n\n—— **TÂCHES**\n\n\n## 来自译者……\n\n我非常喜欢 GSD 和 OpenCode。总觉得只让 GSD 服务于 Claude Code 有些不公平。\n\n—— **Roman**\n\n## 版本 1.33.2\n\n新增了将 `Agent()` 后台任务调用转换为 OpenCode 兼容的 `@gsd-\u003Cagent>` 简写语法的功能。`assets\u002Fconfigs\u002Fremove-task.json` 中的新规则 21 会动态提取 `skill=\"gsd-\u003Cagent>\"` 模式中的代理名称，并将其转换为 OpenCode 格式。此次更新修复了 `autonomous.md` 工作流中计划与执行阶段调度部分的两个 `Agent()` 调用，确保完全兼容 OpenCode。\n\n## 版本 1.33.0\n\n我们再次紧跟原始 GSDv1 的 [v1.33.0](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done\u002Freleases\u002Ftag\u002Fv1.33.0)（2026-04-04）版本。\n\n而在本地，我们也做了许多改动。其中最重要的一点是移除了 `task()` 调用，因为 OpenCode 不支持这一语法，取而代之的是直接调用代理的方式。\n\n## 版本 1.30.0\n\n我们继续跟进原始 GSDv1 的 v1.30.0 版本（2026-03-30）。\n\n为了支持 “skill(skill='command-name')” 语法，我采取了一个颇具争议的解决方案。除此之外，其他部分都应能正常运行。\n\n## 版本 1.22.1\n\n我决定为所有自定义代理添加 ‘mode: subagent’ 属性。这不应影响任何 GSD 功能，但应该能够从 Tab 键显示的代理列表中移除不必要的条目。如果我遗漏了什么，请随时提出意见。\n\n## 版本 1.22.0 — 我们正在追赶原始 v1.22.4（2026-03-03）\n\n一如既往，你可以在我们的 [原始 CHANGELOG.md v1.20.5 -> v1.22.4](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md) 中找到 TACHES 所做的全部更改。\n\n这些变更的核心在于，原始 GSD 使用正确的语法来执行代理任务。因此，不会再出现意外停止的情况，也不会导致规划完成后 Gsd-Planner 仍处于活动状态。\n\n而在 gsd-opencode 方面，我们进行了一些修复，并对后端进行了大量调整。\n\n## 版本 1.20.3 — 新的 gsd-opencode 模型配置文件系统\n\n我不得不放弃对原始 GSD 模型配置文件系统的支持。Claude Code 使用三种不同的模型：Opus、Sonnet 和 Haiku。而在 OpenCode 中，我们则有数十家供应商和数百种模型可供选择。因此，GSD 的模型配置文件系统并不适用于我们。\n\n所以我重新设计了这一系统，暂时命名为“简单|智能|天才”。希望这能解决意外停止的问题。\n\n- `\u002Fgsd-settings` — *不再对模型与代理的分配进行任何更改*。它会询问模型配置文件，但不会执行任何操作。你需要自行运行 `\u002Fgsd-set-profile`。\n- `\u002Fgsd-check-profile` — 检查 gsd-opencode 的配置文件，并报告可能存在的问题（如有）。\n- `\u002Fgsd-set-profile` — 这是你控制每个阶段使用哪种模型的主要界面。试试看吧！真的，**试一试！**\n\n## 版本 1.20.0 — 我们正在追赶原始 v1.20.5\n\n同样，你可以在 [原始 CHANGELOG.md v1.9.4 -> v1.20.5](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md) 中找到 TACHES 所有的改动。\n\n至于我们这边，虽然有许多小改动，但在配置文件管理方面有一个重要的调整。我们没有照搬 TACHES\u002FClaude Code 的做法，而是采用了更符合 OpenCode 的方式。\n\nGSD-OpenCode 支持三种配置文件：\n\n - 简单（允许为所有类型的 gsd 自定义代理指定单一模型）\n - 智能（允许为 gsd 自定义代理指定两种不同模型：一种用于……）\n - 天才（好吧，其实称不上“天才”，但至少可以为自定义代理指定三种不同的模型）\n\n## 版本 1.9.0 - 我们正在追赶原始的 v1.9.4\n\n您可以在 [原始 CHANGELOG.md v1.6.4 -> v1.9.4](https:\u002F\u002Fgithub.com\u002Fglittercowboy\u002Fget-shit-done\u002Fblob\u002Fmain\u002FCHANGELOG.md) 中找到 TACHES 所做的所有更改。\n\n### 模型配置文件管理\n\nOpenCode 现在支持通过以下方式进行全面的模型配置文件管理：\n- `\u002Fgsd-settings` — 配置文件、阶段覆盖和工作流切换的交互式设置菜单\n- `\u002Fgsd-set-profile \u003Cprofile>` — 在高质量\u002F平衡\u002F预算配置文件之间快速切换\n- `\u002Fgsd-set-model \u003Cprofile>` — 配置每个配置文件使用的模型\n\n这些命令会管理 `.planning\u002Fconfig.json` 文件，并生成包含代理与模型映射关系的 `opencode.json` 文件。请注意：更改配置文件后，请退出并重新启动 OpenCode，以使更改生效。\n\n## 版本 1.6.0 - 我们开始使用 Git 子模块\n\n如果您克隆了这个仓库，请别忘了在克隆后执行以下命令：\n\n```\n$ git submodule update --init --recursive \n```\n\n这将从 TÂCHES 仓库更新\u002F填充 .\u002Foriginal\u002Fget-shit-done 文件夹。\n\n这里有一篇关于 Git 子模块的简洁文章：[使用子模块](https:\u002F\u002Fgithub.blog\u002Fopen-source\u002Fgit\u002Fworking-with-submodules\u002F)。感谢 @borisnaydis 指出这一点。\n\n## 版本 1.5.0 - 破坏性变更：命令命名规范更新\n\n**⚠️ 重要提示：命令语法的破坏性变更**\n\n我们进行了更新，以使 GSD 的命令命名规范与 OpenCode 的标准 `kebab-case` 格式保持一致。不幸的是，这给用户一直习惯的可见命令语法带来了破坏性变更。\n\n### 更改内容\n\n**命令命名：** 所有 GSD 命令已从 `\u002Fgsd:` 前缀更新为 `\u002Fgsd-` 格式。\n\n### 为什么进行此更改？\n\n`gsd-kebab-case` 命名规范遵循 OpenCode 的标准命令格式。这种对齐确保了整个生态系统的统一性，并提高了兼容性。\n**注意：** 我们理解这对可见命令语法来说是一个不幸的破坏性变更。如果将来有可能的话，我们可能会考虑恢复原来的 `\u002Fgsd:` 语法，同时保持向后兼容性。\n\n### 迁移指南\n\n对于升级到版本 1.5.0 的用户，只需将所有 GSD 命令中的冒号（`:`）替换为连字符（`-`）即可：\n\n- 旧版：`\u002Fgsd:plan-phase 1`\n- 新版：`\u002Fgsd-plan-phase 1`\n\n所有功能保持不变——只有命令前缀发生了变化。\n\n---\n\nVibecoding 的名声并不好。您描述自己的需求，AI 会生成代码，但结果往往不一致，甚至在规模扩大时就会崩溃。\n\nGSD 解决了这个问题。它是让 OpenCode 变得可靠的上下文工程层。只需描述您的想法，让系统提取所需的所有信息，然后让 OpenCode 开始工作。\n\n---\n\n## 适合人群\n\n那些希望描述自己的需求并让系统正确构建出来的人——而无需假装自己运营着一个拥有 50 名工程师的团队。\n\n---\n\n## 开始使用\n\n```bash\nnpx gsd-opencode\n\n# 或者\n\nnpm install gsd-opencode -g\ngsd-opencode install\n\n```\n\n就这么简单。可以通过 `\u002Fgsd-help` 进行验证。\n\n### 保持更新\n\nGSD 发展迅速。请定期检查更新：\n\n```\n\u002Fgsd-whats-new\n```\n\n更新方法如下：\n\n```bash\nnpx gsd-opencode@latest\n\n# 或者\n\nnpm install gsd-opencode@latest -g\ngsd-opencode install\n\n```\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>非交互式安装（Docker、CI、脚本）\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```bash\nnpx gsd-opencode --global   # 安装到 ~\u002F.config\u002Fopencode\u002F\nnpx gsd-opencode --local    # 安装到 .opencode\u002F\n```\n\n使用 `--global` (`-g`) 或 `--local` (`-l`) 可跳过交互式提示。\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>卸载 GSD-OpenCode\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```bash\n# 卸载（自动检测全局或本地安装）\ngsd-opencode uninstall\n\n# 全局卸载\ngsd-opencode uninstall --global\ngsd-opencode uninstall -g\n\n# 本地卸载\ngsd-opencode uninstall --local\ngsd-opencode uninstall -l\n\n# 预览将要移除的内容（干运行）\ngsd-opencode uninstall --dry-run\n```\n\n有关详细的卸载选项，包括备份控制和安全功能，请参阅 [DISTRIBUTION-MANAGER.md](.\u002FDISTRIBUTION-MANAGER.md)。\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>开发安装\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n克隆仓库并在本地运行安装程序：\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Frokicool\u002Fgsd-opencode.git\ncd gsd-opencode\ngit submodule update --init --recursive \nnode bin\u002Finstall.js --local\n```\n\n这会安装到 `.opencode\u002F` 目录下，以便在贡献代码之前测试修改。\n\n\u003C\u002Fdetails>\n\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>替代方案：细粒度权限\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n如果您不想使用该标志，可以将以下内容添加到您项目的 `.opencode\u002Fsettings.json` 文件中：\n\n```json\n{\n  $schema: https:\u002F\u002Fopencode.ai\u002Fconfig.json,\n  permission: {\n    bash: allow,\n    read: allow,\n    edit: allow,\n    grep: allow,\n    glob: allow,\n    list: allow\n  }\n}\n```\n\n\u003C\u002Fdetails>\n\n---\n\n## 分发管理器（仅限 gsd-opencode）\n\nGSD-OpenCode 包含一个全面的软件包管理器，用于安装、维护和更新 GSD 系统。通过 npm 安装后，您可以使用完整的 CLI 来管理您的 GSD 安装。\n\n### 快速参考\n\n| 命令 | 描述 |\n|---------|-------------|\n| `gsd-opencode install` | 安装 GSD（交互式） |\n| `gsd-opencode install --global` \u002F `-g` | 全局安装（~\u002F.config\u002Fopencode\u002F） |\n| `gsd-opencode install --local` \u002F `-l` | 本地安装（.\u002F.opencode\u002F） |\n| `gsd-opencode list` | 显示安装状态 |\n| `gsd-opencode check` | 验证安装健康状况 |\n| `gsd-opencode repair` | 修复损坏的安装 |\n| `gsd-opencode update` | 更新到最新版本 |\n| `gsd-opencode uninstall` | 移除安装 |\n\n有关所有命令、选项、故障排除和高级用法的详细文档，请参阅 [DISTRIBUTION-MANAGER.md](.\u002FDISTRIBUTION-MANAGER.md)。\n\n---\n\n## 工作原理\n\n> **已经有代码了吗？** 请先运行 `\u002Fgsd-map-codebase`。它会启动并行代理来分析您的技术栈、架构、惯例和关注点。然后，`\u002Fgsd-new-project` 就会了解您的代码库——问题将集中在您要添加的内容上，规划也会自动加载您的模式。\n\n### 1. 初始化项目\n\n```\n\u002Fgsd-new-project\n```\n\n一条命令，一个流程。系统会：\n\n1. **提问** — 直到完全理解您的想法为止（目标、限制、技术偏好、边缘情况）\n2. **研究** — 启动并行代理来研究相关领域（可选，但建议）\n3. **需求** — 提取哪些是 v1、v2，以及哪些超出范围\n4. **路线图** — 创建与需求相对应的阶段\n\n您批准路线图后，就可以开始构建了。\n\n**创建：** `PROJECT.md`、`REQUIREMENTS.md`、`ROADMAP.md`、`STATE.md`、`.planning\u002Fresearch\u002F`\n\n---\n\n### 2. 讨论阶段\n\n```\n\u002Fgsd-discuss-phase 1\n```\n\n**这是你塑造实现细节的地方。**\n\n你的路线图每个阶段只有一两句话，这样的信息量不足以按照你设想的方式构建项目。这一步骤会在任何调研或规划开始之前，先捕捉你的具体偏好。\n\n系统会分析当前阶段，并根据正在构建的内容识别出潜在的模糊地带：\n\n- **视觉特性** → 布局、密度、交互、空状态\n- **API\u002FCLI** → 响应格式、标志位、错误处理、详细程度\n- **内容系统** → 结构、语气、深度、流程\n- **组织任务** → 分组标准、命名、重复项、例外情况\n\n针对每个领域，系统都会不断提问，直到你满意为止。最终生成的 `CONTEXT.md` 文件将直接用于接下来的两个步骤：\n\n1. **研究员阅读** — 知道该调研哪些模式（例如“用户希望使用卡片布局”→研究卡片组件库）\n2. **规划师阅读** — 知道哪些决策已经确定（例如“决定使用无限滚动”→计划中包含滚动处理逻辑）\n\n你在这里投入得越深入，系统就越能构建出你真正想要的东西。如果你跳过这一步，系统会提供合理的默认配置；而如果你充分利用它，就能实现你自己的愿景。\n\n**生成文件：** `{phase}-CONTEXT.md`\n\n---\n\n### 3. 规划阶段\n\n```\n\u002Fgsd-plan-phase 1\n```\n\n系统会执行以下操作：\n\n1. **调研** — 根据你在 `CONTEXT.md` 中做出的决策，研究如何实现当前阶段\n2. **规划** — 创建2–3个具有XML结构的原子任务计划\n3. **验证** — 对计划进行需求检查，循环直至通过\n\n每个计划都足够小，可以在全新的上下文中执行，不会出现信息冗余或“现在我要更简洁一些”的情况。\n\n**生成文件：** `{phase}-RESEARCH.md`, `{phase}-{N}-PLAN.md`\n\n---\n\n### 4. 执行阶段\n\n```\n\u002Fgsd-execute-phase 1\n```\n\n系统会执行以下操作：\n\n1. **分波运行计划** — 可并行的并行执行，有依赖关系的则按顺序执行\n2. **每个计划独立上下文** — 每个计划拥有20万token的纯净执行环境，不会积累无用信息\n3. **按任务提交代码** — 每个任务都会产生一个独立的提交记录\n4. **对照目标验证** — 检查代码库是否实现了该阶段所承诺的功能\n\n你可以暂时离开，稍后再回来查看已完成的工作，此时Git历史记录将是干净整洁的。\n\n**分波执行机制说明：**\n\n计划会根据依赖关系被分组为“波”。在每一波内部，计划可以并行执行；而不同波之间则是顺序执行。\n\n```\n┌─────────────────────────────────────────────────────────────────────┐\n│  阶段执行                                                    │\n├─────────────────────────────────────────────────────────────────────┤\n│                                                                     │\n│  波1（并行）          波2（并行）          波3       │\n│  ┌─────────┐ ┌─────────┐    ┌─────────┐ ┌─────────┐    ┌─────────┐  │\n│  │ 计划01 │ │ 计划02 │ →  │ 计划03 │ │ 计划04 │ →  │ 计划05 │  │\n│  │         │ │         │    │         │ │         │    │         │  │\n│  │ 用户    │ │ 产品    │    │ 订单  │ │ 购物车│    │ 结账  │  │\n│  │ 模型   │ │ 模型   │    │ API     │ │ API     │    │ UI      │  │\n│  └─────────┘ └─────────┘    └─────────┘ └─────────┘    └─────────┘  │\n│       │           │              ↑           ↑              ↑       │\n│       └───────────┴──────────────┴───────────┘              │       │\n│              依赖关系：计划03需要计划01            │       │\n│                          计划04需要计划02              │       │\n│                          计划05需要计划03和04        │       │\n│                                                                     │\n└─────────────────────────────────────────────────────────────────────┘\n```\n\n**为什么分波很重要：**\n- 独立的计划 → 同一波 → 并行执行\n- 有依赖关系的计划 → 后续波 → 等待依赖完成\n- 文件冲突 → 顺序执行或合并为同一计划\n\n这就是为什么“垂直切片”（例如计划01：用户功能端到端）比“水平分层”（例如计划01：所有模型，计划02：所有API）更能并行化的原因。\n\n**生成文件：** `{phase_num}-{N}-SUMMARY.md`, `{phase_num}-VERIFICATION.md`\n\n---\n\n### 5. 验证工作\n\n```\n\u002Fgsd-verify-work 1\n```\n\n**这是你确认功能确实正常运作的时候。**\n\n自动化验证会检查代码是否存在以及测试是否通过。但这个功能是否真的如你预期般工作呢？这正是你亲自体验的机会。\n\n系统会执行以下操作：\n\n1. **提取可测试的交付成果** — 你现在应该能够完成的操作\n2. **逐一引导你进行测试** — “你能用邮箱登录吗？”是\u002F否，或者描述问题所在\n3. **自动诊断失败原因** — 启动调试代理来找出根本原因\n4. **创建已验证的修复计划** — 准备好立即重新执行\n\n如果一切顺利，就可以进入下一阶段。如果有问题，你无需手动调试——只需再次运行 `\u002Fgsd-execute-phase`，系统会自动带上它生成的修复计划。\n\n**生成文件：** `{phase}-UAT.md`, 若发现问题则生成修复计划\n\n---\n\n### 6. 重复 → 完成 → 下一里程碑\n\n```\n\u002Fgsd-discuss-phase 2\n\u002Fgsd-plan-phase 2\n\u002Fgsd-execute-phase 2\n\u002Fgsd-verify-work 2\n...\n\u002Fgsd-complete-milestone\n\u002Fgsd-new-milestone\n```\n\n循环执行 **讨论 → 规划 → 执行 → 验证**，直到里程碑完成。\n\n每个阶段都需要你的输入（讨论）、充分的调研（规划）、干净的执行（执行）以及人工验证（验证）。整个过程保持上下文的纯净，从而确保高质量的产出。\n\n当所有阶段完成后，`\u002Fgsd-complete-milestone` 会归档该里程碑并标记发布版本。\n\n随后，`\u002Fgsd-new-milestone` 将启动下一个版本——流程与新建项目相同，只是针对你现有的代码库。你需要描述接下来想开发的内容，系统会调研相关领域、明确需求范围，并生成一份新的路线图。每一个里程碑都是一个完整的闭环：定义 → 构建 → 发布。\n\n---\n\n### 快速模式\n\n```\n\u002Fgsd-quick\n```\n\n**适用于不需要完整规划的临时性任务。**\n\n快速模式提供了GSD的核心保障（原子提交、状态跟踪），同时采用更快捷的路径：\n\n- **相同的智能体** — 规划师与执行者，质量一致\n- **跳过可选步骤** — 无需调研、无需计划检查、无需验证\n- **独立的跟踪记录** — 存储在 `.planning\u002Fquick\u002F` 目录下，不计入各阶段\n\n适合用于：修复Bug、小型功能、配置变更、一次性任务。\n\n```\n\u002Fgsd-quick\n> 你想做什么？“在设置中添加暗黑模式切换”\n```\n\n**生成文件：** `.planning\u002Fquick\u002F001-add-dark-mode-toggle\u002FPLAN.md`, `SUMMARY.md`\n\n---\n\n## 为何有效\n\n### 上下文工程\n\nOpenCode 非常强大，*前提是*你为其提供所需的上下文。然而，大多数人并没有做到这一点。\n\nGSD 会为你处理这一切：\n\n| 文件 | 作用 |\n|------|------|\n| `PROJECT.md` | 项目愿景，始终加载 |\n| `research\u002F` | 生态系统知识（技术栈、功能、架构、陷阱） |\n| `REQUIREMENTS.md` | 范围明确的 v1\u002Fv2 需求，并附带阶段可追溯性 |\n| `ROADMAP.md` | 项目目标及已完成内容 |\n| `STATE.md` | 决策、阻碍因素、当前状态——跨会话的记忆 |\n| `PLAN.md` | 原子级任务，采用 XML 结构，包含验证步骤 |\n| `SUMMARY.md` | 发生了什么、有何变化、已提交至历史记录 |\n| `todos\u002F` | 捕捉待后续处理的想法和任务 |\n\n根据 OpenCode 质量开始下降的界限设定文件大小限制。保持在限制内，即可获得持续的卓越表现。\n\n### XML 提示格式化\n\n每个计划都以针对 OpenCode 优化的结构化 XML 格式呈现：\n\n```xml\n\u003Ctask type=\"auto\">\n  \u003Cname>创建登录端点\u003C\u002Fname>\n  \u003Cfiles>src\u002Fapp\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts\u003C\u002Ffiles>\n  \u003Caction>\n    使用 jose 库生成 JWT（而非 jsonwebtoken — 因 CommonJS 引发问题）。\n    对用户表中的凭据进行验证。\n    成功时返回 httpOnly Cookie。\n  \u003C\u002Faction>\n  \u003Cverify>使用 curl -X POST localhost:3000\u002Fapi\u002Fauth\u002Flogin 应返回 200 状态码及 Set-Cookie 头\u003C\u002Fverify>\n  \u003Cdone>有效凭据返回 Cookie，无效凭据返回 401 错误\u003C\u002Fdone>\n\u003C\u002Ftask>\n```\n\n精确的指令，无需猜测，内置验证机制。\n\n### 多智能体编排\n\n每个阶段都采用相同的模式：一个轻量级的编排器会启动专门的智能体，收集结果并将其传递到下一步。\n\n| 阶段 | 编排器做什么 | 智能体做什么 |\n|-------|------------------|-----------|\n| 研究 | 协调并展示研究结果 | 4 个并行的研究员分别调查技术栈、功能、架构和潜在陷阱 |\n| 规划 | 验证并管理迭代 | 规划师制定计划，检查者验证，循环直至通过 |\n| 执行 | 将任务分组为批次，跟踪进度 | 执行者并行实现任务，每个执行者拥有全新的 20 万 token 上下文 |\n| 验证 | 展示结果并引导下一步 | 验证者对照目标检查代码库，调试者诊断失败原因 |\n\n编排器本身并不承担繁重的工作。它负责启动智能体、等待结果并整合反馈。\n\n**结果：** 你可以完成整个阶段——深入研究、创建并验证多个计划、由多个执行者并行编写数千行代码、自动验证是否符合目标——而你的主上下文窗口始终保持在 30%–40% 左右。实际工作是在全新的子智能体上下文中进行的。因此，你的会话始终保持快速响应。\n\n### 原子级 Git 提交\n\n每个任务完成后会立即生成独立的提交：\n\n```bash\nabc123f docs(08-02): 完成用户注册计划\ndef456g feat(08-02): 添加邮箱确认流程\nhij789k feat(08-02): 实现密码哈希\nlmn012o feat(08-02): 创建注册端点\n```\n\n> [!NOTE]\n> **好处：** Git bisect 可以精准定位出错的任务。每个任务都可以独立回滚。为未来的 OpenCode 会话提供了清晰的历史记录。在 AI 自动化的工作流中，可观测性更强。\n\n每一个提交都精准、可追溯且具有明确的意义。\n\n### 模块化设计\n\n- 可以向当前里程碑添加新阶段\n- 在各阶段之间插入紧急任务\n- 完成里程碑后重新开始\n- 无需重建整体即可调整计划\n\n你永远不会被锁定。系统会灵活适应。\n\n---\n\n## 命令\n\n### 核心工作流\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-new-project` | 完整初始化：提问 → 研究 → 需求 → 路线图 |\n| `\u002Fgsd-discuss-phase [N]` | 在规划前记录实施决策 |\n| `\u002Fgsd-plan-phase [N]` | 为某一阶段进行研究、规划并验证 |\n| `\u002Fgsd-execute-phase \u003CN>` | 并行分批执行所有计划，完成后进行验证 |\n| `\u002Fgsd-verify-work [N]` | 手动用户验收测试 ¹ |\n| `\u002Fgsd-audit-milestone` | 验证里程碑是否达到“完成”的定义 |\n| `\u002Fgsd-complete-milestone` | 归档里程碑并标记发布版本 |\n| `\u002Fgsd-new-milestone [name]` | 开始下一个版本：提问 → 研究 → 需求 → 路线图 |\n\n### 导航\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-progress` | 我目前处于哪个阶段？接下来要做什么？ |\n| `\u002Fgsd-help` | 显示所有命令及使用指南 |\n| `\u002Fgsd-update` | 更新 GSD，并预览变更日志 |\n| `\u002Fgsd-join-discord` | 加入 GSD Discord 社区 |\n\n### 老项目改造\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-map-codebase` | 在新建项目之前分析现有代码库 |\n\n### 阶段管理\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-add-phase` | 向路线图追加阶段 |\n| `\u002Fgsd-insert-phase [N]` | 在阶段之间插入紧急任务 |\n| `\u002Fgsd-remove-phase [N]` | 删除未来阶段并重新编号 |\n| `\u002Fgsd-list-phase-assumptions [N]` | 查看 OpenCode 在规划前的预期方法 |\n| `\u002Fgsd-plan-milestone-gaps` | 创建阶段以填补审计发现的空白 |\n\n### 会话管理\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-pause-work` | 在阶段中途停止时创建交接 |\n| `\u002Fgsd-resume-work` | 从上次会话恢复工作 |\n\n### 实用工具\n\n| 命令 | 作用 |\n|---------|--------------|\n| `\u002Fgsd-settings` | 交互式设置：配置文件、阶段覆盖、工作流开关 |\n| `\u002Fgsd-set-profile \u003Cprofile>` | 切换模型配置文件（高质量\u002F平衡\u002F经济型） |\n| `\u002Fgsd-set-model [profile]` | 为特定配置文件的阶段配置模型 |\n| `\u002Fgsd-add-todo [desc]` | 捕捉待后续处理的想法 |\n| `\u002Fgsd-check-todos` | 列出待办事项 |\n| `\u002Fgsd-debug [desc]` | 带有持久状态的系统化调试 |\n| `\u002Fgsd-quick` | 使用 GSD 保障执行临时任务 |\n\n\u003Csup>¹ 由 Reddit 用户 OracleGreyBeard 贡献\u003C\u002Fsup>\n\n---\n\n## 配置\n\nGSD 将项目设置存储在 `.planning\u002Fconfig.json` 中。可以在 `\u002Fgsd-new-project` 期间配置，或稍后通过 `\u002Fgsd-settings` 进行更新。\n\n### 核心设置\n\n| 设置 | 选项 | 默认值 | 控制内容 |\n|---------|---------|---------|------------------|\n| `mode` | `yolo`、`interactive` | `interactive` | 自动批准 vs 每步确认 |\n| `depth` | `quick`、`standard`、`comprehensive` | `standard` | 规划的详尽程度（阶段 × 计划） |\n\n### 模型配置文件（gsd-opencode 特定）\n\n| 配置文件 | 规划 | 执行 | 验证 |\n|---------|---------|---------|------------------|\n| 简单  | 第一个模型 | 第一个模型 | 第一个模型 |\n| 智能   | 第一个模型 | 第一个模型 | 第二个模型 |\n| 天才  | 第一个模型 | 第二个模型 | 第三个模型 |\n\n#### 工作原理\n\nGSD 使用一种基于**阶段的模型分配**系统。您无需单独配置每个代理，而是将模型分配给三个阶段：\n\n| 阶段 | 代理 | 目的 |\n|-------|--------|---------|\n| **规划** | gsd-planner、gsd-plan-checker、gsd-phase-researcher、gsd-roadmapper、gsd-project-researcher、gsd-research-synthesizer、gsd-codebase-mapper | 架构决策、研究、任务设计 |\n| **执行** | gsd-executor、gsd-debugger | 按照明确计划实现代码 |\n| **验证** | gsd-verifier、gsd-integration-checker | 根据目标检查交付成果 |\n\n#### 配置文件\n\n有两个文件管理模型分配：\n\n| 文件 | 目的 |\n|------|---------|\n| `.planning\u002Foc-config.json` | **事实来源** — 存储配置文件 |\n| `opencode.json` | **派生配置** — OpenCode 读取的代理到模型映射 |\n\n当您更改配置文件或模型时，GSD 会更新这两个文件。OpenCode 在启动时读取 `opencode.json`。\n\n#### 预设\n\n**预设**定义了每个配置文件的基础模型：\n\n```json\n{\n  \"profiles\": {\n    \"presets\": {\n      \"genius\": {\n        \"planning\": \"bailian-coding-plan\u002Fqwen3.5-plus\",\n        \"execution\": \"bailian-coding-plan\u002Fkimi-k2.5\",\n        \"verification\": \"bailian-coding-plan\u002FMiniMax-M2.5\"\n      }\n    }\n  },\n  \"current_oc_profile\": \"genius\"\n}\n```\n\n#### 首次运行设置\n\n首次使用时（或运行 `\u002Fgsd-set-profile` → 重置预设时），会运行**预设设置向导**：\n\n1. 查询 `opencode models` 以发现可用模型\n2. 提示您为每个配置文件\u002F阶段选择模型（共9次选择）\n3. 将配置保存到 `.planning\u002Foc-config.json`\n4. 生成包含代理映射的 `opencode.json`\n\n这确保您的预设使用的是 OpenCode 安装中实际可用的模型。\n\n#### 命令\n\n| 命令 | 功能 |\n|---------|--------------|\n| `\u002Fgsd-set-profile` | 完整交互式菜单：切换配置文件、设置\u002F清除覆盖、重置预设、切换工作流代理 |\n| `\u002Fgsd-set-profile \u003Cprofile>` | 快速在简单\u002F智能\u002F天才配置文件之间切换 |\n\n\n**示例：**\n\n```bash\n# 切换到简单配置文件\n\u002Fgsd-set-profile simple\n\n# 交互式配置平衡配置文件的模型\n\u002Fgsd-set-profile balanced\n\n# 打开完整设置菜单\n\u002Fgsd-settings\n```\n\n#### 配置文件理念\n\n在配置预设时：\n\n- **简单** — 在所有阶段都使用您最强大的模型。最适合关键的架构工作。\n- **智能** — 强大的模型用于规划（决策很重要），中等水平的模型用于执行\u002F验证（遵循指令）。\n- **天才** — 强大的模型用于规划（决策很重要），中等水平的模型用于执行\u002F验证（遵循指令），轻量级模型用于研究\u002F验证。最适合高容量的工作。\n\n#### 重要提示：需要重启\n\nOpenCode 在启动时加载 `opencode.json`，并且**不会热加载**模型分配。更改配置文件或模型后：\n\n1. 完全退出 OpenCode\n2. 重新启动 OpenCode\n\n这样新的模型分配才会生效。\n\n### 工作流代理\n\n这些代理会在规划\u002F执行过程中生成额外的代理。它们可以提高质量，但会增加 token 数量和时间。\n\n| 设置 | 默认值 | 功能 |\n|---------|---------|--------------|\n| `workflow.research` | `true` | 在规划每个阶段之前进行领域研究 |\n| `workflow.plan_check` | `true` | 在执行前验证计划是否达到阶段目标 |\n| `workflow.verifier` | `true` | 在执行后确认必须交付的内容已到位 |\n\n您可以使用 `\u002Fgsd-settings` 来切换这些设置，或者在每次调用时进行覆盖：\n- `\u002Fgsd-plan-phase --skip-research`\n- `\u002Fgsd-plan-phase --skip-verify`\n\n### 执行\n\n| 设置 | 默认值 | 控制内容 |\n|---------|---------|------------------|\n| `parallelization.enabled` | `true` | 同时运行独立的计划 |\n| `planning.commit_docs` | `true` | 将 `.planning\u002F` 跟踪到 git 中 |\n\n---\n\n## 故障排除\n\n**安装后找不到命令？**\n- 请参阅[分发系统故障排除](#troubleshooting-installation-issues)部分以获取详细帮助\n- 验证安装：`gsd-opencode list`\n- 重启 OpenCode 以重新加载斜杠命令\n\n**安装过程中权限被拒绝？**\n- 请参阅[安装问题故障排除](#troubleshooting-installation-issues)部分以获取解决方案\n\n**如何更新到最新版本？**\n```bash\n# 使用内置更新命令\ngsd-opencode update\n\n# 或通过 npm 重新安装\nnpx gsd-opencode@latest\n```\n\n**使用 Docker 或容器化环境？**\n\n请参阅[Docker\u002F容器使用](#dockercontainer-usage)部分以获取详细说明。\n\n如果使用波浪号路径 (`~\u002F.config\u002Fopencode\u002F...`) 读取文件失败，请在安装前设置 `OPENCODE_CONFIG_DIR`：\n```bash\nOPENCODE_CONFIG_DIR=\u002Fhome\u002Fyouruser\u002F.config\u002Fopencode npx gsd-opencode --global\n```\n这可确保使用绝对路径，而不是可能在容器中无法正确展开的 `~`。\n\n---\n\n\n## 星标历史\n\n[![星标历史图表](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Frokicool_gsd-opencode_readme_059bc2fea1d6.png)](https:\u002F\u002Fwww.star-history.com\u002F#rokicool\u002Fgsd-opencode?type=date&legend=top-left)\n\n## 许可证\n\nMIT 许可证。详情请参阅 [LICENSE](LICENSE)。\n\n---\n\n\u003Cdiv align=\"center\">\n\n**OpenCode 具有潜力。GSD 使其更加可靠。**\n\n\u003C\u002Fdiv>","# gsd-opencode 快速上手指南\n\ngsd-opencode 是一个专为 **OpenCode** 设计的轻量级元提示（meta-prompting）和规格驱动开发系统。它基于 TÂCHES 的 \"Get Shit Done\" (GSD) 框架改编，旨在通过上下文工程和子代理编排，让开发者只需描述需求，AI 即可自动完成高质量的代码构建与验证，无需繁琐的企业级流程。\n\n## 环境准备\n\n在开始之前，请确保您的开发环境满足以下要求：\n\n*   **操作系统**：macOS, Windows, 或 Linux。\n*   **核心依赖**：已安装 [Node.js](https:\u002F\u002Fnodejs.org\u002F) (建议 LTS 版本) 和 `npm`。\n*   **目标平台**：已安装并配置好 **OpenCode** 编辑器\u002F环境。\n*   **网络环境**：能够访问 npm registry 及 GitHub（若下载缓慢，可配置国内镜像源）。\n\n> **💡 国内加速建议**\n> 若安装过程中遇到网络延迟，建议临时切换至国内 npm 镜像源：\n> ```bash\n> npm config set registry https:\u002F\u002Fregistry.npmmirror.com\n> ```\n\n## 安装步骤\n\n您可以通过 `npx` 直接运行，或通过 `npm` 全局安装以获得更完整的 CLI 管理功能。\n\n### 方式一：直接使用 (推荐尝试)\n\n无需预先安装，直接在终端运行最新版本的安装向导：\n\n```bash\nnpx gsd-opencode@latest\n```\n\n### 方式二：全局安装 (推荐长期使用)\n\n1.  安装包到全局环境：\n    ```bash\n    npm install gsd-opencode -g\n    ```\n\n2.  执行安装命令将 GSD 系统集成到 OpenCode：\n    ```bash\n    gsd-opencode install\n    ```\n\n3.  **验证安装**：\n    启动 OpenCode，在对话框中输入以下命令确认系统已就绪：\n    ```text\n    \u002Fgsd-help\n    ```\n\n### 非交互式安装 (适用于 Docker\u002FCI\u002F脚本)\n\n如果您需要跳过交互提示进行自动化部署：\n\n```bash\n# 全局安装到 ~\u002F.config\u002Fopencode\u002F\nnpx gsd-opencode --global\n\n# 或局部安装到当前项目的 .opencode\u002F\nnpx gsd-opencode --local\n```\n\n## 基本使用\n\n安装完成后，gsd-opencode 将作为 OpenCode 的智能层运行。您不需要编写复杂的配置文件，只需通过自然语言描述需求。\n\n### 1. 启动工作流\n\n在 OpenCode 中，直接描述您想要构建的功能。系统会自动识别意图并调用相应的 GSD 代理（如规划、执行、测试等）。\n\n**示例指令：**\n> \"帮我创建一个带有用户登录功能的 React 前端项目，使用 Tailwind CSS 样式，后端使用 Node.js Express。\"\n\n### 2. 常用控制命令\n\n在安装后，您可以使用以下斜杠命令（Slash Commands）来管理系统行为：\n\n*   **查看帮助**：\n    ```text\n    \u002Fgsd-help\n    ```\n*   **检查更新**：\n    ```text\n    \u002Fgsd-whats-new\n    ```\n*   **配置模型策略** (OpenCode 特有功能)：\n    由于 OpenCode 支持多种模型提供商，您可以手动设定不同阶段的模型策略（Simple\u002FSmart\u002FGenius）：\n    ```text\n    \u002Fgsd-set-profile\n    ```\n    *   `Simple`: 所有任务使用同一模型。\n    *   `Smart`: 区分普通任务和复杂任务使用不同模型。\n    *   `Genius`: 为规划、执行、审查分别指定不同模型。\n\n    > **注意**：更改模型配置后，建议重启 OpenCode 以使设置生效。\n\n### 3. 更新系统\n\nGSD 迭代迅速，定期运行以下命令以保持最新功能：\n\n```bash\nnpx gsd-opencode@latest\n# 或者如果已全局安装\nnpm install gsd-opencode@latest -g\ngsd-opencode install\n```\n\n---\n*现在，您可以专注于创意描述，让 gsd-opencode 为您处理复杂的工程实现细节。*","独立开发者小明需要在周末快速构建一个带有用户认证和数据看板的全栈 MVP 原型，但他不想陷入繁琐的项目配置和上下文管理中。\n\n### 没有 gsd-opencode 时\n- **上下文断裂**：手动向 AI 反复粘贴代码片段和需求文档，导致 AI 经常“失忆”，生成的代码与现有架构冲突。\n- **流程冗余**：为了保持逻辑清晰，不得不手动编写详细的技术规格书和任务分解列表，耗费大量编码前的准备时间。\n- **执行分散**：需要频繁切换不同提示词来分别处理规划、编码和测试，缺乏统一的调度机制，容易遗漏关键步骤。\n- **过度工程化**：尝试引入大型敏捷管理流程（如故事点估算、冲刺会议模拟），对于单人开发而言显得笨重且低效。\n\n### 使用 gsd-opencode 后\n- **智能上下文工程**：gsd-opencode 自动管理系统状态和 XML 提示格式，让 AI 始终掌握项目全貌，生成的代码直接可运行且风格统一。\n- **规格驱动开发**：只需输入核心想法，工具自动将其转化为具体执行规范并驱动子代理（Subagents）完成从规划到落地的全过程。\n- **自动化编排**：内置的子代理协调机制自动分发任务，无缝衔接需求分析、代码实现与自我验证环节，真正实现“说完即做完”。\n- **轻量高效**：去除了企业级的繁文缛节，专注于创意落地，让单人开发者也能像拥有完整工程团队一样高效产出。\n\ngsd-opencode 将复杂的提示词工程和任务编排隐藏在幕后，让开发者只需关注“做什么”，剩下的全部交给系统自动搞定。","https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Frokicool_gsd-opencode_7291cd6c.jpg","rokicool","Roman Kiprin","https:\u002F\u002Foss.gittoolsai.com\u002Favatars\u002Frokicool_712ccb5e.png",null,"Chicago, IL","https:\u002F\u002Fgithub.com\u002Frokicool",[80],{"name":81,"color":82,"percentage":83},"JavaScript","#f1e05a",100,672,52,"2026-04-13T13:12:56","Linux, macOS, Windows","未说明",{"notes":90,"python":88,"dependencies":91},"该工具是基于 Node.js 的命令行工具，需通过 npx 或 npm 安装。主要依赖 OpenCode 环境运行，用于增强 Claude Code 的提示工程和上下文管理能力。安装后需在 OpenCode 中重启以生效配置。支持全局和本地两种安装模式。",[92,93],"Node.js\u002Fnpm","OpenCode",[35,13,52],"2026-03-27T02:49:30.150509","2026-04-14T04:24:06.344289",[],[99,104,109,114,119,124,129,134,139,144,149,154,159,164,169,174,179,184,189,194],{"id":100,"version":101,"summary_zh":102,"released_at":103},247229,"v1.33.3"," # gsd-opencode v1.33.3\n\n 自动发布自提交 96bad30f84994c3623c63f50e2651ba73d7c3151。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.33.3\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.33.3.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.33.3.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-04-13T02:19:54",{"id":105,"version":106,"summary_zh":107,"released_at":108},247230,"v1.33.2"," # gsd-opencode v1.33.2\n\n 自动发布，基于提交 699eb76be551e446125b31b932082975ddf472fc。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.33.2\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.33.2.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.33.2.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-04-13T01:08:59",{"id":110,"version":111,"summary_zh":112,"released_at":113},247231,"v1.33.1"," # gsd-opencode v1.33.1\n\n 由提交 a4b25212fdc045f7eb140fddf8cb2be1b17d1816 自动发布。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.33.1\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.33.1.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.33.1.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备完毕\"\n","2026-04-08T01:11:41",{"id":115,"version":116,"summary_zh":117,"released_at":118},247232,"v1.33.0"," # gsd-opencode v1.33.0\n\n 自动发布，基于提交 e9fae8224595d9211bdaab60dadb6a7e95a172e6。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.33.0\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.33.0.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.33.0.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-04-07T01:40:59",{"id":120,"version":121,"summary_zh":122,"released_at":123},247233,"v1.30.0"," # gsd-opencode v1.30.0\n\n 自动发布，基于提交 c8ca847b994902de9b2b0c748a53cb44a0a93806。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.30.0\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.30.0.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.30.0.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-03-31T22:19:47",{"id":125,"version":126,"summary_zh":127,"released_at":128},247234,"v1.22.1"," # gsd-opencode v1.22.1\n\n 自动化发布，基于提交 d23787c1b8695294011b0edc9766b2c384fe4a26。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.22.1\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.22.1.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.22.1.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-03-10T18:10:37",{"id":130,"version":131,"summary_zh":132,"released_at":133},247235,"v1.22.0"," # gsd-opencode v1.22.0\n\n 自动化发布，基于提交 ca0103013c78c6db4c8a8693d31c1c4f2e06c754。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.22.0\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.22.0.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.22.0.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备完毕\"\n","2026-03-09T03:08:13",{"id":135,"version":136,"summary_zh":137,"released_at":138},247236,"v1.20.4"," # gsd-opencode v1.20.4\n\n 自动发布，基于提交 4527186e3fa24630b76bceb99fa962673c23fd43。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.20.4\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.20.4.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.20.4.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-03-05T13:11:25",{"id":140,"version":141,"summary_zh":142,"released_at":143},247237,"v1.20.3"," # gsd-opencode v1.20.3\n\n 自动发布自提交 a7ae7111e009dcad5747bfb3fcae7a5209292ad9。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.20.3\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.20.3.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.20.3.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-03-03T23:14:36",{"id":145,"version":146,"summary_zh":147,"released_at":148},247238,"v1.20.2"," # gsd-opencode v1.20.2\n\n 自动发布自提交 b1b6856c7b3ce2ac3527fb69f3217afff167839c。\n\n ## 安装\n\n npm install -g gsd-opencode@v1.20.2\n\n ## 下载\n\n 请选择符合您需求的资源：\n - gsd-opencode-v1.20.2.tgz - 用于手动安装的 NPM 包\n - gsd-opencode-v1.20.2.tgz.sha256 - NPM 包的 SHA256 校验和\n - release-checksums.txt - 所有文件的完整校验和列表\n\n ## 验证\n\n 请使用提供的 SHA256 校验和验证下载文件的完整性。\n\n ---\n\n 文件结束\n\n  # 如果有变更日志，则添加\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## 变更日志\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ 发布说明已准备\"\n","2026-02-28T05:38:25",{"id":150,"version":151,"summary_zh":152,"released_at":153},247239,"v1.20.1"," # gsd-opencode v1.20.1\n\n Automated release from commit 69aebda8ccbfd861fc98ef3393ffecdb9666f027.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.20.1\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.20.1.tgz - NPM package for manual installation\n - gsd-opencode-v1.20.1.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n  # Add changelog if available\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ Release notes prepared\"\n","2026-02-28T04:20:57",{"id":155,"version":156,"summary_zh":157,"released_at":158},247240,"v1.20.0"," # gsd-opencode v1.20.0\n\n Automated release from commit 2728459486e61b9866136a96e6d06f542cf96d6d.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.20.0\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.20.0.tgz - NPM package for manual installation\n - gsd-opencode-v1.20.0.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n  # Add changelog if available\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ Release notes prepared\"\n","2026-02-26T02:33:20",{"id":160,"version":161,"summary_zh":162,"released_at":163},247241,"v1.10.2"," # gsd-opencode v1.10.2\n\n Automated release from commit fe901f4d8febde4c03c798fc6b96127b3a321236.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.10.2\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.10.2.tgz - NPM package for manual installation\n - gsd-opencode-v1.10.2.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n  # Add changelog if available\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ Release notes prepared\"\n","2026-02-18T02:45:58",{"id":165,"version":166,"summary_zh":167,"released_at":168},247242,"v1.10.1"," # gsd-opencode v1.10.1\n\n Automated release from commit 6dbe0e9ab6ec7a08a005a07049a643c166756856.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.10.1\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.10.1.tgz - NPM package for manual installation\n - gsd-opencode-v1.10.1.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n  # Add changelog if available\n  if [ -f \".\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002Fdist\u002FCHANGELOG.md >> release-notes.md\n  elif [ -f \".\u002Frelease-artifacts\u002FCHANGELOG-release.md\" ]; then\n    echo \"\" >> release-notes.md\n    echo \"## Changelog\" >> release-notes.md\n    echo \"\" >> release-notes.md\n    cat .\u002Frelease-artifacts\u002FCHANGELOG-release.md >> release-notes.md\n  fi\n\n  echo \"✓ Release notes prepared\"\n","2026-02-14T01:27:03",{"id":170,"version":171,"summary_zh":172,"released_at":173},247243,"v1.10.0","## Summary\r\n- Implemented complete Node.js CLI architecture with 7 core commands (install, update, check, config, list, repair, uninstall)\r\n- Added comprehensive service layer including BackupManager, HealthChecker, MigrationService, ManifestManager, and RepairService\r\n- Migrated command documentation from command\u002F to commands\u002F directory structure with automatic migration support\r\n- Introduced safety-first uninstallation with manifest-based file tracking and namespace isolation\r\n- Built extensive test suite with unit, integration, and service-level coverage using vitest\r\n## Additional important details\r\n- Commits: 108 commits since v1.9.2\r\n- Files changed: 101 files with +16,707 insertions, -48 deletions\r\n- Breaking changes: Directory structure renamed from command\u002Fgsd\u002F to commands\u002Fgsd\u002F with automatic migration path for existing installations\r\n- New services: 11 service modules, 7 command handlers, 5 utility modules, and 2 entry point scripts\r\n- Test coverage: 16 test files covering commands, services, utilities, and integration scenarios\r\n- CI\u002FCD: Enhanced GitHub Actions workflow with forbidden strings validation\r\n- Documentation: Updated CHANGELOG.md, README.md, and added DISTRIBUTION-MANAGER.md","2026-02-14T00:34:14",{"id":175,"version":176,"summary_zh":177,"released_at":178},247244,"v1.9.2"," # gsd-opencode v1.9.2\n\n Automated release from commit e80f0dee9b812d5c288ffbb95069fa527e033dd8.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.9.2\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.9.2.tgz - NPM package for manual installation\n - gsd-opencode-v1.9.2.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n # Add changelog if available\n if [ -f \".\u002Frelease-artifacts\u002FCHANGELOG.md\" ]; then\n   echo \"\" >> release-notes.md\n   echo \"## Changelog\" >> release-notes.md\n   echo \"\" >> release-notes.md\n   cat .\u002Frelease-artifacts\u002FCHANGELOG.md >> release-notes.md\n fi\n\n  echo \"✓ Release notes prepared\"\n","2026-01-25T21:31:49",{"id":180,"version":181,"summary_zh":182,"released_at":183},247245,"v1.9.1"," # gsd-opencode v1.9.1\n\n Automated release from commit 5519bab72f9e275a2ee83412f19f71bd5087c735.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.9.1\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.9.1.tgz - NPM package for manual installation\n - gsd-opencode-v1.9.1.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n # Add changelog if available\n if [ -f \".\u002Frelease-artifacts\u002FCHANGELOG.md\" ]; then\n   echo \"\" >> release-notes.md\n   echo \"## Changelog\" >> release-notes.md\n   echo \"\" >> release-notes.md\n   cat .\u002Frelease-artifacts\u002FCHANGELOG.md >> release-notes.md\n fi\n\n  echo \"✓ Release notes prepared\"\n","2026-01-24T01:13:35",{"id":185,"version":186,"summary_zh":187,"released_at":188},247246,"v1.9.0"," # gsd-opencode v1.9.0\n\n Automated release from commit 2dcfdb8ab5edf20b63b9b7eea6a9772dc25605c6.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.9.0\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.9.0.tgz - NPM package for manual installation\n - gsd-opencode-v1.9.0.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n # Add changelog if available\n if [ -f \".\u002Frelease-artifacts\u002FCHANGELOG.md\" ]; then\n   echo \"\" >> release-notes.md\n   echo \"## Changelog\" >> release-notes.md\n   echo \"\" >> release-notes.md\n   cat .\u002Frelease-artifacts\u002FCHANGELOG.md >> release-notes.md\n fi\n\n  echo \"✓ Release notes prepared\"\n","2026-01-22T07:37:03",{"id":190,"version":191,"summary_zh":192,"released_at":193},247247,"v1.6.1"," # gsd-opencode v1.6.1\n\n Automated release from commit d1c8da40982d7e85e36373acf627cdf729ebf65d.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.6.1\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.6.1.tgz - NPM package for manual installation\n - gsd-opencode-v1.6.1.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n # Add changelog if available\n if [ -f \".\u002Frelease-artifacts\u002FCHANGELOG.md\" ]; then\n   echo \"\" >> release-notes.md\n   echo \"## Changelog\" >> release-notes.md\n   echo \"\" >> release-notes.md\n   cat .\u002Frelease-artifacts\u002FCHANGELOG.md >> release-notes.md\n fi\n\n  echo \"✓ Release notes prepared\"\n","2026-01-19T23:02:21",{"id":195,"version":196,"summary_zh":197,"released_at":198},247248,"v1.6.0"," # gsd-opencode v1.6.0\n\n Automated release from commit 375026f3e3b897b9a91ff367fc18d9d2580650d7.\n\n ## Installation\n\n npm install -g gsd-opencode@v1.6.0\n\n ## Download\n\n Choose the asset that matches your needs:\n - gsd-opencode-v1.6.0.tgz - NPM package for manual installation\n - gsd-opencode-v1.6.0.tgz.sha256 - SHA256 checksum for NPM package\n - release-checksums.txt - Complete checksums for all files\n\n ## Verification\n\n Verify the integrity of downloaded files using the provided SHA256 checksums.\n\n ---\n\n EOF\n\n # Add changelog if available\n if [ -f \".\u002Frelease-artifacts\u002FCHANGELOG.md\" ]; then\n   echo \"\" >> release-notes.md\n   echo \"## Changelog\" >> release-notes.md\n   echo \"\" >> release-notes.md\n   cat .\u002Frelease-artifacts\u002FCHANGELOG.md >> release-notes.md\n fi\n\n  echo \"✓ Release notes prepared\"\n","2026-01-19T22:37:45"]