get-shit-done-cc 1.5.27 → 1.5.29

package/get-shit-done/references/principles.md

@@ -1,29 +0,0 @@
-# DEPRECATED: GSD Principles
-
-**This reference has been consolidated into the gsd-planner agent.**
-
-## Migration
-
-Planning expertise is now baked into:
-- `agents/gsd-planner.md` - Section: `<philosophy>`
-
-## Why This Changed
-
-The thin orchestrator pattern consolidates all planning methodology into the agent:
-- Before: Reference files loaded separately (~74 lines)
-- After: Agent has expertise baked in, orchestrator is thin
-
-## Historical Reference
-
-This file previously contained:
-- Solo developer + Claude workflow philosophy
-- "Plans are prompts" principle
-- Scope control and quality degradation curve
-- "Claude automates" and "ship fast" principles
-- Anti-enterprise patterns
-
-All content preserved in `agents/gsd-planner.md`.
-
----
-*Deprecated: 2026-01-16*
-*Replaced by: agents/gsd-planner.md*

package/get-shit-done/references/research-pitfalls.md

@@ -1,233 +0,0 @@
-# Research Pitfalls Reference
-
-## DEPRECATED
-
-**This reference has been consolidated into the gsd-researcher agent.**
-
-The verification protocols and pitfall patterns now live in:
-- `agents/gsd-researcher.md` (section: `<verification_protocol>`)
-
-The content below is preserved for reference but is no longer the primary source.
-
----
-
-*Deprecated: 2026-01-15*
-*Replaced by: agents/gsd-researcher.md*
-
----
-
-<research_pitfalls>
-
-<purpose>
-This document catalogs research mistakes discovered in production use, providing specific patterns to avoid and verification strategies to prevent recurrence.
-</purpose>
-
-<known_pitfalls>
-
-<pitfall_config_scope>
-**What**: Assuming global configuration means no project-scoping exists
-**Example**: Concluding "MCP servers are configured GLOBALLY only" while missing project-scoped `.mcp.json`
-**Why it happens**: Not explicitly checking all known configuration patterns
-**Prevention**:
-```xml
-<verification_checklist>
-**CRITICAL**: Verify ALL configuration scopes:
-- User/global scope - System-wide configuration
-- Project scope - Project-level configuration files
-- Local scope - Project-specific user overrides
-- Workspace scope - IDE/tool workspace settings
-- Environment scope - Environment variables
-</verification_checklist>
-```
-</pitfall_config_scope>
-
-<pitfall_search_vagueness>
-**What**: Asking researchers to "search for documentation" without specifying where
-**Example**: "Research MCP documentation" -> finds outdated community blog instead of official docs
-**Why it happens**: Vague research instructions don't specify exact sources
-**Prevention**:
-```xml
-<sources>
-Official sources (use WebFetch):
-- https://exact-url-to-official-docs
-- https://exact-url-to-api-reference
-
-Search queries (use WebSearch):
-- "specific search query {current_year}"
-- "another specific query {current_year}"
-</sources>
-```
-</pitfall_search_vagueness>
-
-<pitfall_deprecated_features>
-**What**: Finding archived/old documentation and concluding feature doesn't exist
-**Example**: Finding 2022 docs saying "feature not supported" when current version added it
-**Why it happens**: Not checking multiple sources or recent updates
-**Prevention**:
-```xml
-<verification_checklist>
-- Check current official documentation
-- Review changelog/release notes for recent updates
-- Verify version numbers and publication dates
-- Cross-reference multiple authoritative sources
-</verification_checklist>
-```
-</pitfall_deprecated_features>
-
-<pitfall_tool_variations>
-**What**: Conflating capabilities across different tools/environments
-**Example**: "Claude Desktop supports X" does not mean "Claude Code supports X"
-**Why it happens**: Not explicitly checking each environment separately
-**Prevention**:
-```xml
-<verification_checklist>
-- Claude Desktop capabilities
-- Claude Code capabilities
-- VS Code extension capabilities
-- API/SDK capabilities
-Document which environment supports which features
-</verification_checklist>
-```
-</pitfall_tool_variations>
-
-<pitfall_negative_claims>
-**What**: Making definitive "X is not possible" statements without official source verification
-**Example**: "Folder-scoped MCP configuration is not supported" (missing `.mcp.json`)
-**Why it happens**: Drawing conclusions from absence of evidence rather than evidence of absence
-**Prevention**:
-```xml
-<critical_claims_audit>
-For any "X is not possible" or "Y is the only way" statement:
-- [ ] Is this verified by official documentation stating it explicitly?
-- [ ] Have I checked for recent updates that might change this?
-- [ ] Have I verified all possible approaches/mechanisms?
-- [ ] Am I confusing "I didn't find it" with "it doesn't exist"?
-</critical_claims_audit>
-```
-</pitfall_negative_claims>
-
-<pitfall_missing_enumeration>
-**What**: Investigating open-ended scope without enumerating known possibilities first
-**Example**: "Research configuration options" instead of listing specific options to verify
-**Why it happens**: Not creating explicit checklist of items to investigate
-**Prevention**:
-```xml
-<verification_checklist>
-Enumerate ALL known options FIRST:
-- Option 1: [specific item]
-- Option 2: [specific item]
-- Option 3: [specific item]
-- Check for additional unlisted options
-
-For each option above, document:
-- Existence (confirmed/not found/unclear)
-- Official source URL
-- Current status (active/deprecated/beta)
-</verification_checklist>
-```
-</pitfall_missing_enumeration>
-
-<pitfall_single_source>
-**What**: Relying on a single source for critical claims
-**Example**: Using only Stack Overflow answer from 2021 for current best practices
-**Why it happens**: Not cross-referencing multiple authoritative sources
-**Prevention**:
-```xml
-<source_verification>
-For critical claims, require multiple sources:
-- [ ] Official documentation (primary)
-- [ ] Release notes/changelog (for currency)
-- [ ] Additional authoritative source (for verification)
-- [ ] Contradiction check (ensure sources agree)
-</source_verification>
-```
-</pitfall_single_source>
-
-<pitfall_assumed_completeness>
-**What**: Assuming search results are complete and authoritative
-**Example**: First Google result is outdated but assumed current
-**Why it happens**: Not verifying publication dates and source authority
-**Prevention**:
-```xml
-<source_verification>
-For each source consulted:
-- [ ] Publication/update date verified (prefer recent/current)
-- [ ] Source authority confirmed (official docs, not blogs)
-- [ ] Version relevance checked (matches current version)
-- [ ] Multiple search queries tried (not just one)
-</source_verification>
-```
-</pitfall_assumed_completeness>
-</known_pitfalls>
-
-<red_flags>
-
-<red_flag_zero_not_found>
-**Warning**: Every investigation succeeds perfectly
-**Problem**: Real research encounters dead ends, ambiguity, and unknowns
-**Action**: Expect honest reporting of limitations, contradictions, and gaps
-</red_flag_zero_not_found>
-
-<red_flag_no_confidence>
-**Warning**: All findings presented as equally certain
-**Problem**: Can't distinguish verified facts from educated guesses
-**Action**: Require confidence levels (High/Medium/Low) for key findings
-</red_flag_no_confidence>
-
-<red_flag_missing_urls>
-**Warning**: "According to documentation..." without specific URL
-**Problem**: Can't verify claims or check for updates
-**Action**: Require actual URLs for all official documentation claims
-</red_flag_missing_urls>
-
-<red_flag_no_evidence>
-**Warning**: "X cannot do Y" or "Z is the only way" without citation
-**Problem**: Strong claims require strong evidence
-**Action**: Flag for verification against official sources
-</red_flag_no_evidence>
-
-<red_flag_incomplete_enum>
-**Warning**: Verification checklist lists 4 items, output covers 2
-**Problem**: Systematic gaps in coverage
-**Action**: Ensure all enumerated items addressed or marked "not found"
-</red_flag_incomplete_enum>
-</red_flags>
-
-<continuous_improvement>
-
-When research gaps occur:
-
-1. **Document the gap**
-   - What was missed or incorrect?
-   - What was the actual correct information?
-   - What was the impact?
-
-2. **Root cause analysis**
-   - Why wasn't it caught?
-   - Which verification step would have prevented it?
-   - What pattern does this reveal?
-
-3. **Update this document**
-   - Add new pitfall entry
-   - Update relevant checklists
-   - Share lesson learned
-</continuous_improvement>
-
-<quick_reference>
-
-Before submitting research, verify:
-
-- [ ] All enumerated items investigated (not just some)
-- [ ] Negative claims verified with official docs
-- [ ] Multiple sources cross-referenced for critical claims
-- [ ] URLs provided for all official documentation
-- [ ] Publication dates checked (prefer recent/current)
-- [ ] Tool/environment-specific variations documented
-- [ ] Confidence levels assigned honestly
-- [ ] Assumptions distinguished from verified facts
-- [ ] "What might I have missed?" review completed
-
-**Living Document**: Update after each significant research gap
-**Lessons From**: MCP configuration research gap (missed `.mcp.json`)
-</quick_reference>
-</research_pitfalls>

package/get-shit-done/references/scope-estimation.md

@@ -1,32 +0,0 @@
-# DEPRECATED: Scope Estimation Reference
-
-**This reference has been consolidated into the gsd-planner agent.**
-
-## Migration
-
-Planning expertise is now baked into:
-- `agents/gsd-planner.md` - Section: `<scope_estimation>`
-
-## Why This Changed
-
-The thin orchestrator pattern consolidates all planning methodology into the agent:
-- Before: Reference files loaded separately (~257 lines)
-- After: Agent has expertise baked in, orchestrator is thin
-
-## Historical Reference
-
-This file previously contained:
-- Quality degradation curve (0-30%, 30-50%, 50-70%, 70%+)
-- Context budget targets (~50%)
-- Task-per-plan rules (2-3 tasks)
-- Split signals (always split, consider splitting)
-- Splitting strategies (vertical slices preferred)
-- Dependency awareness and wave assignment
-- File ownership for parallel execution
-- Depth calibration (quick, standard, comprehensive)
-
-All content preserved in `agents/gsd-planner.md`.
-
----
-*Deprecated: 2026-01-16*
-*Replaced by: agents/gsd-planner.md*

package/get-shit-done/templates/research-subagent-prompt.md

@@ -1,92 +0,0 @@
-# Research Subagent Prompt Template
-
-Template for spawning gsd-researcher agent. The agent contains all research expertise - this template provides research context only.
-
----
-
-## Template
-
-```markdown
-<objective>
-Research: {research_question}
-
-Mode: {research_mode}
-</objective>
-
-<context>
-**Phase:** {phase_number} - {phase_name}
-**Description:** {phase_description}
-
-**Requirements:**
-{phase_requirements}
-
-**Constraints:**
-{constraints_from_state}
-
-**Phase context (if available):**
-{context_md_content}
-</context>
-
-<output>
-Write research findings to: {output_path}
-Use RESEARCH.md template structure for phase research.
-</output>
-```
-
----
-
-## Placeholders
-
-| Placeholder | Source | Example |
-|-------------|--------|---------|
-| `{research_question}` | Phase description | `How to implement 3D visualization` |
-| `{research_mode}` | Orchestrator sets | `ecosystem` |
-| `{phase_number}` | From roadmap | `5` |
-| `{phase_name}` | From roadmap | `3d-visualization` |
-| `{phase_description}` | From roadmap | `Add interactive 3D model viewer` |
-| `{phase_requirements}` | From REQUIREMENTS.md | `VIZ-01: Support GLB format` |
-| `{constraints_from_state}` | From STATE.md decisions | `Using React, not Vue` |
-| `{context_md_content}` | From CONTEXT.md | User's vision notes |
-| `{output_path}` | Generated | `.planning/phases/5-viz/5-RESEARCH.md` |
-
----
-
-## Usage
-
-**From /gsd:research-phase:**
-```python
-Task(
-  prompt=filled_template,
-  subagent_type="gsd-researcher",
-  description="Research Phase {phase}"
-)
-```
-
----
-
-## Continuation
-
-For checkpoints, spawn fresh agent with:
-
-```markdown
-<objective>
-Continue research for Phase {phase_number}: {phase_name}
-</objective>
-
-<prior_state>
-Research file: @{output_path}
-</prior_state>
-
-<checkpoint_response>
-**Type:** {checkpoint_type}
-**Response:** {user_response}
-</checkpoint_response>
-
-<mode>
-Continue: {research_mode}
-</mode>
-```
-
----
-
-**Note:** Research methodology, tool strategy (Context7 > Official > WebSearch), and verification protocols are baked into the gsd-researcher agent. This template only passes context.

package/get-shit-done/workflows/create-milestone.md

@@ -1,203 +0,0 @@
-<purpose>
-Start a new milestone cycle by updating PROJECT.md with new goals.
-
-This is the brownfield equivalent of new-project. The project exists and has history.
-This workflow gathers "what's next" and updates PROJECT.md, then routes to the
-requirements → roadmap cycle.
-</purpose>
-
-<required_reading>
-**Read these files NOW:**
-
-1. ~/.claude/get-shit-done/references/questioning.md
-2. ~/.claude/get-shit-done/templates/project.md
-3. `.planning/PROJECT.md`
-4. `.planning/MILESTONES.md` (if exists)
-5. `.planning/STATE.md`
-</required_reading>
-
-<process>
-
-<step name="load_context">
-Load project context:
-
-```bash
-cat .planning/PROJECT.md
-cat .planning/MILESTONES.md 2>/dev/null || echo "No milestones file yet"
-cat .planning/STATE.md
-cat .planning/MILESTONE-CONTEXT.md 2>/dev/null || echo "No milestone context file"
-cat .planning/config.json 2>/dev/null
-```
-
-Extract:
-- What shipped previously (from MILESTONES.md)
-- Current Validated requirements (from PROJECT.md)
-- Pending todos and blockers (from STATE.md)
-- Any context from discuss-milestone (MILESTONE-CONTEXT.md)
-
-**Calculate next milestone version:**
-- Parse last version from MILESTONES.md
-- If v1.0 → suggest v1.1 (minor) or v2.0 (major)
-- If v1.3 → suggest v1.4 or v2.0
-</step>
-
-<step name="gather_goals">
-**If MILESTONE-CONTEXT.md exists (from /gsd:discuss-milestone):**
-- Use features and scope already gathered
-- Present summary for confirmation
-- Skip to confirm_goals step
-
-**If no context file:**
-
-Present what shipped:
-```
-Last milestone: v[X.Y] [Name]
-Key accomplishments:
-- [From MILESTONES.md]
-
-Validated so far:
-- [From PROJECT.md Validated section]
-
-Pending todos:
-- [From STATE.md if any]
-```
-
-Ask (freeform, not AskUserQuestion):
-"What do you want to build in the next milestone?"
-
-Wait for response. Then use AskUserQuestion to explore:
-- Probe specific features mentioned
-- Ask about priorities
-- Surface constraints or dependencies
-- Clarify scope boundaries
-
-Continue until you have clear milestone goals.
-</step>
-
-<step name="confirm_goals">
-Present gathered goals:
-
-```
-Milestone: v[X.Y] [Name]
-
-Goal: [One sentence focus]
-
-Target features:
-- [Feature 1]
-- [Feature 2]
-- [Feature 3]
-
-Ready to update PROJECT.md? (yes / adjust)
-```
-
-If "adjust": return to gather_goals.
-</step>
-
-<step name="update_project">
-Update `.planning/PROJECT.md`:
-
-**Add Current Milestone section** (after Core Value, before Requirements):
-
-```markdown
-## Current Milestone: v[X.Y] [Name]
-
-**Goal:** [One sentence describing milestone focus]
-
-**Target features:**
-- [Feature 1]
-- [Feature 2]
-- [Feature 3]
-```
-
-**Update Active requirements:**
-- Add new milestone goals to Active section
-- Keep existing Active items that weren't addressed
-- Don't remove anything from Validated
-
-**Update footer:**
-```markdown
----
-*Last updated: [date] after v[X.Y] milestone start*
-```
-</step>
-
-<step name="update_state">
-Update `.planning/STATE.md`:
-
-```markdown
-## Current Position
-
-Phase: Not started (run /gsd:create-roadmap)
-Plan: —
-Status: Defining requirements
-Last activity: [today] — Milestone v[X.Y] started
-
-Progress: ░░░░░░░░░░ 0%
-```
-
-Keep Accumulated Context (decisions, blockers) from previous milestone.
-</step>
-
-<step name="cleanup">
-Delete temporary context file if it exists:
-
-```bash
-rm -f .planning/MILESTONE-CONTEXT.md
-```
-</step>
-
-<step name="git_commit">
-```bash
-git add .planning/PROJECT.md .planning/STATE.md
-git commit -m "$(cat <<'EOF'
-docs: start milestone v[X.Y] [Name]
-
-Goal: [One sentence]
-Target features: [count] features
-EOF
-)"
-```
-</step>
-
-<step name="offer_next">
-```
-Milestone v[X.Y] [Name] initialized.
-
-PROJECT.md updated with:
-- Current Milestone section
-- Target features in Active requirements
-
----
-
-## ▶ Next Up
-
-**Define Requirements** — scope v[X.Y] features into REQUIREMENTS.md
-
-`/gsd:define-requirements`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Or research first:**
-- `/gsd:research-project` — investigate ecosystem before scoping
-
-**Full flow:**
-1. `/gsd:define-requirements` — create REQUIREMENTS.md
-2. `/gsd:create-roadmap` — create ROADMAP.md with phases
-3. `/gsd:plan-phase [N]` — start execution
-
----
-```
-</step>
-
-</process>
-
-<success_criteria>
-- PROJECT.md updated with Current Milestone section
-- Active requirements reflect new milestone goals
-- STATE.md reset for new milestone (keeps accumulated context)
-- MILESTONE-CONTEXT.md consumed and deleted (if existed)
-- Git commit made
-- User routed to define-requirements (or research-project)
-</success_criteria>

package/get-shit-done/workflows/debug.md

@@ -1,14 +0,0 @@
-# Debug Workflow (DEPRECATED)
-
-This workflow has been consolidated into the `gsd-debugger` agent.
-
-**Location:** `agents/gsd-debugger.md`
-
-**Reason:** The gsd-debugger agent contains all debugging expertise. Loading a separate workflow into orchestrator context was wasteful.
-
-**Migration:**
-- `/gsd:debug` now spawns `gsd-debugger` agent directly
-- All debugging methodology lives in the agent file
-- Templates remain at `get-shit-done/templates/DEBUG.md`
-
-See `agents/gsd-debugger.md` for debugging expertise.

package/get-shit-done/workflows/plan-phase.md

@@ -1,41 +0,0 @@
-# DEPRECATED: Plan-Phase Workflow
-
-**This workflow has been consolidated into the gsd-planner agent.**
-
-## Migration
-
-Planning expertise is now baked into:
-- `agents/gsd-planner.md` - Complete planning methodology
-
-The `/gsd:plan-phase` command spawns the gsd-planner agent directly.
-
-## Why This Changed
-
-The thin orchestrator pattern reduces main context usage:
-- Before: ~3,580 lines loaded into main context
-- After: ~150 lines in orchestrator, expertise in agent
-
-## Historical Reference
-
-This file previously contained:
-- Decimal phase numbering rules
-- Required reading list (8 reference files)
-- Planning principles and philosophy
-- Discovery level definitions (Level 0-3)
-- Project history assembly via frontmatter dependency graph
-- Gap closure mode process
-- Task breakdown with TDD detection
-- Dependency graph building
-- Wave assignment algorithm
-- Plan grouping rules
-- Scope estimation and depth calibration
-- Phase prompt writing (PLAN.md structure)
-- User setup frontmatter for external services
-- Git commit step
-- Success criteria (standard and gap closure modes)
-
-All content preserved in `agents/gsd-planner.md`.
-
----
-*Deprecated: 2026-01-16*
-*Replaced by: agents/gsd-planner.md*

package/get-shit-done/workflows/research-phase.md

@@ -1,17 +0,0 @@
-# Research Phase Workflow
-
-## DEPRECATED
-
-**This workflow has been consolidated into the gsd-researcher agent.**
-
-The research methodology, tool strategy, source hierarchy, and verification protocols now live in:
-- `agents/gsd-researcher.md`
-
-The `/gsd:research-phase` command spawns the gsd-researcher agent directly.
-
-**Migration:** No action needed - the command handles this automatically.
-
----
-
-*Deprecated: 2026-01-15*
-*Replaced by: agents/gsd-researcher.md*

package/get-shit-done/workflows/research-project.md

@@ -1,23 +0,0 @@
-# Research Project Workflow
-
-## DEPRECATED
-
-**This workflow has been consolidated into the gsd-researcher agent.**
-
-The research methodology for project research now lives in:
-- `agents/gsd-researcher.md`
-
-The `/gsd:research-project` command spawns 4 parallel gsd-researcher agents:
-- Stack agent -> .planning/research/STACK.md
-- Features agent -> .planning/research/FEATURES.md
-- Architecture agent -> .planning/research/ARCHITECTURE.md
-- Pitfalls agent -> .planning/research/PITFALLS.md
-
-The orchestrator synthesizes SUMMARY.md after all agents complete.
-
-**Migration:** No action needed - the command handles this automatically.
-
----
-
-*Deprecated: 2026-01-15*
-*Replaced by: agents/gsd-researcher.md*