1b317dec45
* feat(gsd-tools): add history-digest, atomic state operations, and summary variants Adds new performance-focused commands to gsd-tools and introduces specialized summary templates to reduce context tax: - history-digest: Compiles phase summaries into structured JSON for JIT loading - state get/patch: Enables atomic STATE.md operations instead of full rewrites - template select: Automatically chooses optimal summary template based on plan complexity - Adds minimal, standard, and complex summary templates Part of the "Hydra" architecture for GSD context optimization. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: add project config * docs: define v1 requirements * docs: create roadmap (6 phases) * feat(history-digest): fix nested YAML parsing and add tests - Fix extractFrontmatter() to handle nested YAML structures like dependency-graph.provides, tech-stack.added using stack-based parsing - Add test infrastructure with Node test runner (npm test) - Update gsd-planner to use digest fields directly instead of reading full SUMMARY.md files - Add 6 schema validation tests covering nested fields, merging, malformed files, and backward compatibility Closes: HIST-01, HIST-02, HIST-03, HIST-04 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(planner): use digest for selection, full SUMMARY for understanding The previous commit went too far by eliminating full SUMMARY reads. The digest is an index for smart selection, not a replacement for understanding what actually happened. Two-step approach: 1. Digest to score/select relevant phases (2-4 typically) 2. Full SUMMARY read for selected phases (implementation details) 3. Digest-level context retained for unselected phases Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(gsd-tools): add phases, roadmap, and phase commands TDD implementation of three new commands to replace repetitive bash: phases list [--type plans|summaries] [--phase N] - Lists phase directories sorted numerically (handles decimals) - Filter by file type or specific phase - Replaces: ls -d .planning/phases/*/ | sort -V (22 occurrences) roadmap get-phase <N> - Extracts phase section from ROADMAP.md - Returns name, goal, full section content - Replaces: grep -A20 "Phase X:" ROADMAP.md (19 occurrences) phase next-decimal <N> - Calculates next decimal phase (06 → 06.1, 06.2 → 06.3) - Handles gaps, normalizes input - Replaces: complex bash math in insert-phase (3 occurrences) 16 new tests, all passing. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: migrate agents/workflows to use gsd-tools commands Replace inline bash patterns with centralized gsd-tools commands: phases list: - audit-milestone.md: ls -d .planning/phases/*/ | sort -V - plan-milestone-gaps.md: ls -d ... | sort -V | tail -1 roadmap get-phase: - plan-phase.md: grep -A5 "Phase X:" ROADMAP.md (2 occurrences) - research-phase.md: grep patterns (2 occurrences) - verify-phase.md: grep -A5 pattern - gsd-verifier.md: grep -A5 pattern - gsd-plan-checker.md: grep -A10 pattern - commands/gsd/research-phase.md: grep patterns (2 occurrences) phase next-decimal: - insert-phase.md: complex bash decimal calculation - decimal-phase-calculation.md: reference doc rewritten phase-argument-parsing.md: updated to reference gsd-tools Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
60 lines
1.3 KiB
Markdown
60 lines
1.3 KiB
Markdown
---
|
|
phase: XX-name
|
|
plan: YY
|
|
subsystem: [primary category]
|
|
tags: [searchable tech]
|
|
requires:
|
|
- phase: [prior phase]
|
|
provides: [what that phase built]
|
|
provides:
|
|
- [bullet list of what was built/delivered]
|
|
affects: [list of phase names or keywords]
|
|
tech-stack:
|
|
added: [libraries/tools]
|
|
patterns: [architectural/code patterns]
|
|
key-files:
|
|
created: [important files created]
|
|
modified: [important files modified]
|
|
key-decisions:
|
|
- "Decision 1"
|
|
patterns-established:
|
|
- "Pattern 1: description"
|
|
duration: Xmin
|
|
completed: YYYY-MM-DD
|
|
---
|
|
|
|
# Phase [X]: [Name] Summary (Complex)
|
|
|
|
**[Substantive one-liner describing outcome]**
|
|
|
|
## Performance
|
|
- **Duration:** [time]
|
|
- **Tasks:** [count completed]
|
|
- **Files modified:** [count]
|
|
|
|
## Accomplishments
|
|
- [Key outcome 1]
|
|
- [Key outcome 2]
|
|
|
|
## Task Commits
|
|
1. **Task 1: [task name]** - `hash`
|
|
2. **Task 2: [task name]** - `hash`
|
|
3. **Task 3: [task name]** - `hash`
|
|
|
|
## Files Created/Modified
|
|
- `path/to/file.ts` - What it does
|
|
- `path/to/another.ts` - What it does
|
|
|
|
## Decisions Made
|
|
[Key decisions with brief rationale]
|
|
|
|
## Deviations from Plan (Auto-fixed)
|
|
[Detailed auto-fix records per GSD deviation rules]
|
|
|
|
## Issues Encountered
|
|
[Problems during planned work and resolutions]
|
|
|
|
## Next Phase Readiness
|
|
[What's ready for next phase]
|
|
[Blockers or concerns]
|