Clarified verification instructions for usage.
I was initially trying to get this to work in my PowerShell terminal, but later realized that the /gsd:help command became available inside Claude Code.
Sequential execution is now the recommended default. Parallel
execution is still being refined and may not yield best results.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
New features:
- /gsd:execute-phase: run all plans in a phase with parallel background agents
- /gsd:status: monitor background agent status from parallel execution
- Parallelization-aware planning with depends_on and files_modified frontmatter
- Automatic dependency analysis and wave-based execution
Configuration options in .planning/config.json:
- max_concurrent_agents (default: 3)
- skip_checkpoints (default: true)
- min_plans_for_parallel (default: 2)
Inspired by PR #43 from @davesienkowski - thank you for the design work!
Remove confusing `parallelizable` boolean field. It was redundant -
execute-phase already computes parallelizability from `depends_on`
and file conflicts.
Changes:
- Remove `parallelizable: true|false` from plan frontmatter
- Rename `files_exclusive` to `files_modified` (clearer intent)
- Simplify execute-phase dependency detection logic
- Update phase-prompt template and plan-phase workflow
Parallelization is now fully automatic based on:
- `depends_on: []` (empty = independent)
- `files_modified: [...]` (no overlap = can parallelize)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Routes to batch execution when 2+ plans exist, with execute-plan
as alternative for interactive mode.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Context isolation is the primary goal, not parallelization.
Even sequential plans spawn separate subagents for fresh 200k context.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add parallel-aware plan example with vertical slice pattern
- Add sequential plan example with explicit dependencies
- Document key differences between parallel and sequential plans
Tasks completed: 2/2
- Update analyze_plan_dependencies to read frontmatter fields
- Update categorization to use frontmatter parallelizable field
SUMMARY: .planning/phases/11-parallel-aware-planning/11-03-SUMMARY.md
- Update categorization table to show frontmatter-aware criteria
- Add categorization priority documentation
- Update calculate_wave() to check frontmatter depends_on first
- Handle parallelizable: false as implicit Wave 2+ assignment
- Fall back to inferred requires only when no frontmatter
- Add [frontmatter] annotation in wave output for plans using new fields
- Add PLAN_PARALLELIZABLE, PLAN_DEPENDS_ON, PLAN_FILES_EXCLUSIVE arrays
- Check for parallelizable, depends_on, files_exclusive in plan frontmatter
- Use frontmatter values directly when present
- Fall back to inference logic for old plans without frontmatter
- Document dependency detection priority
- Include parallelizable, depends_on, files_exclusive in frontmatter
- Rules for parallelizable field determination
- Parallel-aware context section guidance
- Avoid reflexive SUMMARY references when parallel
- File ownership analysis per task group
- Detect unnecessary inter-plan dependencies
- Restructure for vertical slices when beneficial
- Mark plans with parallelization frontmatter values
- Reads .planning/config.json parallelization settings early
- Documents planning behavior when parallel enabled vs disabled
- Placed after load_project_state, before load_codebase_context
- Default: assume parallelization enabled for new projects
- parallelizable: marks plan as safe for concurrent execution
- depends_on: explicit plan dependencies
- files_exclusive: conflict detection for parallel agents
- Added frontmatter_guidance section with usage rules
- Updated good_examples with parallel/sequential examples
Simple command to check background agent status:
- Shows running/completed agents from agent-history.json
- Uses TaskOutput to poll agent status
- --wait flag blocks until all complete
- Reports time savings vs sequential execution
Inspired by PR #43 but intentionally minimal (117 lines vs 317).
Skipped task-level parallelization display (not implementing that).
Moves config.json creation to its own step so the parallelization
question isn't skipped. Matches pattern used by mode and depth steps.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Tasks completed: 3/3
- Update schema version and add new fields
- Add parallel execution examples
- Document resume support for parallel groups
Phase 10 complete. Milestone complete.
SUMMARY: .planning/phases/10-parallel-phase-execution/10-04-SUMMARY.md
- Sequential execution example with all fields
- Plan-level parallel execution example
- Queued with dependency example
- Document parallel_group format conventions
- Command now loads both workflows (execution + orchestration)
- Agents commit tasks normally (removed DON'T COMMIT instruction)
- Orchestrator only commits metadata after all agents complete
- No duplication - single source of truth for execution logic
Adds /gsd:add-todo and /gsd:check-todos commands for capturing
ideas during work sessions without losing context.
Features:
- Capture todos from conversation context or explicit description
- Structured frontmatter (created, title, area, files)
- Area inference from file paths for grouping
- Duplicate detection before creating
- Filter todos by area
- Route to appropriate action (work now, add to phase, brainstorm)
- Git commits on capture and when starting work
Closes#48
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
