gsd-remix 1.0.2 → 1.1.0

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

@@ -1,365 +0,0 @@
-<purpose>
-
-Interactive command center for managing a milestone from a single terminal. Shows a dashboard of all phases with visual status, dispatches discuss inline and plan/execute as background agents, and loops back to the dashboard after each action. Enables parallel phase work from one terminal.
-
-</purpose>
-
-<required_reading>
-
-Read all files referenced by the invoking prompt's execution_context before starting.
-
-</required_reading>
-
-<process>
-
-<step name="initialize" priority="first">
-
-## 1. Initialize
-
-Bootstrap via manager init:
-
-```bash
-INIT=$(gsd-remix-sdk query init.manager)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Parse JSON for: `milestone_version`, `milestone_name`, `phase_count`, `completed_count`, `in_progress_count`, `phases`, `recommended_actions`, `all_complete`, `waiting_signal`, `manager_flags`.
-
-`manager_flags` contains per-step passthrough flags from config:
-- `manager_flags.discuss` — appended to `/gsd-discuss-phase` args (e.g. `"--auto --analyze"`)
-- `manager_flags.plan` — appended to plan agent init command
-- `manager_flags.execute` — appended to execute agent init command
-
-These are empty strings by default. Set via: `gsd-remix-sdk query config-set manager.flags.discuss "--auto --analyze"`
-
-**If error:** Display the error message and exit.
-
-Display startup banner:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► MANAGER
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
- {milestone_version} — {milestone_name}
- {phase_count} phases · {completed_count} complete
-
- ✓ Discuss → inline    ◆ Plan/Execute → background
- Dashboard auto-refreshes when background work is active.
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-Proceed to dashboard step.
-
-</step>
-
-<step name="dashboard">
-
-## 2. Dashboard (Refresh Point)
-
-**Every time this step is reached**, re-read state from disk to pick up changes from background agents:
-
-```bash
-INIT=$(gsd-remix-sdk query init.manager)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Parse the full JSON. Build the dashboard display.
-
-Build dashboard from JSON. Symbols: `✓` done, `◆` active, `○` pending, `·` queued. Progress bar: 20-char `█░`.
-
-**Status mapping** (disk_status → D P E Status):
-
-- `complete` → `✓ ✓ ✓` `✓ Complete`
-- `partial` → `✓ ✓ ◆` `◆ Executing...`
-- `planned` → `✓ ✓ ○` `○ Ready to execute`
-- `discussed` → `✓ ○ ·` `○ Ready to plan`
-- `researched` → `◆ · ·` `○ Ready to plan`
-- `empty`/`no_directory` + `is_next_to_discuss` → `○ · ·` `○ Ready to discuss`
-- `empty`/`no_directory` otherwise → `· · ·` `· Up next`
-- If `is_active`, replace status icon with `◆` and append `(active)`
-
-If any `is_active` phases, show: `◆ Background: {action} Phase {N}, ...` above grid.
-
-Use `display_name` (not `name`) for the Phase column — it's pre-truncated to 20 chars with `…` if clipped. Pad all phase names to the same width for alignment.
-
-Use `deps_display` from init JSON for the Deps column — shows which phases this phase depends on (e.g. `1,3`) or `—` for none.
-
-Example output:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► DASHBOARD
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- ████████████░░░░░░░░ 60%  (3/5 phases)
- ◆ Background: Planning Phase 4
- | # | Phase                | Deps | D | P | E | Status              |
- |---|----------------------|------|---|---|---|---------------------|
- | 1 | Foundation           | —    | ✓ | ✓ | ✓ | ✓ Complete          |
- | 2 | API Layer            | 1    | ✓ | ✓ | ◆ | ◆ Executing (active)|
- | 3 | Auth System          | 1    | ✓ | ✓ | ○ | ○ Ready to execute  |
- | 4 | Dashboard UI & Set…  | 1,2  | ✓ | ◆ | · | ◆ Planning (active) |
- | 5 | Notifications        | —    | ○ | · | · | ○ Ready to discuss  |
- | 6 | Polish & Final Mail… | 1-5  | · | · | · | · Up next           |
-```
-
-**Recommendations section:**
-
-If `all_complete` is true:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  MILESTONE COMPLETE                                          ║
-╚══════════════════════════════════════════════════════════════╝
-
-All {phase_count} phases done. Ready for final steps:
-  → /gsd-verify-work — run acceptance testing
-  → /gsd-complete-milestone — archive and wrap up
-```
-
-
-**Text mode (`workflow.text_mode: true` in config or `--text` flag):** Set `TEXT_MODE=true` if `--text` is present in `$ARGUMENTS` OR `text_mode` from init JSON is `true`. When TEXT_MODE is active, replace every `AskUserQuestion` call with a plain-text numbered list and ask the user to type their choice number. This is required for non-Claude runtimes (OpenAI Codex, Gemini CLI, etc.) where `AskUserQuestion` is not available.
-Ask user via AskUserQuestion:
-- **question:** "All phases complete. What next?"
-- **options:** "Verify work" / "Complete milestone" / "Exit manager"
-
-Handle responses:
-- "Verify work": `Skill(skill="gsd-verify-work")`  then loop to dashboard.
-- "Complete milestone": `Skill(skill="gsd-complete-milestone")` then exit.
-- "Exit manager": Go to exit step.
-
-**If NOT all_complete**, build compound options from `recommended_actions`:
-
-**Compound option logic:** Group background actions (plan/execute) together, and pair them with the single inline action (discuss) when one exists. The goal is to present the fewest options possible — one option can dispatch multiple background agents plus one inline action.
-
-**Building options:**
-
-1. Collect all background actions (execute and plan recommendations) — there can be multiple of each.
-2. Collect the inline action (discuss recommendation, if any — there will be at most one since discuss is sequential).
-3. Build compound options:
-
-   **If there are ANY recommended actions (background, inline, or both):**
-   Create ONE primary "Continue" option that dispatches ALL of them together:
-   - Label: `"Continue"` — always this exact word
-   - Below the label, list every action that will happen. Enumerate ALL recommended actions — do not cap or truncate:
-     ```
-     Continue:
-       → Execute Phase 32 (background)
-       → Plan Phase 34 (background)
-       → Discuss Phase 35 (inline)
-     ```
-   - This dispatches all background agents first, then runs the inline discuss (if any).
-   - If there is no inline discuss, the dashboard refreshes after spawning background agents.
-
-   **Important:** The Continue option must include EVERY action from `recommended_actions` — not just 2. If there are 3 actions, list 3. If there are 5, list 5.
-
-4. Always add:
-   - `"Refresh dashboard"`
-   - `"Exit manager"`
-
-Display recommendations compactly:
-
-```
-───────────────────────────────────────────────────────────────
-▶ Next Steps
-───────────────────────────────────────────────────────────────
-
-Continue:
-  → Execute Phase 32 (background)
-  → Plan Phase 34 (background)
-  → Discuss Phase 35 (inline)
-```
-
-**Auto-refresh:** If background agents are running (`is_active` is true for any phase), set a 60-second auto-refresh cycle. After presenting the action menu, if no user input is received within 60 seconds, automatically refresh the dashboard. This interval is configurable via `manager_refresh_interval` in GSD config (default: 60 seconds, set to 0 to disable).
-
-Present via AskUserQuestion:
-- **question:** "What would you like to do?"
-- **options:** (compound options as built above + refresh + exit, AskUserQuestion auto-adds "Other")
-
-**On "Other" (free text):** Parse intent — if it mentions a phase number and action, dispatch accordingly. If unclear, display available actions and loop to action_menu.
-
-Proceed to handle_action step with the selected action.
-
-</step>
-
-<step name="handle_action">
-
-## 4. Handle Action
-
-### Refresh Dashboard
-
-Loop back to dashboard step.
-
-### Exit Manager
-
-Go to exit step.
-
-### Compound Action (background + inline)
-
-When the user selects a compound option:
-
-1. **Spawn all background agents first** (plan/execute) — dispatch them in parallel using the Plan Phase N / Execute Phase N handlers below.
-2. **Then run the inline discuss:**
-
-```
-Skill(skill="gsd-discuss-phase", args="{PHASE_NUM} {manager_flags.discuss}")
-```
-
-After discuss completes, loop back to dashboard step (background agents continue running).
-
-### Discuss Phase N
-
-Discussion is interactive — needs user input. Run inline with any configured flags:
-
-```
-Skill(skill="gsd-discuss-phase", args="{PHASE_NUM} {manager_flags.discuss}")
-```
-
-After discuss completes, loop back to dashboard step.
-
-### Plan Phase N
-
-Planning runs autonomously. Spawn a background agent that delegates to the Skill pipeline with any configured flags:
-
-```
-Task(
-  description="Plan phase {N}: {phase_name}",
-  run_in_background=true,
-  prompt="You are running the GSD plan-phase workflow for phase {N} of the project.
-
-Working directory: {cwd}
-Phase: {N} — {phase_name}
-Goal: {goal}
-Manager flags: {manager_flags.plan}
-
-Run the plan-phase Skill with any configured manager flags:
-Skill(skill=\"gsd-plan-phase\", args=\"{N} --auto {manager_flags.plan}\")
-
-This delegates to the full plan-phase pipeline including local patches, research, plan-checker, and all quality gates.
-
-Important: You are running in the background. Do NOT use AskUserQuestion — make autonomous decisions based on project context. If you hit a blocker, write it to STATE.md as a blocker and stop. Do NOT silently work around permission or file access errors — let them fail so the manager can surface them with resolution hints. Do NOT use --no-verify on git commits."
-)
-```
-
-Display:
-
-```
-◆ Spawning planner for Phase {N}: {phase_name}...
-```
-
-Loop back to dashboard step.
-
-### Execute Phase N
-
-Execution runs autonomously. Spawn a background agent that delegates to the Skill pipeline with any configured flags:
-
-```
-Task(
-  description="Execute phase {N}: {phase_name}",
-  run_in_background=true,
-  prompt="You are running the GSD execute-phase workflow for phase {N} of the project.
-
-Working directory: {cwd}
-Phase: {N} — {phase_name}
-Goal: {goal}
-Manager flags: {manager_flags.execute}
-
-Run the execute-phase Skill with any configured manager flags:
-Skill(skill=\"gsd-execute-phase\", args=\"{N} {manager_flags.execute}\")
-
-This delegates to the full execute-phase pipeline including local patches, branching, wave-based execution, verification, and all quality gates.
-
-Important: You are running in the background. Do NOT use AskUserQuestion — make autonomous decisions. Do NOT use --no-verify on git commits — let pre-commit hooks run normally. If you hit a permission error, file lock, or any access issue, do NOT work around it — let it fail and write the error to STATE.md as a blocker so the manager can surface it with resolution guidance."
-)
-```
-
-Display:
-
-```
-◆ Spawning executor for Phase {N}: {phase_name}...
-```
-
-Loop back to dashboard step.
-
-</step>
-
-<step name="background_completion">
-
-## 5. Background Agent Completion
-
-When notified that a background agent completed:
-
-1. Read the result message from the agent.
-2. Display a brief notification:
-
-```
-✓ {description}
-  {brief summary from agent result}
-```
-
-3. Loop back to dashboard step.
-
-**If the agent reported an error or blocker:**
-
-Classify the error:
-
-**Permission / tool access error** (e.g. tool not allowed, permission denied, sandbox restriction):
-- Parse the error to identify which tool or command was blocked.
-- Display the error clearly, then offer to fix it:
-  - **question:** "Phase {N} failed — permission denied for `{tool_or_command}`. Want me to add it to settings.local.json so it's allowed?"
-  - **options:** "Add permission and retry" / "Run this phase inline instead" / "Skip and continue"
-  - "Add permission and retry": Use `Skill(skill="update-config")` to add the permission to `settings.local.json`, then re-spawn the background agent. Loop to dashboard.
-  - "Run this phase inline instead": Dispatch the same action inline via the appropriate Skill — use `Skill(skill="gsd-plan-phase", args="{N}")` if the failed action was planning, or `Skill(skill="gsd-execute-phase", args="{N}")` if the failed action was execution. Loop to dashboard after.
-  - "Skip and continue": Loop to dashboard (phase stays in current state).
-
-**Other errors** (git lock, file conflict, logic error, etc.):
-- Display the error, then offer options via AskUserQuestion:
-  - **question:** "Background agent for Phase {N} encountered an issue: {error}. What next?"
-  - **options:** "Retry" / "Run inline instead" / "Skip and continue" / "View details"
-  - "Retry": Re-spawn the same background agent. Loop to dashboard.
-  - "Run inline instead": Dispatch the action inline via the appropriate Skill — use `Skill(skill="gsd-plan-phase", args="{N}")` if the failed action was planning, or `Skill(skill="gsd-execute-phase", args="{N}")` if the failed action was execution. Loop to dashboard after.
-  - "Skip and continue": Loop to dashboard (phase stays in current state).
-  - "View details": Read STATE.md blockers section, display, then re-present options.
-
-</step>
-
-<step name="exit">
-
-## 6. Exit
-
-Display final status with progress bar:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SESSION END
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
- {milestone_version} — {milestone_name}
- {PROGRESS_BAR} {progress_pct}%  ({completed_count}/{phase_count} phases)
-
- Resume anytime: /gsd-manager
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-**Note:** Any background agents still running will continue to completion. Their results will be visible on next `/gsd-manager` or `/gsd-progress` invocation.
-
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Dashboard displays all phases with correct status indicators (D/P/E/V columns)
-- [ ] Progress bar shows accurate completion percentage
-- [ ] Dependency resolution: blocked phases show which deps are missing
-- [ ] Recommendations prioritize: execute > plan > discuss
-- [ ] Discuss phases run inline via Skill() — interactive questions work
-- [ ] Plan phases spawn background Task agents — return to dashboard immediately
-- [ ] Execute phases spawn background Task agents — return to dashboard immediately
-- [ ] Dashboard refreshes pick up changes from background agents via disk state
-- [ ] Background agent completion triggers notification and dashboard refresh
-- [ ] Background agent errors present retry/skip options
-- [ ] All-complete state offers verify-work and complete-milestone
-- [ ] Exit shows final status with resume instructions
-- [ ] "Other" free-text input parsed for phase number and action
-- [ ] Manager loop continues until user exits or milestone completes
-</success_criteria>

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

@@ -1,223 +0,0 @@
-# Milestone Summary Workflow
-
-Generate a comprehensive, human-friendly project summary from completed milestone artifacts.
-Designed for team onboarding — a new contributor can read the output and understand the entire project.
-
----
-
-## Step 1: Resolve Version
-
-```bash
-VERSION="$ARGUMENTS"
-```
-
-If `$ARGUMENTS` is empty:
-1. Check `.planning/STATE.md` for current milestone version
-2. Check `.planning/milestones/` for the latest archived version
-3. If neither found, check if `.planning/ROADMAP.md` exists (project may be mid-milestone)
-4. If nothing found: error "No milestone found. Run /gsd-new-project or /gsd-new-milestone first."
-
-Set `VERSION` to the resolved version (e.g., "1.0").
-
-## Step 2: Locate Artifacts
-
-Determine whether the milestone is **archived** or **current**:
-
-**Archived milestone** (`.planning/milestones/v{VERSION}-ROADMAP.md` exists):
-```
-ROADMAP_PATH=".planning/milestones/v${VERSION}-ROADMAP.md"
-REQUIREMENTS_PATH=".planning/milestones/v${VERSION}-REQUIREMENTS.md"
-AUDIT_PATH=".planning/milestones/v${VERSION}-MILESTONE-AUDIT.md"
-```
-
-**Current/in-progress milestone** (no archive yet):
-```
-ROADMAP_PATH=".planning/ROADMAP.md"
-REQUIREMENTS_PATH=".planning/REQUIREMENTS.md"
-AUDIT_PATH=".planning/v${VERSION}-MILESTONE-AUDIT.md"
-```
-
-Note: The audit file moves to `.planning/milestones/` on archive (per `complete-milestone` workflow). Check both locations as a fallback.
-
-**Always available:**
-```
-PROJECT_PATH=".planning/PROJECT.md"
-RETRO_PATH=".planning/RETROSPECTIVE.md"
-STATE_PATH=".planning/STATE.md"
-```
-
-Read all files that exist. Missing files are fine — the summary adapts to what's available.
-
-## Step 3: Discover Phase Artifacts
-
-Find all phase directories:
-
-```bash
-gsd-remix-sdk query init.progress
-```
-
-This returns phase metadata. For each phase in the milestone scope:
-
-- Read `{phase_dir}/{padded}-SUMMARY.md` if it exists — extract `one_liner`, `accomplishments`, `decisions`
-- Read `{phase_dir}/{padded}-VERIFICATION.md` if it exists — extract status, gaps, deferred items
-- Read `{phase_dir}/{padded}-CONTEXT.md` if it exists — extract key decisions from `<decisions>` section
-- Read `{phase_dir}/{padded}-RESEARCH.md` if it exists — note what was researched
-
-Track which phases have which artifacts.
-
-**If no phase directories exist** (empty milestone or pre-build state): skip to Step 5 and generate a minimal summary noting "No phases have been executed yet." Do not error — the summary should still capture PROJECT.md and ROADMAP.md content.
-
-## Step 4: Gather Git Statistics
-
-Try each method in order until one succeeds:
-
-**Method 1 — Tagged milestone** (check first):
-```bash
-git tag -l "v${VERSION}" | head -1
-```
-If the tag exists:
-```bash
-git log v${VERSION} --oneline | wc -l
-git diff --stat $(git log --format=%H --reverse v${VERSION} | head -1)..v${VERSION}
-```
-
-**Method 2 — STATE.md date range** (if no tag):
-Read STATE.md and extract the `started_at` or earliest session date. Use it as the `--since` boundary:
-```bash
-git log --oneline --since="<started_at_date>" | wc -l
-```
-
-**Method 3 — Earliest phase commit** (if STATE.md has no date):
-Find the earliest `.planning/phases/` commit:
-```bash
-git log --oneline --diff-filter=A -- ".planning/phases/" | tail -1
-```
-Use that commit's date as the start boundary.
-
-**Method 4 — Skip stats** (if none of the above work):
-Report "Git statistics unavailable — no tag or date range could be determined." This is not an error — the summary continues without the Stats section.
-
-Extract (when available):
-- Total commits in milestone
-- Files changed, insertions, deletions
-- Timeline (start date → end date)
-- Contributors (from git log authors)
-
-## Step 5: Generate Summary Document
-
-Write to `.planning/reports/MILESTONE_SUMMARY-v${VERSION}.md`:
-
-```markdown
-# Milestone v{VERSION} — Project Summary
-
-**Generated:** {date}
-**Purpose:** Team onboarding and project review
-
----
-
-## 1. Project Overview
-
-{From PROJECT.md: "What This Is", core value proposition, target users}
-{If mid-milestone: note which phases are complete vs in-progress}
-
-## 2. Architecture & Technical Decisions
-
-{From CONTEXT.md files across phases: key technical choices}
-{From SUMMARY.md decisions: patterns, libraries, frameworks chosen}
-{From PROJECT.md: tech stack if documented}
-
-Present as a bulleted list of decisions with brief rationale:
-- **Decision:** {what was chosen}
-  - **Why:** {rationale from CONTEXT.md}
-  - **Phase:** {which phase made this decision}
-
-## 3. Phases Delivered
-
-| Phase | Name | Status | One-Liner |
-|-------|------|--------|-----------|
-{For each phase: number, name, status (complete/in-progress/planned), one_liner from SUMMARY.md}
-
-## 4. Requirements Coverage
-
-{From REQUIREMENTS.md: list each requirement with status}
-- ✅ {Requirement met}
-- ⚠️ {Requirement partially met — note gap}
-- ❌ {Requirement not met — note reason}
-
-{If MILESTONE-AUDIT.md exists: include audit verdict}
-
-## 5. Key Decisions Log
-
-{Aggregate from all CONTEXT.md <decisions> sections}
-{Each decision with: ID, description, phase, rationale}
-
-## 6. Tech Debt & Deferred Items
-
-{From VERIFICATION.md files: gaps found, anti-patterns noted}
-{From RETROSPECTIVE.md: lessons learned, what to improve}
-{From CONTEXT.md <deferred> sections: ideas parked for later}
-
-## 7. Getting Started
-
-{Entry points for new contributors:}
-- **Run the project:** {from PROJECT.md or SUMMARY.md}
-- **Key directories:** {from codebase structure}
-- **Tests:** {test command from PROJECT.md or CLAUDE.md}
-- **Where to look first:** {main entry points, core modules}
-
----
-
-## Stats
-
-- **Timeline:** {start} → {end} ({duration})
-- **Phases:** {count complete} / {count total}
-- **Commits:** {count}
-- **Files changed:** {count} (+{insertions} / -{deletions})
-- **Contributors:** {list}
-```
-
-## Step 6: Write and Commit
-
-**Overwrite guard:** If `.planning/reports/MILESTONE_SUMMARY-v${VERSION}.md` already exists, ask the user:
-> "A milestone summary for v{VERSION} already exists. Overwrite it, or view the existing one?"
-If "view": display existing file and skip to Step 8 (interactive mode). If "overwrite": proceed.
-
-Create the reports directory if needed:
-```bash
-mkdir -p .planning/reports
-```
-
-Write the summary, then commit:
-```bash
-gsd-remix-sdk query commit "docs(v${VERSION}): generate milestone summary for onboarding" \
-  ".planning/reports/MILESTONE_SUMMARY-v${VERSION}.md"
-```
-
-## Step 7: Present Summary
-
-Display the full summary document inline.
-
-## Step 8: Offer Interactive Mode
-
-After presenting the summary:
-
-> "Summary written to `.planning/reports/MILESTONE_SUMMARY-v{VERSION}.md`.
->
-> I have full context from the build artifacts. Want to ask anything about the project?
-> Architecture decisions, specific phases, requirements, tech debt — ask away."
-
-If the user asks questions:
-- Answer from the artifacts already loaded (CONTEXT.md, SUMMARY.md, VERIFICATION.md, etc.)
-- Reference specific files and decisions
-- Stay grounded in what was actually built (not speculation)
-
-If the user is done:
-- Suggest next steps: `/gsd-new-milestone`, `/gsd-progress`, or sharing the summary with the team
-
-## Step 9: Update STATE.md
-
-```bash
-gsd-remix-sdk query state.record-session "" \
-  "Milestone v${VERSION} summary generated" \
-  ".planning/reports/MILESTONE_SUMMARY-v${VERSION}.md"
-```