1bfadec2d0
* fix(#1921): preserve verify-work state across gap-closure + defer follow-ups Resuming /gsd:verify-work after /gsd:execute-phase --gaps-only lost the verification state: UAT ## Gaps still read status: failed even after their fix plans executed, so verify-work re-diagnosed them as fresh blockers, spawned a new gap plan, and reported only the new plan verified. A new state contract links each gap to its fix plan so fixed gaps are recognized. - verify-work.md gap YAML: stable gap_id (G-{phase}-{N}) per gap. - plan_gap_closure planner prompt: each *-PLAN.md tags the gap_ids it addresses in its frontmatter (gap_closure: true, gap_ids: [...]). - new reconcile_gaps step (run at resume_from_file entry): marks a gap status: resolved when its plan has a matching *-SUMMARY.md — fixed gaps are not re-diagnosed and do not spawn new gap plans; a re-reported break is treated as a fresh regression with a new gap_id. - deferred-follow-up branch: a future-work idea (signals: 'later', 'next version', 'out of scope', ...) is captured to UAT ## Deferred Follow-Ups instead of becoming a blocking gap/plan. - workflow-size baseline recaptured (verify-work LARGE tier, 38221/61440). Closes #1921 * docs(#1921): backfill changeset pr 2025 * fix(#1921): balance <step> tags in verify-work.md via 4-backtick outer fence The plan_gap_closure step nested a ```yaml example inside a ``` block; same-length fences made stripFencedCode close the outer block early, swallowing the step's </step> (14 opens / 13 closes). Widen the outer fence to 4 backticks so the nested yaml is contained. Regenerate golden fixtures + size baselines. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
GSD Core
Git. Ship. Done.
English · Português · 简体中文 · 日本語 · 한국어
A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.
What is GSD Core
GSD Core is a context-engineering and spec-driven development framework that drives AI coding agents (Claude Code, Codex, Antigravity CLI, Kimi CLI, Copilot, Cursor, and more) through a disciplined phase loop. It solves context rot — the quality degradation that accumulates as an AI fills its context window — by running all heavy research, planning, and execution work in fresh-context subagents while keeping your main session lean.
How it works
Each milestone repeats the same five-step loop, one phase at a time:
- Discuss — capture implementation decisions before anything is planned
- Plan — research, decompose, and verify the plan fits a fresh context window
- Execute — run plans in parallel waves; each executor starts with a clean 200k-token context
- Verify — walk through what was built; diagnose and fix before declaring done
- Ship — create the PR, archive the phase, repeat for the next one
Quickstart
npx @opengsd/gsd-core@latest
The installer prompts for your runtime (Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more) and whether to install globally or locally. The installer is required for cross-runtime compatibility — do not copy files from agents/ or commands/ directly.
On another runtime or without Node.js? See Install on your runtime.
Once installed, start your first project:
/gsd-new-project
New here? Follow Your first project for a guided walkthrough from install to first shipped phase.
Documentation
Tutorials — learning by doing:
How-to guides — task-focused recipes:
Reference — authoritative facts:
Explanation — concepts and design decisions:
Full index: docs/README.md. Other languages: 日本語 · 한국어 · Português · 简体中文.
Why it works
Most AI-coding setups fail at scale because context bloat silently degrades output quality, there is no shared memory between sessions, and nothing verifies that code actually works. GSD Core solves all three: heavy work runs in fresh subagents, structured artifacts like STATE.md and CONTEXT.md survive session boundaries, and the verify step walks through what was built and generates fix plans before a phase is declared done. See docs/explanation/context-engineering.md for the full reasoning.
Troubleshooting? See docs/how-to/recover-and-troubleshoot.md.
Community
| Project | Platform |
|---|---|
| gsd-opencode | Original OpenCode port |
| Discord | Community support |
Star History
License
MIT License. See LICENSE for details.
Claude Code is powerful. GSD Core makes it reliable.