OpenSpec vs Get Shit Done

文件: OpenSpec/src/core/schemas/base.schema.ts

export const RequirementSchema = z.object({
  text: z.string()
    .min(1, VALIDATION_MESSAGES.REQUIREMENT_EMPTY)
    .refine(
      (text) => text.includes('SHALL') || text.includes('MUST'),
      VALIDATION_MESSAGES.REQUIREMENT_NO_SHALL
    ),
  scenarios: z.array(ScenarioSchema)
    .min(1, VALIDATION_MESSAGES.REQUIREMENT_NO_SCENARIOS),
});

解读: OpenSpec 用 Zod 的 refine() 强制每个 Requirement 必须包含 "SHALL" 或 "MUST"，这是 RFC 2119 规范风格的强制要求。

文件: OpenSpec/src/core/artifact-graph/schema.ts

function validateNoCycles(artifacts: Artifact[]): void {
  const artifactMap = new Map(artifacts.map(a => [a.id, a]));
  const visited = new Set<string>();
  const inStack = new Set<string>();
  const parent = new Map<string, string>();

  function dfs(id: string): string | null {
    visited.add(id);
    inStack.add(id);
    for (const dep of artifactMap.get(id).requires) {
      if (!visited.has(dep)) {
        parent.set(dep, id);
        const cycle = dfs(dep);
        if (cycle) return cycle;
      } else if (inStack.has(dep)) {
        // Found cycle — reconstruct full path
        const cyclePath = [dep];
        let current = id;
        while (current !== dep) {
          cyclePath.unshift(current);
          current = parent.get(current);
        }
        cyclePath.unshift(dep);
        return cyclePath.join(' → ');
      }
    }
    inStack.delete(id);
    return null;
  }
}

解读: OpenSpec 的 Artifact Graph 支持声明式依赖，用 DFS 检测循环依赖并报告完整路径。这是一种声明式编程思想。

文件: OpenSpec/src/core/config.ts

export const AI_TOOLS: AIToolOption[] = [
  { name: 'Amazon Q Developer', value: 'amazon-q', available: true, successLabel: 'Amazon Q Developer', skillsDir: '.amazonq' },
  { name: 'Antigravity', value: 'antigravity', available: true, successLabel: 'Antigravity', skillsDir: '.agent' },
  { name: 'Claude Code', value: 'claude', available: true, successLabel: 'Claude Code', skillsDir: '.claude' },
  { name: 'Cursor', value: 'cursor', available: true, successLabel: 'Cursor', skillsDir: '.cursor' },
  { name: 'Gemini CLI', value: 'gemini', available: true, successLabel: 'Gemini CLI', skillsDir: '.gemini' },
  { name: 'GitHub Copilot', value: 'github-copilot', available: true, successLabel: 'GitHub Copilot', skillsDir: '.github' },
  { name: 'OpenCode', value: 'opencode', available: true, successLabel: 'OpenCode', skillsDir: '.opencode' },
  { name: 'Windsurf', value: 'windsurf', available: true, successLabel: 'Windsurf', skillsDir: '.windsurf' },
  // ... 17 more tools
];

文件: get-shit-done/get-shit-done/references/model-profiles.md

| Agent | quality | balanced | budget | inherit |
|-------|---------|----------|--------|---------|
| gsd-planner | opus | opus | sonnet | inherit |
| gsd-executor | opus | sonnet | sonnet | inherit |
| gsd-phase-researcher | opus | sonnet | haiku | inherit |
| gsd-verifier | sonnet | sonnet | haiku | inherit |
| gsd-plan-checker | sonnet | sonnet | haiku | inherit |

解读: GSD 有精细的模型分配策略，不同 Agent 根据任务复杂度使用不同档位模型。planning 类用 Opus，执行类用 Sonnet，验证类可用 Haiku。

文件: get-shit-done/get-shit-done/workflows/discuss-phase.md

<purpose>
Extract implementation decisions that downstream agents need. 
Analyze the phase to identify gray areas, let the user choose 
what to discuss, then deep-dive each selected area until satisfied.
You are a thinking partner, not an interviewer. The user is the 
visionary — you are the builder.
</purpose>

<scope_guardrail>
CRITICAL: No scope creep.
The phase boundary comes from ROADMAP.md and is FIXED. 
Discussion clarifies HOW to implement what's scoped, never WHETHER 
to add new capabilities.
</scope_guardrail>

解读: discuss-phase 是 GSD 的用户交互入口，强调"用户是愿景者，AI 是建造者"。严格防止范围蔓延（scope creep），所有决策写入 CONTEXT.md 供后续 planner 使用。

文件: get-shit-done/get-shit-done/bin/gsd-tools.cjs

// 核心子命令列表（部分）:
# Atomic Commands:
#   state load | state json | state update | state get | state patch
#   resolve-model | find-phase | commit | verify-summary
#   generate-slug | current-timestamp | list-todos
# Phase Operations:
#   phase next-decimal | phase add | phase insert | phase remove | phase complete
# Roadmap Operations:
#   roadmap get-phase | roadmap analyze | roadmap update-plan-progress
# Verification Suite:
#   verify plan-structure | verify phase-completeness | verify references
#   verify commits | verify artifacts | verify key-links
# Template Fill:
#   template fill summary | template fill plan | template fill verification

解读: gsd-tools.cjs 是 GSD 的瑞士军刀，60+ 子命令覆盖状态管理、phase 操作、roadmap 分析、验证套件和模板填充。比 OpenSpec 的 CLI 命令更细粒度。

文件: get-shit-done/hooks/gsd-context-monitor.js

// Thresholds:
const WARNING_THRESHOLD = 35;   // remaining_percentage <= 35%
const CRITICAL_THRESHOLD = 25; // remaining_percentage <= 25%
// Debounce: 5 tool uses between warnings to avoid spam

// 检查 /tmp/claude-ctx-{session_id}.json 的上下文使用情况
// WARNING  → Agent 应该结束当前任务
// CRITICAL → Agent 立即停止并保存状态
const metrics = JSON.parse(fs.readFileSync(metricsPath, 'utf8'));
const remaining = metrics.remaining_percentage;

解读: GSD 有专门的上下文窗口监控 hook，通过 PostToolUse/AfterTool hook 在每次工具调用后检查上下文剩余量，防止上下文耗尽导致质量下降。

文件: get-shit-done/bin/install.js

// 工具名映射（Claude Code → 各运行时）
const claudeToGeminiTools = {
  Read: 'read_file',
  Write: 'write_file',
  Edit: 'replace',
  Bash: 'run_shell_command',
  Glob: 'glob',
  Grep: 'search_file_content',
  WebSearch: 'google_web_search',
  WebFetch: 'web_fetch',
};

const claudeToCopilotTools = {
  Read: 'read',
  Write: 'edit',
  Bash: 'execute',
  Grep: 'search',
  Task: 'agent',
};

解读: install.js 包含完整的跨运行时工具名映射系统，将 Claude Code 的工具名转换为 Gemini、Copilot、Codex 等各自对应的工具名。这使得 GSD 能在 6 种不同运行时上运行相同的 workflow 文件。