gsd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Get Shit Done (GSD) - Project Management System

Get Shit Done (GSD) - 项目管理系统

A comprehensive project management system designed for solo developers working with Claude AI agents. GSD provides structured workflows for project initialization, planning, execution, verification, and debugging.
这是一款专为使用Claude AI Agent的独立开发者设计的综合性项目管理系统。GSD为项目初始化、规划、执行、验证和调试提供了结构化工作流。

Overview

概述

GSD is a modular agent-based system that transforms project ideas into shipped software through:
  1. Deep questioning - Extract user vision and requirements
  2. Domain research - Discover standard stacks and patterns
  3. Roadmap creation - Break requirements into phases
  4. Phase planning - Create executable plans with verification
  5. Execution - Implement plans with atomic commits
  6. Verification - Ensure goals are achieved, not just tasks done
  7. Debugging - Systematic investigation of issues
GSD是一个基于Agent的模块化系统,通过以下步骤将项目想法转化为可交付的软件:
  1. 深度提问 - 挖掘用户愿景与需求
  2. 领域调研 - 探索标准技术栈与模式
  3. 路线图创建 - 将需求拆解为多个阶段
  4. 阶段规划 - 制定带有验证机制的可执行计划
  5. 执行落地 - 通过原子提交实现计划
  6. 验证确认 - 确保目标达成,而非仅完成任务
  7. 问题调试 - 系统化排查问题

Core Philosophy

核心理念

  • Solo Developer + Claude Workflow - No teams, no stakeholders, no ceremonies
  • Plans are Prompts - PLAN.md files ARE the execution prompts, not documents
  • Goal-Backward Planning - Start from what must be TRUE, derive what to build
  • Atomic Commits - Each task commits independently for clean history
  • Quality Over Speed - Stop before context degrades (~50% usage)
  • Ship Fast - Plan → Execute → Ship → Learn → Repeat
  • 独立开发者 + Claude 工作流 - 无需团队、无需利益相关者、无需繁琐流程
  • 计划即提示词 - PLAN.md文件本身就是执行提示词,而非单纯文档
  • 目标倒推规划 - 从必须实现的目标出发,推导需要构建的内容
  • 原子提交 - 每个任务独立提交,保持清晰的版本历史
  • 质量优先于速度 - 在上下文信息质量下降前停止(约50%使用阈值)
  • 快速交付 - 规划→执行→交付→学习→重复

When to Use GSD

适用场景

Use GSD when you need to:
  • Initialize a new software project
  • Plan and execute development phases
  • Map an existing codebase
  • Debug issues systematically
  • Verify phase completion
  • Track project progress and state
当你需要以下操作时,可使用GSD:
  • 初始化新软件项目
  • 规划并执行开发阶段
  • 梳理现有代码库
  • 系统化调试问题
  • 验证阶段完成情况
  • 跟踪项目进度与状态

Quick Start Commands

快速开始命令

New Project

新项目初始化

bash
/gsd:new-project
Initializes a new project with questioning → research → requirements → roadmap flow.
bash
/gsd:new-project
通过提问→调研→需求梳理→路线图生成的流程初始化新项目。

Plan a Phase

规划阶段

bash
/gsd:plan-phase [phase-number]
Creates detailed execution plans with research and verification.
bash
/gsd:plan-phase [phase-number]
结合调研与验证机制,创建详细的执行计划。

Execute a Phase

执行阶段

bash
/gsd:execute-phase [phase-number]
Executes all plans in a phase with parallel execution support.
bash
/gsd:execute-phase [phase-number]
执行某一阶段的所有计划,支持并行执行。

Map Codebase

代码库梳理

bash
/gsd:map-codebase [optional-focus-area]
Analyzes existing codebase with parallel mapper agents.
bash
/gsd:map-codebase [optional-focus-area]
通过并行映射Agent分析现有代码库。

Debug Issues

问题调试

bash
/gsd:debug [issue-description]
Systematic debugging using scientific method and hypothesis testing.
bash
/gsd:debug [issue-description]
采用科学方法与假设测试进行系统化调试。

Verify Phase

阶段验证

bash
/gsd:verify-work [phase-number]
Goal-backward verification of phase completion.
bash
/gsd:verify-work [phase-number]
通过目标倒推的方式验证阶段完成情况。

Check Progress

查看进度

bash
/gsd:progress
Shows current project position, completed phases, and next steps.
bash
/gsd:progress
显示当前项目位置、已完成阶段及下一步计划。

Agent Skills

Agent技能

GSD includes specialized agents for different tasks:
  • gsd-codebase-mapper - Explores and documents codebase structure
  • gsd-planner - Creates executable phase plans
  • gsd-executor - Executes plans with atomic commits
  • gsd-debugger - Investigates bugs systematically
  • gsd-verifier - Verifies goal achievement
  • gsd-research-synthesizer - Synthesizes research outputs
  • gsd-roadmapper - Creates project roadmaps
  • gsd-phase-researcher - Researches phase implementation
  • gsd-project-researcher - Researches domain ecosystem
  • gsd-integration-checker - Verifies integrations work
  • gsd-plan-checker - Validates plan quality
GSD包含针对不同任务的专用Agent:
  • gsd-codebase-mapper - 探索并记录代码库结构
  • gsd-planner - 创建可执行的阶段计划
  • gsd-executor - 通过原子提交执行计划
  • gsd-debugger - 系统化排查Bug
  • gsd-verifier - 验证目标达成情况
  • gsd-research-synthesizer - 整合调研输出内容
  • gsd-roadmapper - 创建项目路线图
  • gsd-phase-researcher - 调研阶段实现方案
  • gsd-project-researcher - 调研领域生态系统
  • gsd-integration-checker - 验证集成功能可用性
  • gsd-plan-checker - 验证计划质量

Command Skills

命令技能

GSD provides commands for orchestrating the entire project lifecycle:
  • gsd:new-project - Initialize new project
  • gsd:map-codebase - Map existing codebase
  • gsd:plan-phase - Plan a phase
  • gsd:execute-phase - Execute a phase
  • gsd:verify-work - Verify phase completion
  • gsd:debug - Debug issues
  • gsd:discuss-phase - Gather phase context
  • gsd:research-phase - Research phase implementation
  • gsd:complete-milestone - Complete milestone
  • gsd:audit-milestone - Audit milestone
  • gsd:add-phase - Add new phase
  • gsd:insert-phase - Insert phase
  • gsd:remove-phase - Remove phase
  • gsd:add-todo - Add todo item
  • gsd:check-todos - Check todos
  • gsd:plan-milestone-gaps - Plan milestone gaps
  • gsd:pause-work - Pause work
  • gsd:resume-work - Resume work
  • gsd:update - Update project state
  • gsd:whats-new - Show what's new
GSD提供用于编排整个项目生命周期的命令:
  • gsd:new-project - 初始化新项目
  • gsd:map-codebase - 梳理现有代码库
  • gsd:plan-phase - 规划阶段
  • gsd:execute-phase - 执行阶段
  • gsd:verify-work - 验证阶段完成情况
  • gsd:debug - 调试问题
  • gsd:discuss-phase - 收集阶段上下文信息
  • gsd:research-phase - 调研阶段实现方案
  • gsd:complete-milestone - 完成里程碑
  • gsd:audit-milestone - 审核里程碑
  • gsd:add-phase - 添加新阶段
  • gsd:insert-phase - 插入阶段
  • gsd:remove-phase - 删除阶段
  • gsd:add-todo - 添加待办事项
  • gsd:check-todos - 查看待办事项
  • gsd:plan-milestone-gaps - 规划里程碑缺口
  • gsd:pause-work - 暂停工作
  • gsd:resume-work - 恢复工作
  • gsd:update - 更新项目状态
  • gsd:whats-new - 查看更新内容

Workflow Skills

工作流技能

Detailed workflow definitions for complex operations:
  • discovery-phase - Phase discovery workflow
  • execute-phase - Phase execution workflow
  • diagnose-issues - Parallel UAT diagnosis
  • map-codebase - Codebase mapping workflow
  • discuss-phase - Phase discussion workflow
  • verify-phase - Phase verification workflow
  • verify-work - Work verification workflow
  • transition - Phase transition workflow
  • resume-project - Project resumption workflow
针对复杂操作的详细工作流定义:
  • discovery-phase - 阶段探索工作流
  • execute-phase - 阶段执行工作流
  • diagnose-issues - 并行用户验收测试(UAT)诊断
  • map-codebase - 代码库梳理工作流
  • discuss-phase - 阶段讨论工作流
  • verify-phase - 阶段验证工作流
  • verify-work - 工作成果验证工作流
  • transition - 阶段过渡工作流
  • resume-project - 项目恢复工作流

Reference Skills

参考技能

Reference documents for best practices and guidelines:
  • questioning - Deep questioning techniques
  • tdd - Test-driven development patterns
  • ui-brand - UI/UX guidelines
  • verification-patterns - Verification methodologies
  • git-integration - Git workflow patterns
  • checkpoints - Checkpoint handling
  • continuation-format - Continuation format specification
包含最佳实践与指南的参考文档:
  • questioning - 深度提问技巧
  • tdd - 测试驱动开发模式
  • ui-brand - UI/UX设计指南
  • verification-patterns - 验证方法论
  • git-integration - Git工作流模式
  • checkpoints - 检查点处理方式
  • continuation-format - 续期格式规范

Project Structure

项目结构

GSD creates a
.planning/
directory with:
.planning/
├── PROJECT.md           # Project context and vision
├── config.json          # Workflow preferences
├── REQUIREMENTS.md      # Scoped requirements
├── ROADMAP.md          # Phase structure
├── STATE.md            # Project memory and state
├── research/            # Domain research outputs
├── phases/              # Phase-specific artifacts
│   ├── XX-name/
│   │   ├── XX-PLAN.md
│   │   ├── XX-SUMMARY.md
│   │   ├── XX-CONTEXT.md
│   │   ├── XX-RESEARCH.md
│   │   ├── XX-VERIFICATION.md
│   │   └── XX-UAT.md
└── codebase/            # Codebase analysis
    ├── STACK.md
    ├── ARCHITECTURE.md
    ├── STRUCTURE.md
    ├── CONVENTIONS.md
    ├── TESTING.md
    ├── INTEGRATIONS.md
    └── CONCERNS.md
GSD会创建一个
.planning/
目录,结构如下:
.planning/
├── PROJECT.md           # 项目上下文与愿景
├── config.json          # 工作流偏好设置
├── REQUIREMENTS.md      # 已梳理的需求
├── ROADMAP.md          # 阶段结构
├── STATE.md            # 项目记忆与状态
├── research/            # 领域调研输出
├── phases/              # 阶段专属工件
│   ├── XX-name/
│   │   ├── XX-PLAN.md
│   │   ├── XX-SUMMARY.md
│   │   ├── XX-CONTEXT.md
│   │   ├── XX-RESEARCH.md
│   │   ├── XX-VERIFICATION.md
│   │   └── XX-UAT.md
└── codebase/            # 代码库分析结果
    ├── STACK.md
    ├── ARCHITECTURE.md
    ├── STRUCTURE.md
    ├── CONVENTIONS.md
    ├── TESTING.md
    ├── INTEGRATIONS.md
    └── CONCERNS.md

Key Concepts

核心概念

Goal-Backward Planning

目标倒推规划

Instead of asking "what should we build?", ask "what must be TRUE for the goal to be achieved?"
Forward: "Build authentication system" → task list Goal-Backward: "Users can securely access accounts" → derive what must exist
不要问“我们应该构建什么?”,而是问“要实现目标,哪些条件必须成立?”
正向思维: “构建认证系统” → 任务列表 目标倒推: “用户可以安全访问账户” → 推导必须存在的功能

Atomic Commits

原子提交

Each task commits independently with descriptive messages:
bash
feat(01-01): implement user login
fix(01-02): fix password validation
test(01-03): add login tests
每个任务独立提交,并附带描述性信息:
bash
feat(01-01): implement user login
fix(01-02): fix password validation
test(01-03): add login tests

Context Budgeting

上下文预算

Plans complete within ~50% context usage to maintain quality:
  • 0-30%: PEAK quality
  • 30-50%: GOOD quality
  • 50-70%: DEGRADING quality
  • 70%+: POOR quality (avoid)
计划需在上下文信息质量下降前完成(约50%使用阈值):
  • 0-30%:最佳质量
  • 30-50%:良好质量
  • 50-70%:质量下降
  • 70%+:质量极差(需避免)

Wave-Based Execution

波浪式执行

Plans are grouped into waves for parallel execution:
  • Wave 1: Independent plans (no dependencies)
  • Wave 2: Plans depending only on Wave 1
  • Wave 3: Plans depending on Wave 2, etc.
计划被分组为多个波浪进行并行执行:
  • 第一波: 独立计划(无依赖)
  • 第二波: 仅依赖第一波的计划
  • 第三波: 依赖第二波的计划,以此类推

Anti-Patterns to Avoid

需避免的反模式

  • Enterprise PM Theater - No RACI matrices, sprint ceremonies, stakeholder management
  • Horizontal Layers - Don't group by "all models, then all APIs" - group by features
  • Vague Success Criteria - "Authentication works" → "User can log in with email/password"
  • Time Estimates - Never estimate in hours/days/weeks
  • Task Completion ≠ Goal Achievement - Verify outcomes, not just task completion
  • 企业级项目管理形式主义 - 无需RACI矩阵、冲刺流程、利益相关者管理
  • 横向分层开发 - 不要按“所有模型→所有API”分组,应按功能分组
  • 模糊的成功标准 - 避免“认证功能可用”,应明确为“用户可通过邮箱/密码登录”
  • 时间估算 - 永远不要按小时/天/周估算
  • 任务完成≠目标达成 - 验证成果,而非仅确认任务完成

Getting Help

获取帮助

Each agent, command, and workflow has its own SKILL.md with detailed instructions. Use:
  • @skills/gsd/agents/
    for agent-specific help
  • @skills/gsd/commands/
    for command-specific help
  • @skills/gsd/workflows/
    for workflow-specific help
  • @skills/gsd/references/
    for reference documentation
每个Agent、命令和工作流都有对应的SKILL.md文档,包含详细说明。可通过以下路径访问:
  • @skills/gsd/agents/
    获取Agent专属帮助
  • @skills/gsd/commands/
    获取命令专属帮助
  • @skills/gsd/workflows/
    获取工作流专属帮助
  • @skills/gsd/references/
    获取参考文档

Version

版本

GSD Version: 1.0.0 Last Updated: 2026-01-19
GSD版本:1.0.0 最后更新:2026-01-19