pi-gsd 1.0.3

package/skills/gsd-thread/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: gsd-thread
+description: Manage persistent context threads for cross-session work
+---
+
+<objective>
+Create, list, or resume persistent context threads. Threads are lightweight
+cross-session knowledge stores for work that spans multiple sessions but
+doesn't belong to any specific phase.
+</objective>
+
+<process>
+
+**Parse $ARGUMENTS to determine mode:**
+
+<mode_list>
+**If no arguments or $ARGUMENTS is empty:**
+
+List all threads:
+
+```bash
+ls .planning/threads/*.md 2>/dev/null
+```
+
+For each thread, read the first few lines to show title and status:
+
+```
+## Active Threads
+
+| Thread | Status | Last Updated |
+|--------|--------|-------------|
+| fix-deploy-key-auth | OPEN | 2026-03-15 |
+| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
+| perf-investigation | IN PROGRESS | 2026-03-17 |
+```
+
+If no threads exist, show:
+
+```
+No threads found. Create one with: /gsd-thread <description>
+```
+
+</mode_list>
+
+<mode_resume>
+**If $ARGUMENTS matches an existing thread name (file exists):**
+
+Resume the thread - load its context into the current session:
+
+```bash
+cat ".planning/threads/${THREAD_NAME}.md"
+```
+
+Display the thread content and ask what the user wants to work on next.
+Update the thread's status to `IN PROGRESS` if it was `OPEN`.
+</mode_resume>
+
+<mode_create>
+**If $ARGUMENTS is a new description (no matching thread file):**
+
+Create a new thread:
+
+1. Generate slug from description:
+
+   ```bash
+   SLUG=$(node ".agent/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS")
+   ```
+
+2. Create the threads directory if needed:
+
+   ```bash
+   mkdir -p .planning/threads
+   ```
+
+3. Write the thread file:
+
+   ```bash
+   cat > ".planning/threads/${SLUG}.md" << 'EOF'
+   # Thread: {description}
+
+   ## Status: OPEN
+
+   ## Goal
+
+   {description}
+
+   ## Context
+
+   *Created from conversation on {today's date}.*
+
+   ## References
+
+   - *(add links, file paths, or issue numbers)*
+
+   ## Next Steps
+
+   - *(what the next session should do first)*
+   EOF
+   ```
+
+4. If there's relevant context in the current conversation (code snippets,
+   error messages, investigation results), extract and add it to the Context
+   section.
+
+5. Commit:
+
+   ```bash
+   node ".agent/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread - ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
+   ```
+
+6. Report:
+
+   ```
+   ## 🧵 Thread Created
+
+   Thread: {slug}
+   File: .planning/threads/{slug}.md
+
+   Resume anytime with: /gsd-thread {slug}
+   ```
+
+   </mode_create>
+
+</process>
+
+<notes>
+- Threads are NOT phase-scoped - they exist independently of the roadmap
+- Lighter weight than /gsd-pause-work - no phase state, no plan context
+- The value is in Context and Next Steps - a cold-start session can pick up immediately
+- Threads can be promoted to phases or backlog items when they mature:
+  /gsd-add-phase or /gsd-add-backlog with context from the thread
+- Thread files live in .planning/threads/ - no collision with phases or other GSD structures
+</notes>

package/skills/gsd-ui-phase/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: gsd-ui-phase
+description: Generate UI design contract (UI-SPEC.md) for frontend phases
+---
+
+<objective>
+Create a UI design contract (UI-SPEC.md) for a frontend phase.
+Orchestrates gsd-ui-researcher and gsd-ui-checker.
+Flow: Validate → Research UI → Verify UI-SPEC → Done
+</objective>
+
+<execution_context>
+@.agent/get-shit-done/workflows/ui-phase.md
+@.agent/get-shit-done/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS - optional, auto-detects next unplanned phase if omitted.
+</context>
+
+<process>
+Execute @.agent/get-shit-done/workflows/ui-phase.md end-to-end.
+Preserve all workflow gates.
+</process>

package/skills/gsd-ui-review/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: gsd-ui-review
+description: Retroactive 6-pillar visual audit of implemented frontend code
+---
+
+<objective>
+Conduct a retroactive 6-pillar visual audit. Produces UI-REVIEW.md with
+graded assessment (1-4 per pillar). Works on any project.
+Output: {phase_num}-UI-REVIEW.md
+</objective>
+
+<execution_context>
+@.agent/get-shit-done/workflows/ui-review.md
+@.agent/get-shit-done/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS - optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @.agent/get-shit-done/workflows/ui-review.md end-to-end.
+Preserve all workflow gates.
+</process>

package/skills/gsd-update/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: gsd-update
+description: Update GSD to latest version with changelog display
+---
+
+
+<objective>
+Check for GSD updates, install if available, and display what changed.
+
+Routes to the update workflow which handles:
+- Version detection (local vs global installation)
+- npm version checking
+- Changelog fetching and display
+- User confirmation with clean install warning
+- Update execution and cache clearing
+- Restart reminder
+</objective>
+
+<execution_context>
+@.agent/get-shit-done/workflows/update.md
+</execution_context>
+
+<process>
+**Follow the update workflow** from `@.agent/get-shit-done/workflows/update.md`.
+
+The workflow handles all logic including:
+1. Installed version detection (local/global)
+2. Latest version checking via npm
+3. Version comparison
+4. Changelog fetching and extraction
+5. Clean install warning display
+6. User confirmation
+7. Update execution
+8. Cache clearing
+</process>

package/skills/gsd-validate-phase/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: gsd-validate-phase
+description: Retroactively audit and fill Nyquist validation gaps for a completed phase
+---
+
+<objective>
+Audit Nyquist validation coverage for a completed phase. Three states:
+- (A) VALIDATION.md exists - audit and fill gaps
+- (B) No VALIDATION.md, SUMMARY.md exists - reconstruct from artifacts
+- (C) Phase not executed - exit with guidance
+
+Output: updated VALIDATION.md + generated test files.
+</objective>
+
+<execution_context>
+@.agent/get-shit-done/workflows/validate-phase.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS - optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @.agent/get-shit-done/workflows/validate-phase.md.
+Preserve all workflow gates.
+</process>

package/skills/gsd-verify-work/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: gsd-verify-work
+description: Validate built features through conversational UAT
+---
+
+<objective>
+Validate built features through conversational testing with persistent state.
+
+Purpose: Confirm what the agent built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
+
+Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase
+</objective>
+
+<execution_context>
+@.agent/get-shit-done/workflows/verify-work.md
+@.agent/get-shit-done/templates/UAT.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS (optional)
+- If provided: Test specific phase (e.g., "4")
+- If not provided: Check for active sessions or prompt for phase
+
+Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
+</context>
+
+<process>
+Execute the verify-work workflow from @.agent/get-shit-done/workflows/verify-work.md end-to-end.
+Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
+</process>

package/skills/gsd-workstreams/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: gsd-workstreams
+description: Manage parallel workstreams - list, create, switch, status, progress, complete, and resume
+---
+
+# /gsd-workstreams
+
+Manage parallel workstreams for concurrent milestone work.
+
+## Usage
+
+`/gsd-workstreams [subcommand] [args]`
+
+### Subcommands
+
+| Command           | Description                             |
+| ----------------- | --------------------------------------- |
+| `list`            | List all workstreams with status        |
+| `create <name>`   | Create a new workstream                 |
+| `status <name>`   | Detailed status for one workstream      |
+| `switch <name>`   | Set active workstream                   |
+| `progress`        | Progress summary across all workstreams |
+| `complete <name>` | Archive a completed workstream          |
+| `resume <name>`   | Resume work in a workstream             |
+
+## Step 1: Parse Subcommand
+
+Parse the user's input to determine which workstream operation to perform.
+If no subcommand given, default to `list`.
+
+## Step 2: Execute Operation
+
+### list
+
+Run: `node "$GSD_TOOLS" workstream list --raw --cwd "$CWD"`
+Display the workstreams in a table format showing name, status, current phase, and progress.
+
+### create
+
+Run: `node "$GSD_TOOLS" workstream create <name> --raw --cwd "$CWD"`
+After creation, display the new workstream path and suggest next steps:
+
+- `/gsd-new-milestone --ws <name>` to set up the milestone
+
+### status
+
+Run: `node "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"`
+Display detailed phase breakdown and state information.
+
+### switch
+
+Run: `node "$GSD_TOOLS" workstream set <name> --raw --cwd "$CWD"`
+Also set `GSD_WORKSTREAM` env var for the current session.
+
+### progress
+
+Run: `node "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"`
+Display a progress overview across all workstreams.
+
+### complete
+
+Run: `node "$GSD_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
+Archive the workstream to milestones/.
+
+### resume
+
+Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
+
+## Step 3: Display Results
+
+Format the JSON output from gsd-tools into a human-readable display.
+Include the `${GSD_WS}` flag in any routing suggestions.