@undeemed/get-shit-done-codex 1.6.11 → 1.20.2

package/commands/gsd/help.md

@@ -2,382 +2,21 @@
 name: gsd:help
 description: Show available GSD commands and usage guide
 ---
-
 <objective>
 Display the complete GSD command reference.
 
 Output ONLY the reference content below. Do NOT add:
-
 - Project-specific analysis
 - Git status or file context
 - Next-step suggestions
 - Any commentary beyond the reference
-  </objective>
-
-<reference>
-# GSD Command Reference
-
-**GSD** (Get Shit Done) creates hierarchical project plans optimized for solo agentic development with OpenAI Codex CLI.
-
-## Quick Start
-
-1. `/gsd:new-project` - Initialize project (includes research, requirements, roadmap)
-2. `/gsd:plan-phase 1` - Create detailed plan for first phase
-3. `/gsd:execute-phase 1` - Execute the phase
-
-## Staying Updated
-
-GSD evolves fast. Check for updates periodically:
-
-```
-/gsd:whats-new
-```
-
-Shows what changed since your installed version. Update with:
-
-```bash
-npx get-shit-done-cc@latest
-```
-
-## Core Workflow
-
-```
-/gsd:new-project → /gsd:plan-phase → /gsd:execute-phase → repeat
-```
-
-### Project Initialization
-
-**`/gsd:new-project`**
-Initialize new project through unified flow.
-
-One command takes you from idea to ready-for-planning:
-- Deep questioning to understand what you're building
-- Optional domain research (spawns 4 parallel researcher agents)
-- Requirements definition with v1/v2/out-of-scope scoping
-- Roadmap creation with phase breakdown and success criteria
-
-Creates all `.planning/` artifacts:
-- `PROJECT.md` — vision and requirements
-- `config.json` — workflow mode (interactive/yolo)
-- `research/` — domain research (if selected)
-- `REQUIREMENTS.md` — scoped requirements with REQ-IDs
-- `ROADMAP.md` — phases mapped to requirements
-- `STATE.md` — project memory
-
-Usage: `/gsd:new-project`
-
-**`/gsd:map-codebase`**
-Map an existing codebase for brownfield projects.
-
-- Analyzes codebase with parallel Explore agents
-- Creates `.planning/codebase/` with 7 focused documents
-- Covers stack, architecture, structure, conventions, testing, integrations, concerns
-- Use before `/gsd:new-project` on existing codebases
-
-Usage: `/gsd:map-codebase`
-
-### Phase Planning
-
-**`/gsd:discuss-phase <number>`**
-Help articulate your vision for a phase before planning.
-
-- Captures how you imagine this phase working
-- Creates CONTEXT.md with your vision, essentials, and boundaries
-- Use when you have ideas about how something should look/feel
-
-Usage: `/gsd:discuss-phase 2`
-
-**`/gsd:research-phase <number>`**
-Comprehensive ecosystem research for niche/complex domains.
-
-- Discovers standard stack, architecture patterns, pitfalls
-- Creates RESEARCH.md with "how experts build this" knowledge
-- Use for 3D, games, audio, shaders, ML, and other specialized domains
-- Goes beyond "which library" to ecosystem knowledge
-
-Usage: `/gsd:research-phase 3`
-
-**`/gsd:list-phase-assumptions <number>`**
-See what Claude is planning to do before it starts.
-
-- Shows Codex's intended approach for a phase
-- Lets you course-correct if Codex misunderstood your vision
-- No files created - conversational output only
-
-Usage: `/gsd:list-phase-assumptions 3`
-
-**`/gsd:plan-phase <number>`**
-Create detailed execution plan for a specific phase.
-
-- Generates `.planning/phases/XX-phase-name/XX-YY-PLAN.md`
-- Breaks phase into concrete, actionable tasks
-- Includes verification criteria and success measures
-- Multiple plans per phase supported (XX-01, XX-02, etc.)
-
-Usage: `/gsd:plan-phase 1`
-Result: Creates `.planning/phases/01-foundation/01-01-PLAN.md`
-
-### Execution
-
-**`/gsd:execute-phase <phase-number>`**
-Execute all plans in a phase.
-
-- Groups plans by wave (from frontmatter), executes waves sequentially
-- Plans within each wave run in parallel via Task tool
-- Verifies phase goal after all plans complete
-- Updates REQUIREMENTS.md, ROADMAP.md, STATE.md
-
-Usage: `/gsd:execute-phase 5`
-
-### Roadmap Management
-
-**`/gsd:add-phase <description>`**
-Add new phase to end of current milestone.
-
-- Appends to ROADMAP.md
-- Uses next sequential number
-- Updates phase directory structure
-
-Usage: `/gsd:add-phase "Add admin dashboard"`
-
-**`/gsd:insert-phase <after> <description>`**
-Insert urgent work as decimal phase between existing phases.
-
-- Creates intermediate phase (e.g., 7.1 between 7 and 8)
-- Useful for discovered work that must happen mid-milestone
-- Maintains phase ordering
-
-Usage: `/gsd:insert-phase 7 "Fix critical auth bug"`
-Result: Creates Phase 7.1
-
-**`/gsd:remove-phase <number>`**
-Remove a future phase and renumber subsequent phases.
-
-- Deletes phase directory and all references
-- Renumbers all subsequent phases to close the gap
-- Only works on future (unstarted) phases
-- Git commit preserves historical record
-
-Usage: `/gsd:remove-phase 17`
-Result: Phase 17 deleted, phases 18-20 become 17-19
-
-### Milestone Management
-
-**`/gsd:new-milestone <name>`**
-Start a new milestone through unified flow.
-
-- Deep questioning to understand what you're building next
-- Optional domain research (spawns 4 parallel researcher agents)
-- Requirements definition with scoping
-- Roadmap creation with phase breakdown
-
-Mirrors `/gsd:new-project` flow for brownfield projects (existing PROJECT.md).
-
-Usage: `/gsd:new-milestone "v2.0 Features"`
-
-**`/gsd:complete-milestone <version>`**
-Archive completed milestone and prepare for next version.
-
-- Creates MILESTONES.md entry with stats
-- Archives full details to milestones/ directory
-- Creates git tag for the release
-- Prepares workspace for next version
-
-Usage: `/gsd:complete-milestone 1.0.0`
-
-### Progress Tracking
-
-**`/gsd:progress`**
-Check project status and intelligently route to next action.
-
-- Shows visual progress bar and completion percentage
-- Summarizes recent work from SUMMARY files
-- Displays current position and what's next
-- Lists key decisions and open issues
-- Offers to execute next plan or create it if missing
-- Detects 100% milestone completion
-
-Usage: `/gsd:progress`
-
-### Session Management
-
-**`/gsd:resume-work`**
-Resume work from previous session with full context restoration.
-
-- Reads STATE.md for project context
-- Shows current position and recent progress
-- Offers next actions based on project state
-
-Usage: `/gsd:resume-work`
-
-**`/gsd:pause-work`**
-Create context handoff when pausing work mid-phase.
-
-- Creates .continue-here file with current state
-- Updates STATE.md session continuity section
-- Captures in-progress work context
-
-Usage: `/gsd:pause-work`
-
-### Debugging
-
-**`/gsd:debug [issue description]`**
-Systematic debugging with persistent state across context resets.
-
-- Gathers symptoms through adaptive questioning
-- Creates `.planning/debug/[slug].md` to track investigation
-- Investigates using scientific method (evidence → hypothesis → test)
-- Survives `/clear` — run `/gsd:debug` with no args to resume
-- Archives resolved issues to `.planning/debug/resolved/`
-
-Usage: `/gsd:debug "login button doesn't work"`
-Usage: `/gsd:debug` (resume active session)
-
-### Todo Management
-
-**`/gsd:add-todo [description]`**
-Capture idea or task as todo from current conversation.
-
-- Extracts context from conversation (or uses provided description)
-- Creates structured todo file in `.planning/todos/pending/`
-- Infers area from file paths for grouping
-- Checks for duplicates before creating
-- Updates STATE.md todo count
-
-Usage: `/gsd:add-todo` (infers from conversation)
-Usage: `/gsd:add-todo Add auth token refresh`
-
-**`/gsd:check-todos [area]`**
-List pending todos and select one to work on.
-
-- Lists all pending todos with title, area, age
-- Optional area filter (e.g., `/gsd:check-todos api`)
-- Loads full context for selected todo
-- Routes to appropriate action (work now, add to phase, brainstorm)
-- Moves todo to done/ when work begins
-
-Usage: `/gsd:check-todos`
-Usage: `/gsd:check-todos api`
-
-### Utility Commands
-
-**`/gsd:help`**
-Show this command reference.
-
-**`/gsd:whats-new`**
-See what's changed since your installed version.
-
-- Shows installed vs latest version comparison
-- Displays changelog entries for versions you've missed
-- Highlights breaking changes
-- Provides update instructions when behind
-
-Usage: `/gsd:whats-new`
-
-## Files & Structure
-
-```
-.planning/
-├── PROJECT.md            # Project vision
-├── ROADMAP.md            # Current phase breakdown
-├── STATE.md              # Project memory & context
-├── config.json           # Workflow mode & gates
-├── todos/                # Captured ideas and tasks
-│   ├── pending/          # Todos waiting to be worked on
-│   └── done/             # Completed todos
-├── debug/                # Active debug sessions
-│   └── resolved/         # Archived resolved issues
-├── codebase/             # Codebase map (brownfield projects)
-│   ├── STACK.md          # Languages, frameworks, dependencies
-│   ├── ARCHITECTURE.md   # Patterns, layers, data flow
-│   ├── STRUCTURE.md      # Directory layout, key files
-│   ├── CONVENTIONS.md    # Coding standards, naming
-│   ├── TESTING.md        # Test setup, patterns
-│   ├── INTEGRATIONS.md   # External services, APIs
-│   └── CONCERNS.md       # Tech debt, known issues
-└── phases/
-    ├── 01-foundation/
-    │   ├── 01-01-PLAN.md
-    │   └── 01-01-SUMMARY.md
-    └── 02-core-features/
-        ├── 02-01-PLAN.md
-        └── 02-01-SUMMARY.md
-```
-
-## Workflow Modes
-
-Set during `/gsd:new-project`:
-
-**Interactive Mode**
-
-- Confirms each major decision
-- Pauses at checkpoints for approval
-- More guidance throughout
-
-**YOLO Mode**
-
-- Auto-approves most decisions
-- Executes plans without confirmation
-- Only stops for critical checkpoints
-
-Change anytime by editing `.planning/config.json`
-
-## Common Workflows
-
-**Starting a new project:**
-
-```
-/gsd:new-project        # Unified flow: questioning → research → requirements → roadmap
-/clear
-/gsd:plan-phase 1       # Create plans for first phase
-/clear
-/gsd:execute-phase 1    # Execute all plans in phase
-```
-
-**Resuming work after a break:**
-
-```
-/gsd:progress  # See where you left off and continue
-```
-
-**Adding urgent mid-milestone work:**
-
-```
-/gsd:insert-phase 5 "Critical security fix"
-/gsd:plan-phase 5.1
-/gsd:execute-phase 5.1
-```
-
-**Completing a milestone:**
-
-```
-/gsd:complete-milestone 1.0.0
-/clear
-/gsd:new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
-```
-
-**Capturing ideas during work:**
-
-```
-/gsd:add-todo                    # Capture from conversation context
-/gsd:add-todo Fix modal z-index  # Capture with explicit description
-/gsd:check-todos                 # Review and work on todos
-/gsd:check-todos api             # Filter by area
-```
-
-**Debugging an issue:**
-
-```
-/gsd:debug "form submission fails silently"  # Start debug session
-# ... investigation happens, context fills up ...
-/clear
-/gsd:debug                                    # Resume from where you left off
-```
+</objective>
 
-## Getting Help
+<execution_context>
+@~/.claude/get-shit-done/workflows/help.md
+</execution_context>
 
-- Read `.planning/PROJECT.md` for project vision
-- Read `.planning/STATE.md` for current context
-- Check `.planning/ROADMAP.md` for phase status
-- Run `/gsd:progress` to check where you're up to
-  </reference>
+<process>
+Output the complete GSD command reference from @~/.claude/get-shit-done/workflows/help.md.
+Display the reference content directly — no additions or modifications.
+</process>

package/commands/gsd/insert-phase.md

@@ -17,211 +17,17 @@ Purpose: Handle urgent work discovered during execution without renumbering enti
 </objective>
 
 <execution_context>
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@~/.claude/get-shit-done/workflows/insert-phase.md
 </execution_context>
 
-<process>
-
-<step name="parse_arguments">
-Parse the command arguments:
-- First argument: integer phase number to insert after
-- Remaining arguments: phase description
-
-Example: `/gsd:insert-phase 72 Fix critical auth bug`
-→ after = 72
-→ description = "Fix critical auth bug"
-
-Validation:
-
-```bash
-if [ $# -lt 2 ]; then
-  echo "ERROR: Both phase number and description required"
-  echo "Usage: /gsd:insert-phase <after> <description>"
-  echo "Example: /gsd:insert-phase 72 Fix critical auth bug"
-  exit 1
-fi
-```
-
-Parse first argument as integer:
-
-```bash
-after_phase=$1
-shift
-description="$*"
-
-# Validate after_phase is an integer
-if ! [[ "$after_phase" =~ ^[0-9]+$ ]]; then
-  echo "ERROR: Phase number must be an integer"
-  exit 1
-fi
-```
-
-</step>
-
-<step name="load_roadmap">
-Load the roadmap file:
-
-```bash
-if [ -f .planning/ROADMAP.md ]; then
-  ROADMAP=".planning/ROADMAP.md"
-else
-  echo "ERROR: No roadmap found (.planning/ROADMAP.md)"
-  exit 1
-fi
-```
-
-Read roadmap content for parsing.
-</step>
-
-<step name="verify_target_phase">
-Verify that the target phase exists in the roadmap:
-
-1. Search for "### Phase {after_phase}:" heading
-2. If not found:
-
-   ```
-   ERROR: Phase {after_phase} not found in roadmap
-   Available phases: [list phase numbers]
-   ```
-
-   Exit.
-
-3. Verify phase is in current milestone (not completed/archived)
-   </step>
-
-<step name="find_existing_decimals">
-Find existing decimal phases after the target phase:
-
-1. Search for all "### Phase {after_phase}.N:" headings
-2. Extract decimal suffixes (e.g., for Phase 72: find 72.1, 72.2, 72.3)
-3. Find the highest decimal suffix
-4. Calculate next decimal: max + 1
-
-Examples:
-
-- Phase 72 with no decimals → next is 72.1
-- Phase 72 with 72.1 → next is 72.2
-- Phase 72 with 72.1, 72.2 → next is 72.3
-
-Store as: `decimal_phase="$(printf "%02d" $after_phase).${next_decimal}"`
-</step>
-
-<step name="generate_slug">
-Convert the phase description to a kebab-case slug:
-
-```bash
-slug=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-//;s/-$//')
-```
-
-Phase directory name: `{decimal-phase}-{slug}`
-Example: `06.1-fix-critical-auth-bug` (phase 6 insertion)
-</step>
-
-<step name="create_phase_directory">
-Create the phase directory structure:
-
-```bash
-phase_dir=".planning/phases/${decimal_phase}-${slug}"
-mkdir -p "$phase_dir"
-```
-
-Confirm: "Created directory: $phase_dir"
-</step>
-
-<step name="update_roadmap">
-Insert the new phase entry into the roadmap:
-
-1. Find insertion point: immediately after Phase {after_phase}'s content (before next phase heading or "---")
-2. Insert new phase heading with (INSERTED) marker:
+<context>
+Arguments: $ARGUMENTS (format: <after-phase-number> <description>)
 
-   ```
-   ### Phase {decimal_phase}: {Description} (INSERTED)
-
-   **Goal:** [Urgent work - to be planned]
-   **Depends on:** Phase {after_phase}
-   **Plans:** 0 plans
-
-   Plans:
-   - [ ] TBD (run /gsd:plan-phase {decimal_phase} to break down)
-
-   **Details:**
-   [To be added during planning]
-   ```
-
-3. Write updated roadmap back to file
-
-The "(INSERTED)" marker helps identify decimal phases as urgent insertions.
-
-Preserve all other content exactly (formatting, spacing, other phases).
-</step>
-
-<step name="update_project_state">
-Update STATE.md to reflect the inserted phase:
-
-1. Read `.planning/STATE.md`
-2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
-   ```
-   - Phase {decimal_phase} inserted after Phase {after_phase}: {description} (URGENT)
-   ```
-
-If "Roadmap Evolution" section doesn't exist, create it.
-
-Add note about insertion reason if appropriate.
-</step>
-
-<step name="completion">
-Present completion summary:
-
-```
-Phase {decimal_phase} inserted after Phase {after_phase}:
-- Description: {description}
-- Directory: .planning/phases/{decimal-phase}-{slug}/
-- Status: Not planned yet
-- Marker: (INSERTED) - indicates urgent work
-
-Roadmap updated: {roadmap-path}
-Project state updated: .planning/STATE.md
-
----
-
-## ▶ Next Up
-
-**Phase {decimal_phase}: {description}** — urgent insertion
-
-`/gsd:plan-phase {decimal_phase}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- Review insertion impact: Check if Phase {next_integer} dependencies still make sense
-- Review roadmap
-
----
-```
-</step>
+@.planning/ROADMAP.md
+@.planning/STATE.md
+</context>
 
+<process>
+Execute the insert-phase workflow from @~/.claude/get-shit-done/workflows/insert-phase.md end-to-end.
+Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates).
 </process>
-
-<anti_patterns>
-
-- Don't use this for planned work at end of milestone (use /gsd:add-phase)
-- Don't insert before Phase 1 (decimal 0.1 makes no sense)
-- Don't renumber existing phases
-- Don't modify the target phase content
-- Don't create plans yet (that's /gsd:plan-phase)
-- Don't commit changes (user decides when to commit)
-  </anti_patterns>
-
-<success_criteria>
-Phase insertion is complete when:
-
-- [ ] Phase directory created: `.planning/phases/{N.M}-{slug}/`
-- [ ] Roadmap updated with new phase entry (includes "(INSERTED)" marker)
-- [ ] Phase inserted in correct position (after target phase, before next integer phase)
-- [ ] STATE.md updated with roadmap evolution note
-- [ ] Decimal number calculated correctly (based on existing decimals)
-- [ ] User informed of next steps and dependency implications
-      </success_criteria>

package/commands/gsd/join-discord.md

@@ -0,0 +1,18 @@
+---
+name: gsd:join-discord
+description: Join the GSD Discord community
+---
+
+<objective>
+Display the Discord invite link for the GSD community server.
+</objective>
+
+<output>
+# Join the GSD Discord
+
+Connect with other GSD users, get help, share what you're building, and stay updated.
+
+**Invite link:** https://discord.gg/5JJgD5svVS
+
+Click the link or paste it into your browser to join.
+</output>