get-shit-done-cc 1.5.30 → 1.6.1

package/commands/gsd/define-requirements.md

@@ -1,134 +0,0 @@
----
-name: gsd:define-requirements
-description: Define what "done" looks like with checkable requirements
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - AskUserQuestion
----
-
-<!--
-DEPRECATED: This command is now integrated into /gsd:new-project
-
-The unified /gsd:new-project flow includes requirements definition as Phase 7.
-This standalone command is kept for users who want to:
-- Redefine requirements mid-project
-- Add new requirements after initial project setup
-- Adjust v1/v2 scope boundaries
-
-For new projects, use /gsd:new-project instead.
-
-Deprecated: 2026-01-16
--->
-
-<objective>
-Define concrete, checkable requirements for v1.
-
-Two modes:
-1. **With research** — Transform FEATURES.md into scoped requirements
-2. **Without research** — Gather requirements through questioning
-
-Output: `.planning/REQUIREMENTS.md`
-
-**Note:** For new projects, `/gsd:new-project` includes requirements definition. Use this command to redefine requirements later.
-</objective>
-
-<execution_context>
-@~/.claude/get-shit-done/workflows/define-requirements.md
-@~/.claude/get-shit-done/templates/requirements.md
-</execution_context>
-
-<context>
-@.planning/PROJECT.md
-@.planning/research/FEATURES.md (if exists)
-@.planning/research/SUMMARY.md (if exists)
-</context>
-
-<process>
-
-<step name="validate">
-```bash
-# Verify project exists
-[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md found. Run /gsd:new-project first."; exit 1; }
-
-# Check for research
-[ -f .planning/research/FEATURES.md ] && echo "HAS_RESEARCH" || echo "NO_RESEARCH"
-
-# Check if requirements already exist
-[ -f .planning/REQUIREMENTS.md ] && echo "REQUIREMENTS_EXISTS" || echo "NO_REQUIREMENTS"
-```
-</step>
-
-<step name="check_existing">
-**If REQUIREMENTS_EXISTS:**
-
-Use AskUserQuestion:
-- header: "Requirements exist"
-- question: "Requirements already defined. What would you like to do?"
-- options:
-  - "View existing" — Show current requirements
-  - "Replace" — Define requirements fresh (will overwrite)
-  - "Cancel" — Keep existing requirements
-
-If "View existing": Read and display `.planning/REQUIREMENTS.md`, then exit
-If "Cancel": Exit
-If "Replace": Continue with workflow
-</step>
-
-<step name="execute">
-**If HAS_RESEARCH:**
-Follow the define-requirements.md workflow:
-- Load research features from FEATURES.md
-- Present features by category
-- Ask user to scope each category (v1 / v2 / out of scope)
-- Capture any additions research missed
-- Generate REQUIREMENTS.md with checkable list
-
-**If NO_RESEARCH:**
-Gather requirements through questioning:
-- Read PROJECT.md for core value and context
-- Ask: "What are the main things users need to be able to do?"
-- For each capability mentioned, probe for specifics
-- Group into categories (Authentication, Content, etc.)
-- For each category, ask what's v1 vs v2 vs out of scope
-- Generate REQUIREMENTS.md with checkable list
-
-Same output format either way — the difference is source (research vs conversation).
-</step>
-
-<step name="done">
-```
-Requirements defined:
-
-- Requirements: .planning/REQUIREMENTS.md
-- v1 scope: [N] requirements across [M] categories
-- v2 scope: [X] requirements deferred
-- Out of scope: [Y] requirements excluded
-
----
-
-## ▶ Next Up
-
-**Create roadmap** — phases mapped to requirements
-
-`/gsd:create-roadmap`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] PROJECT.md validated
-- [ ] Features gathered (from research OR questioning)
-- [ ] User scoped each category (v1/v2/out of scope)
-- [ ] User had opportunity to add missing requirements
-- [ ] REQUIREMENTS.md created with checkable list
-- [ ] Requirements committed to git
-- [ ] User knows next step (create-roadmap)
-</success_criteria>

package/commands/gsd/discuss-milestone.md

@@ -1,47 +0,0 @@
----
-name: gsd:discuss-milestone
-description: Gather context for next milestone through adaptive questioning
----
-
-<objective>
-Help you figure out what to build in the next milestone through collaborative thinking.
-
-Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build.
-Output: Context gathered, then routes to /gsd:new-milestone
-</objective>
-
-<execution_context>
-@~/.claude/get-shit-done/workflows/discuss-milestone.md
-</execution_context>
-
-<context>
-**Load project state first:**
-@.planning/STATE.md
-
-**Load project:**
-@.planning/PROJECT.md
-
-**Load milestones (if exists):**
-@.planning/MILESTONES.md
-</context>
-
-<process>
-1. Verify previous milestone complete (or acknowledge active milestone)
-2. Present context from previous milestone (accomplishments, phase count)
-3. Follow discuss-milestone.md workflow with **ALL questions using AskUserQuestion**:
-   - Use AskUserQuestion: "What do you want to add, improve, or fix?" with feature categories
-   - Use AskUserQuestion to dig into features they mention
-   - Use AskUserQuestion to help them articulate what matters most
-   - Use AskUserQuestion for decision gate (ready / ask more / let me add context)
-4. Hand off to /gsd:new-milestone with gathered context
-
-**CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
-</process>
-
-<success_criteria>
-
-- Project state loaded and presented
-- Previous milestone context summarized
-- Milestone scope gathered through adaptive questioning
-- Context handed off to /gsd:new-milestone
-  </success_criteria>

package/commands/gsd/research-project.md

@@ -1,323 +0,0 @@
----
-name: gsd:research-project
-description: Research domain ecosystem before creating roadmap
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Task
-  - AskUserQuestion
----
-
-<!--
-DEPRECATED: This command is now integrated into /gsd:new-project
-
-The unified /gsd:new-project flow includes optional research as Phase 6.
-This standalone command is kept for users who want to:
-- Re-research a domain mid-project
-- Research without running full new-project flow
-- Add research after skipping it initially
-
-For new projects, use /gsd:new-project instead.
-
-Deprecated: 2026-01-16
--->
-
-<objective>
-Research domain ecosystem. Spawns 4 parallel gsd-project-researcher agents for comprehensive coverage.
-
-**Orchestrator role:** Analyze project, generate research questions, spawn 4 parallel agents, synthesize SUMMARY.md.
-
-**Why subagents:** Research burns context fast. Fresh 200k context per domain. Main context stays lean.
-
-**Note:** For new projects, `/gsd:new-project` includes research as an optional step. Use this command to re-research or add research later.
-</objective>
-
-<context>
-@.planning/PROJECT.md
-@.planning/config.json (if exists)
-</context>
-
-<process>
-
-## 1. Validate Prerequisites
-
-```bash
-[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md. Run /gsd:new-project first."; exit 1; }
-[ -f .planning/ROADMAP.md ] && echo "WARNING: ROADMAP.md exists. Research is typically done before roadmap."
-[ -d .planning/research ] && echo "RESEARCH_EXISTS" || echo "NO_RESEARCH"
-```
-
-## 2. Handle Existing Research
-
-**If RESEARCH_EXISTS:** Use AskUserQuestion (View existing / Replace / Cancel)
-
-## 3. Analyze Project
-
-Read PROJECT.md, extract domain/stack/core value/constraints. Present for approval:
-```
-Domain analysis:
-- Type: [domain]
-- Stack: [stated or TBD]
-- Core: [core value]
-Does this look right? (yes / adjust)
-```
-
-## 4. Generate Research Questions
-
-| Dimension | Question |
-|-----------|----------|
-| Stack | "What's the standard 2025 stack for [domain]?" |
-| Features | "What features do [domain] products have?" |
-| Architecture | "How are [domain] systems structured?" |
-| Pitfalls | "What do [domain] projects get wrong?" |
-
-Present for approval.
-
-## 5. Spawn Research Agents
-
-```bash
-mkdir -p .planning/research
-```
-
-**Determine milestone context:**
-- If no "Validated" requirements in REQUIREMENTS.md → Greenfield (v1.0)
-- If "Validated" requirements exist → Subsequent milestone (v1.1+)
-
-Spawn all 4 in parallel with rich context:
-
-```
-Task(prompt="
-<research_type>
-Project Research — Stack dimension for [domain].
-</research_type>
-
-<milestone_context>
-{greenfield OR subsequent}
-
-Greenfield: Research the standard stack for building [domain] from scratch.
-Subsequent: Research what's needed to add [target features] to an existing [domain] app. Don't re-research the existing system.
-</milestone_context>
-
-<question>
-[stack question from step 4]
-</question>
-
-<project_context>
-[PROJECT.md summary]
-</project_context>
-
-<downstream_consumer>
-Your STACK.md feeds into /gsd:create-roadmap. Be prescriptive:
-- Specific libraries with versions
-- Clear rationale for each choice
-- What NOT to use and why
-</downstream_consumer>
-
-<quality_gate>
-- [ ] Versions are current (not Claude's training data)
-- [ ] Rationale explains WHY, not just WHAT
-- [ ] Confidence levels assigned
-</quality_gate>
-
-<output>
-Write to: .planning/research/STACK.md
-Use template: ~/.claude/get-shit-done/templates/research-project/STACK.md
-</output>
-", subagent_type="gsd-project-researcher", description="Stack research")
-
-Task(prompt="
-<research_type>
-Project Research — Features dimension for [domain].
-</research_type>
-
-<milestone_context>
-{greenfield OR subsequent}
-
-Greenfield: What features do [domain] products have? What's table stakes vs differentiating?
-Subsequent: How do [target features] typically work? What's expected behavior?
-</milestone_context>
-
-<question>
-[features question from step 4]
-</question>
-
-<project_context>
-[PROJECT.md summary]
-</project_context>
-
-<downstream_consumer>
-Your FEATURES.md feeds into /gsd:define-requirements. Categorize clearly:
-- Table stakes (must have or users leave)
-- Differentiators (competitive advantage)
-- Anti-features (things to deliberately NOT build)
-</downstream_consumer>
-
-<quality_gate>
-- [ ] Categories are clear
-- [ ] Complexity noted for each
-- [ ] Dependencies between features identified
-</quality_gate>
-
-<output>
-Write to: .planning/research/FEATURES.md
-Use template: ~/.claude/get-shit-done/templates/research-project/FEATURES.md
-</output>
-", subagent_type="gsd-project-researcher", description="Features research")
-
-Task(prompt="
-<research_type>
-Project Research — Architecture dimension for [domain].
-</research_type>
-
-<milestone_context>
-{greenfield OR subsequent}
-
-Greenfield: How are [domain] systems typically structured? What are major components?
-Subsequent: How do [target features] integrate with existing [domain] architecture?
-</milestone_context>
-
-<question>
-[architecture question from step 4]
-</question>
-
-<project_context>
-[PROJECT.md summary]
-</project_context>
-
-<downstream_consumer>
-Your ARCHITECTURE.md informs phase structure in roadmap. Include:
-- Component boundaries (what talks to what)
-- Data flow (how information moves)
-- Suggested build order (dependencies between components)
-</downstream_consumer>
-
-<quality_gate>
-- [ ] Components clearly defined
-- [ ] Boundaries explicit
-- [ ] Build order implications noted
-</quality_gate>
-
-<output>
-Write to: .planning/research/ARCHITECTURE.md
-Use template: ~/.claude/get-shit-done/templates/research-project/ARCHITECTURE.md
-</output>
-", subagent_type="gsd-project-researcher", description="Architecture research")
-
-Task(prompt="
-<research_type>
-Project Research — Pitfalls dimension for [domain].
-</research_type>
-
-<milestone_context>
-{greenfield OR subsequent}
-
-Greenfield: What do [domain] projects commonly get wrong? Critical mistakes?
-Subsequent: What are common mistakes when adding [target features] to [domain]?
-</milestone_context>
-
-<question>
-[pitfalls question from step 4]
-</question>
-
-<project_context>
-[PROJECT.md summary]
-</project_context>
-
-<downstream_consumer>
-Your PITFALLS.md prevents mistakes in roadmap/planning. For each pitfall:
-- Warning signs (how to detect early)
-- Prevention strategy (how to avoid)
-- Which phase should address it
-</downstream_consumer>
-
-<quality_gate>
-- [ ] Pitfalls are specific, not generic
-- [ ] Prevention is actionable
-- [ ] Phase mapping included
-</quality_gate>
-
-<output>
-Write to: .planning/research/PITFALLS.md
-Use template: ~/.claude/get-shit-done/templates/research-project/PITFALLS.md
-</output>
-", subagent_type="gsd-project-researcher", description="Pitfalls research")
-```
-
-**Announce:** "Spawning 4 research agents... may take 2-3 minutes."
-
-## 6. Synthesize Results
-
-After all agents complete, read their outputs and write `.planning/research/SUMMARY.md`:
-- Read template: `~/.claude/get-shit-done/templates/research-project/SUMMARY.md`
-- Synthesize executive summary from all 4 files
-- Add confidence assessment
-
-**Critical: Include "Implications for Roadmap" section:**
-
-```markdown
-## Implications for Roadmap
-
-Based on research, suggested phase structure:
-
-1. **[Phase name]** — [rationale from research]
-   - Addresses: [features from FEATURES.md]
-   - Avoids: [pitfall from PITFALLS.md]
-   - Uses: [stack element from STACK.md]
-
-2. **[Phase name]** — [rationale from research]
-   - Implements: [architecture component from ARCHITECTURE.md]
-   ...
-
-**Phase ordering rationale:**
-- [Why this order based on dependencies discovered in ARCHITECTURE.md]
-- [Why this grouping based on PITFALLS.md prevention strategies]
-
-**Research flags for phases:**
-- Phase [X]: Likely needs deeper research (reason)
-- Phase [Y]: Standard patterns, unlikely to need research
-```
-
-This section directly feeds into `/gsd:create-roadmap`.
-
-## 7. Commit Research
-
-```bash
-git add .planning/research/
-git commit -m "docs: research [domain] ecosystem
-
-Key findings:
-- Stack: [one-liner]
-- Architecture: [one-liner]
-- Critical pitfall: [one-liner]"
-```
-
-## 8. Present Results
-
-```
-Research complete:
-
-Files: SUMMARY.md, STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md
-
-Key findings:
-- Stack: [one-liner]
-- Architecture: [one-liner]
-- Critical pitfall: [one-liner]
-
----
-## > Next Up
-**Define requirements** - `/gsd:define-requirements`
-<sub>`/clear` first</sub>
----
-```
-
-</process>
-
-<success_criteria>
-- [ ] PROJECT.md validated
-- [ ] Domain identified and approved
-- [ ] 4 gsd-project-researcher agents spawned in parallel
-- [ ] All research files created
-- [ ] SUMMARY.md synthesized with roadmap implications
-- [ ] Research committed
-</success_criteria>

package/get-shit-done/templates/milestone-context.md

@@ -1,93 +0,0 @@
-# Milestone Context Template
-
-Template for `.planning/MILESTONE-CONTEXT.md` - temporary handoff file from discuss-milestone to create-milestone.
-
-**Purpose:** Persist milestone discussion context so `/clear` can be used between commands. This file is consumed by `/gsd:new-milestone` and deleted after the milestone is created.
-
----
-
-## File Template
-
-```markdown
-# Milestone Context
-
-**Generated:** [date]
-**Status:** Ready for /gsd:new-milestone
-
-<features>
-## Features to Build
-
-[Features identified during discussion - the substance of this milestone]
-
-- **[Feature 1]**: [description]
-- **[Feature 2]**: [description]
-- **[Feature 3]**: [description]
-
-</features>
-
-<scope>
-## Scope
-
-**Suggested name:** v[X.Y] [Theme Name]
-**Estimated phases:** [N]
-**Focus:** [One sentence theme/focus]
-
-</scope>
-
-<phase_mapping>
-## Phase Mapping
-
-[How features map to phases - rough breakdown]
-
-- Phase [N]: [Feature/goal]
-- Phase [N+1]: [Feature/goal]
-- Phase [N+2]: [Feature/goal]
-
-</phase_mapping>
-
-<constraints>
-## Constraints
-
-[Any constraints or boundaries mentioned during discussion]
-
-- [Constraint 1]
-- [Constraint 2]
-
-</constraints>
-
-<notes>
-## Additional Context
-
-[Anything else captured during discussion that informs the milestone]
-
-</notes>
-
----
-
-*This file is temporary. It will be deleted after /gsd:new-milestone creates the milestone.*
-```
-
-<guidelines>
-**This is a handoff artifact, not permanent documentation.**
-
-The file exists only to pass context from `discuss-milestone` to `create-milestone` across a `/clear` boundary.
-
-**Lifecycle:**
-1. `/gsd:discuss-milestone` creates this file at end of discussion
-2. User runs `/clear` (safe now - context is persisted)
-3. `/gsd:new-milestone` reads this file
-4. `/gsd:new-milestone` uses context to populate milestone
-5. `/gsd:new-milestone` deletes this file after successful creation
-
-**Content should include:**
-- Features identified (the core of what to build)
-- Suggested milestone name/theme
-- Rough phase mapping
-- Any constraints or scope boundaries
-- Notes from discussion
-
-**Content should NOT include:**
-- Technical analysis (that comes during phase research)
-- Detailed phase specifications (create-milestone handles that)
-- Implementation details
-</guidelines>