- Add research & scope step to "How It Works" (optional but recommended)
- Update brownfield section with full optional flow
- Add research-project and define-requirements to commands
- Add research/ and REQUIREMENTS.md to context engineering table
- Split commands into 7 grouped tables for easier scanning
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Research now loads concrete requirements (e.g., "AUTH-02: User receives
email verification") to inform research domains, not just high-level
roadmap descriptions.
Co-Authored-By: Claude <noreply@anthropic.com>
- Remove phantom status.md command (background agent model abandoned)
- Remove agent-history.md template (unused)
- Remove _archive/ directory
- Add narration to execute-phase (describe what's being built before/after waves)
- Update new-project to offer define-requirements as fast path
- Make define-requirements work without research (gather through questioning)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Promote /gsd:whats-new and update command visibility.
GSD evolves fast — users should check periodically.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Subagents can't determine if phase is complete. The orchestrator
(execute-plan and execute-phase commands) runs in main context,
can count plans vs summaries, and updates REQUIREMENTS.md when
phase completes.
- execute-plan: Step 2.5 updates requirements when summaries = plans
- execute-phase: Step 6 updates requirements (phase always complete)
- Removed duplicate from workflow (subagent can't run it anyway)
When all plans in a phase complete:
1. Look up phase's requirements from ROADMAP.md
2. Update REQUIREMENTS.md traceability table (Pending → Complete)
3. Include in metadata commit
Closes the loop on requirement tracking.
- Roadmap template now includes Requirements: field for each phase
- plan-phase loads REQUIREMENTS.md and extracts phase-specific requirements
- define-requirements shows full list inline before commit (not just counts)
Reduce principles.md from 158 to 73 lines:
- Remove duplicates (atomic_commits, tdd, deviation_rules)
- Remove version drag from claude_automates
- Keep core orientation: solo dev model, plans are prompts,
scope control, ship fast, anti-enterprise
Add principles.md to 9 core commands so Claude always
understands what GSD is.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Focus on what to extract, not what to avoid:
- What they're building
- Why it needs to exist
- Who it's for
- What done looks like
Remove version drag and redundant question categories.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Follow threads naturally instead of rigid step order
- Cleaner question techniques in questioning.md
- Background context checklist instead of forced checklist mode
- Updated next steps to show research flow
Adds /gsd:research-project to research domain ecosystem before creating roadmap.
Spawns parallel agents to investigate stack, features, architecture, and pitfalls.
New files:
- commands/gsd/research-project.md
- get-shit-done/workflows/research-project.md
- get-shit-done/templates/research-project/ (5 templates)
Modified:
- new-project.md: offers research vs direct roadmap options
- create-roadmap.md: loads research if exists
- workflows/create-roadmap.md: uses research to inform phases
Co-Authored-By: Claude <noreply@anthropic.com>
Command now references workflow for checkpoint handling details
instead of duplicating logic. Keeps command thin as intended.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- execute-plan.md: Replace broken Task(resume=...) with fresh continuation agent
- execute-phase.md: Expand checkpoint handling with full continuation flow
- checkpoints.md: Restore ~500 lines of detailed examples and anti-patterns
Checkpoint presentation formats now documented for all three types.
Templates referenced: checkpoint-return.md, continuation-prompt.md
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The orchestrator pattern conversion (8ed6a8f) removed workflow context
loading for context efficiency but inadvertently removed the offer_next
step that presents copy/paste-ready next commands after plan/phase
completion.
Added explicit <offer_next> sections to both commands:
- execute-plan.md: routes to next plan, next phase, or milestone complete
- execute-phase.md: routes to next phase or milestone complete
Both include /clear hints and copy/paste-ready command paths.
Fixes#69
Co-Authored-By: Claude <noreply@anthropic.com>
- Reads installed version from VERSION file
- Fetches remote changelog from GitHub
- Displays version comparison and missed changes
- Provides update instructions when behind