gsd-trae 1.0.1 → 1.0.2

package/refs/gsd/get-shit-done/workflows/audit-milestone.md

@@ -1,297 +0,0 @@
-<purpose>
-Verify milestone achieved its definition of done by aggregating phase verifications, checking cross-phase integration, and assessing requirements coverage. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-## 0. Initialize Milestone Context
-
-```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs init milestone-op)
-```
-
-Extract from init JSON: `milestone_version`, `milestone_name`, `phase_count`, `completed_phases`, `commit_docs`.
-
-Resolve integration checker model:
-```bash
-CHECKER_MODEL=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs resolve-model gsd-integration-checker --raw)
-```
-
-## 1. Determine Milestone Scope
-
-```bash
-# Get phases in milestone (sorted numerically, handles decimals)
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs phases list
-```
-
-- Parse version from arguments or detect current from ROADMAP.md
-- Identify all phase directories in scope
-- Extract milestone definition of done from ROADMAP.md
-- Extract requirements mapped to this milestone from REQUIREMENTS.md
-
-## 2. Read All Phase Verifications
-
-For each phase directory, read the VERIFICATION.md:
-
-```bash
-# For each phase, use find-phase to resolve the directory (handles archived phases)
-PHASE_INFO=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs find-phase 01 --raw)
-# Extract directory from JSON, then read VERIFICATION.md from that directory
-# Repeat for each phase number from ROADMAP.md
-```
-
-From each VERIFICATION.md, extract:
-- **Status:** passed | gaps_found
-- **Critical gaps:** (if any — these are blockers)
-- **Non-critical gaps:** tech debt, deferred items, warnings
-- **Anti-patterns found:** TODOs, stubs, placeholders
-- **Requirements coverage:** which requirements satisfied/blocked
-
-If a phase is missing VERIFICATION.md, flag it as "unverified phase" — this is a blocker.
-
-## 3. Spawn Integration Checker
-
-With phase context collected:
-
-Extract `MILESTONE_REQ_IDS` from REQUIREMENTS.md traceability table — all REQ-IDs assigned to phases in this milestone.
-
-```
-Task(
-  prompt="Check cross-phase integration and E2E flows.
-
-Phases: {phase_dirs}
-Phase exports: {from SUMMARYs}
-API routes: {routes created}
-
-Milestone Requirements:
-{MILESTONE_REQ_IDS — list each REQ-ID with description and assigned phase}
-
-MUST map each integration finding to affected requirement IDs where applicable.
-
-Verify cross-phase wiring and E2E user flows.",
-  subagent_type="gsd-integration-checker",
-  model="{integration_checker_model}"
-)
-```
-
-## 4. Collect Results
-
-Combine:
-- Phase-level gaps and tech debt (from step 2)
-- Integration checker's report (wiring gaps, broken flows)
-
-## 5. Check Requirements Coverage (3-Source Cross-Reference)
-
-MUST cross-reference three independent sources for each requirement:
-
-### 5a. Parse REQUIREMENTS.md Traceability Table
-
-Extract all REQ-IDs mapped to milestone phases from the traceability table:
-- Requirement ID, description, assigned phase, current status, checked-off state (`[x]` vs `[ ]`)
-
-### 5b. Parse Phase VERIFICATION.md Requirements Tables
-
-For each phase's VERIFICATION.md, extract the expanded requirements table:
-- Requirement | Source Plan | Description | Status | Evidence
-- Map each entry back to its REQ-ID
-
-### 5c. Extract SUMMARY.md Frontmatter Cross-Check
-
-For each phase's SUMMARY.md, extract `requirements-completed` from YAML frontmatter:
-```bash
-for summary in .planning/phases/*-*/*-SUMMARY.md; do
-  node ~/.claude/get-shit-done/bin/gsd-tools.cjs summary-extract "$summary" --fields requirements_completed | jq -r '.requirements_completed'
-done
-```
-
-### 5d. Status Determination Matrix
-
-For each REQ-ID, determine status using all three sources:
-
-| VERIFICATION.md Status | SUMMARY Frontmatter | REQUIREMENTS.md | → Final Status |
-|------------------------|---------------------|-----------------|----------------|
-| passed                 | listed              | `[x]`           | **satisfied**  |
-| passed                 | listed              | `[ ]`           | **satisfied** (update checkbox) |
-| passed                 | missing             | any             | **partial** (verify manually) |
-| gaps_found             | any                 | any             | **unsatisfied** |
-| missing                | listed              | any             | **partial** (verification gap) |
-| missing                | missing             | any             | **unsatisfied** |
-
-### 5e. FAIL Gate and Orphan Detection
-
-**REQUIRED:** Any `unsatisfied` requirement MUST force `gaps_found` status on the milestone audit.
-
-**Orphan detection:** Requirements present in REQUIREMENTS.md traceability table but absent from ALL phase VERIFICATION.md files MUST be flagged as orphaned. Orphaned requirements are treated as `unsatisfied` — they were assigned but never verified by any phase.
-
-## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
-
-Create `.planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
-
-```yaml
----
-milestone: {version}
-audited: {timestamp}
-status: passed | gaps_found | tech_debt
-scores:
-  requirements: N/M
-  phases: N/M
-  integration: N/M
-  flows: N/M
-gaps:  # Critical blockers
-  requirements:
-    - id: "{REQ-ID}"
-      status: "unsatisfied | partial | orphaned"
-      phase: "{assigned phase}"
-      claimed_by_plans: ["{plan files that reference this requirement}"]
-      completed_by_plans: ["{plan files whose SUMMARY marks it complete}"]
-      verification_status: "passed | gaps_found | missing | orphaned"
-      evidence: "{specific evidence or lack thereof}"
-  integration: [...]
-  flows: [...]
-tech_debt:  # Non-critical, deferred
-  - phase: 01-auth
-    items:
-      - "TODO: add rate limiting"
-      - "Warning: no password strength validation"
-  - phase: 03-dashboard
-    items:
-      - "Deferred: mobile responsive layout"
----
-```
-
-Plus full markdown report with tables for requirements, phases, integration, tech debt.
-
-**Status values:**
-- `passed` — all requirements met, no critical gaps, minimal tech debt
-- `gaps_found` — critical blockers exist
-- `tech_debt` — no blockers but accumulated deferred items need review
-
-## 7. Present Results
-
-Route by status (see `<offer_next>`).
-
-</process>
-
-<offer_next>
-Output this markdown directly (not as a code block). Route based on status:
-
----
-
-**If passed:**
-
-## ✓ Milestone {version} — Audit Passed
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements covered. Cross-phase integration verified. E2E flows complete.
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Complete milestone** — archive and tag
-
-/gsd:complete-milestone {version}
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If gaps_found:**
-
-## ⚠ Milestone {version} — Gaps Found
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-### Unsatisfied Requirements
-
-{For each unsatisfied requirement:}
-- **{REQ-ID}: {description}** (Phase {X})
-  - {reason}
-
-### Cross-Phase Issues
-
-{For each integration gap:}
-- **{from} → {to}:** {issue}
-
-### Broken Flows
-
-{For each flow gap:}
-- **{flow name}:** breaks at {step}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Plan gap closure** — create phases to complete milestone
-
-/gsd:plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
-- /gsd:complete-milestone {version} — proceed anyway (accept tech debt)
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If tech_debt (no blockers but accumulated debt):**
-
-## ⚡ Milestone {version} — Tech Debt Review
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements met. No critical blockers. Accumulated tech debt needs review.
-
-### Tech Debt by Phase
-
-{For each phase with debt:}
-**Phase {X}: {name}**
-- {item 1}
-- {item 2}
-
-### Total: {N} items across {M} phases
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Options
-
-**A. Complete milestone** — accept debt, track in backlog
-
-/gsd:complete-milestone {version}
-
-**B. Plan cleanup phase** — address debt before completing
-
-/gsd:plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-</offer_next>
-
-<success_criteria>
-- [ ] Milestone scope identified
-- [ ] All phase VERIFICATION.md files read
-- [ ] SUMMARY.md `requirements-completed` frontmatter extracted for each phase
-- [ ] REQUIREMENTS.md traceability table parsed for all milestone REQ-IDs
-- [ ] 3-source cross-reference completed (VERIFICATION + SUMMARY + traceability)
-- [ ] Orphaned requirements detected (in traceability but absent from all VERIFICATIONs)
-- [ ] Tech debt and deferred gaps aggregated
-- [ ] Integration checker spawned with milestone requirement IDs
-- [ ] v{version}-MILESTONE-AUDIT.md created with structured requirement gap objects
-- [ ] FAIL gate enforced — any unsatisfied requirement forces gaps_found status
-- [ ] Results presented with actionable next steps
-</success_criteria>

package/refs/gsd/get-shit-done/workflows/check-todos.md

@@ -1,176 +0,0 @@
-<purpose>
-List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="init_context">
-Load todo context:
-
-```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs init todos)
-```
-
-Extract from init JSON: `todo_count`, `todos`, `pending_dir`.
-
-If `todo_count` is 0:
-```
-No pending todos.
-
-Todos are captured during work sessions with /gsd:add-todo.
-
----
-
-Would you like to:
-
-1. Continue with current phase (/gsd:progress)
-2. Add a todo now (/gsd:add-todo)
-```
-
-Exit.
-</step>
-
-<step name="parse_filter">
-Check for area filter in arguments:
-- `/gsd:check-todos` → show all
-- `/gsd:check-todos api` → filter to area:api only
-</step>
-
-<step name="list_todos">
-Use the `todos` array from init context (already filtered by area if specified).
-
-Parse and display as numbered list:
-
-```
-Pending Todos:
-
-1. Add auth token refresh (api, 2d ago)
-2. Fix modal z-index issue (ui, 1d ago)
-3. Refactor database connection pool (database, 5h ago)
-
----
-
-Reply with a number to view details, or:
-- `/gsd:check-todos [area]` to filter by area
-- `q` to exit
-```
-
-Format age as relative time from created timestamp.
-</step>
-
-<step name="handle_selection">
-Wait for user to reply with a number.
-
-If valid: load selected todo, proceed.
-If invalid: "Invalid selection. Reply with a number (1-[N]) or `q` to exit."
-</step>
-
-<step name="load_context">
-Read the todo file completely. Display:
-
-```
-## [title]
-
-**Area:** [area]
-**Created:** [date] ([relative time] ago)
-**Files:** [list or "None"]
-
-### Problem
-[problem section content]
-
-### Solution
-[solution section content]
-```
-
-If `files` field has entries, read and briefly summarize each.
-</step>
-
-<step name="check_roadmap">
-Check for roadmap (can use init progress or directly check file existence):
-
-If `.planning/ROADMAP.md` exists:
-1. Check if todo's area matches an upcoming phase
-2. Check if todo's files overlap with a phase's scope
-3. Note any match for action options
-</step>
-
-<step name="offer_actions">
-**If todo maps to a roadmap phase:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "This todo relates to Phase [N]: [name]. What would you like to do?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Add to phase plan" — include when planning Phase [N]
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-
-**If no roadmap match:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "What would you like to do with this todo?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Create a phase" — /gsd:add-phase with this scope
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-</step>
-
-<step name="execute_action">
-**Work on it now:**
-```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
-```
-Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
-
-**Add to phase plan:**
-Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
-
-**Create a phase:**
-Display: `/gsd:add-phase [description from todo]`
-Keep in pending. User runs command in fresh context.
-
-**Brainstorm approach:**
-Keep in pending. Start discussion about problem and approaches.
-
-**Put it back:**
-Return to list_todos step.
-</step>
-
-<step name="update_state">
-After any action that changes todo count:
-
-Re-run `init todos` to get updated count, then update STATE.md "### Pending Todos" section if exists.
-</step>
-
-<step name="git_commit">
-If todo was moved to done/, commit the change:
-
-```bash
-git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs: start work on todo - [title]" --files .planning/todos/done/[filename] .planning/STATE.md
-```
-
-Tool respects `commit_docs` config and gitignore automatically.
-
-Confirm: "Committed: docs: start work on todo - [title]"
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] All pending todos listed with title, area, age
-- [ ] Area filter applied if specified
-- [ ] Selected todo's full context loaded
-- [ ] Roadmap context checked for phase match
-- [ ] Appropriate actions offered
-- [ ] Selected action executed
-- [ ] STATE.md updated if todo count changed
-- [ ] Changes committed to git (if todo moved to done/)
-</success_criteria>

package/refs/gsd/get-shit-done/workflows/cleanup.md

@@ -1,152 +0,0 @@
-<purpose>
-
-Archive accumulated phase directories from completed milestones into `.planning/milestones/v{X.Y}-phases/`. Identifies which phases belong to each completed milestone, shows a dry-run summary, and moves directories on confirmation.
-
-</purpose>
-
-<required_reading>
-
-1. `.planning/MILESTONES.md`
-2. `.planning/milestones/` directory listing
-3. `.planning/phases/` directory listing
-
-</required_reading>
-
-<process>
-
-<step name="identify_completed_milestones">
-
-Read `.planning/MILESTONES.md` to identify completed milestones and their versions.
-
-```bash
-cat .planning/MILESTONES.md
-```
-
-Extract each milestone version (e.g., v1.0, v1.1, v2.0).
-
-Check which milestone archive dirs already exist:
-
-```bash
-ls -d .planning/milestones/v*-phases 2>/dev/null
-```
-
-Filter to milestones that do NOT already have a `-phases` archive directory.
-
-If all milestones already have phase archives:
-
-```
-All completed milestones already have phase directories archived. Nothing to clean up.
-```
-
-Stop here.
-
-</step>
-
-<step name="determine_phase_membership">
-
-For each completed milestone without a `-phases` archive, read the archived ROADMAP snapshot to determine which phases belong to it:
-
-```bash
-cat .planning/milestones/v{X.Y}-ROADMAP.md
-```
-
-Extract phase numbers and names from the archived roadmap (e.g., Phase 1: Foundation, Phase 2: Auth).
-
-Check which of those phase directories still exist in `.planning/phases/`:
-
-```bash
-ls -d .planning/phases/*/ 2>/dev/null
-```
-
-Match phase directories to milestone membership. Only include directories that still exist in `.planning/phases/`.
-
-</step>
-
-<step name="show_dry_run">
-
-Present a dry-run summary for each milestone:
-
-```
-## Cleanup Summary
-
-### v{X.Y} — {Milestone Name}
-These phase directories will be archived:
-- 01-foundation/
-- 02-auth/
-- 03-core-features/
-
-Destination: .planning/milestones/v{X.Y}-phases/
-
-### v{X.Z} — {Milestone Name}
-These phase directories will be archived:
-- 04-security/
-- 05-hardening/
-
-Destination: .planning/milestones/v{X.Z}-phases/
-```
-
-If no phase directories remain to archive (all already moved or deleted):
-
-```
-No phase directories found to archive. Phases may have been removed or archived previously.
-```
-
-Stop here.
-
-AskUserQuestion: "Proceed with archiving?" with options: "Yes — archive listed phases" | "Cancel"
-
-If "Cancel": Stop.
-
-</step>
-
-<step name="archive_phases">
-
-For each milestone, move phase directories:
-
-```bash
-mkdir -p .planning/milestones/v{X.Y}-phases
-```
-
-For each phase directory belonging to this milestone:
-
-```bash
-mv .planning/phases/{dir} .planning/milestones/v{X.Y}-phases/
-```
-
-Repeat for all milestones in the cleanup set.
-
-</step>
-
-<step name="commit">
-
-Commit the changes:
-
-```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "chore: archive phase directories from completed milestones" --files .planning/milestones/ .planning/phases/
-```
-
-</step>
-
-<step name="report">
-
-```
-Archived:
-{For each milestone}
-- v{X.Y}: {N} phase directories → .planning/milestones/v{X.Y}-phases/
-
-.planning/phases/ cleaned up.
-```
-
-</step>
-
-</process>
-
-<success_criteria>
-
-- [ ] All completed milestones without existing phase archives identified
-- [ ] Phase membership determined from archived ROADMAP snapshots
-- [ ] Dry-run summary shown and user confirmed
-- [ ] Phase directories moved to `.planning/milestones/v{X.Y}-phases/`
-- [ ] Changes committed
-
-</success_criteria>