zaileys 2.2.7 → 3.0.0

package/.agent/workflows/check-todos.md

@@ -0,0 +1,80 @@
+---
+description: List all pending todo items
+argument-hint: "[--all] [--priority high|medium|low]"
+---
+
+# /check-todos Workflow
+
+<objective>
+Display pending todo items, optionally filtered by priority or status.
+</objective>
+
+<context>
+**Flags:**
+- `--all` — Show completed items too
+- `--priority high|medium|low` — Filter by priority
+
+**Input:**
+- `.gsd/TODO.md` — Todo items
+</context>
+
+<process>
+
+## 1. Load TODO.md
+
+```powershell
+if (-not (Test-Path ".gsd/TODO.md")) {
+    Write-Output "No todos found. Use /add-todo to create one."
+    exit
+}
+
+Get-Content ".gsd/TODO.md"
+```
+
+---
+
+## 2. Parse and Filter
+
+Count items by status:
+- `- [ ]` = pending
+- `- [x]` = complete
+
+Filter by priority if flag provided.
+
+---
+
+## 3. Display
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► TODOS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+PENDING ({N} items)
+───────────────────
+🔴 {high priority item}
+🟡 {medium priority item}
+🟢 {low priority item}
+
+{If --all flag:}
+COMPLETED ({M} items)
+─────────────────────
+✅ {completed item}
+
+───────────────────────────────────────────────────────
+
+/add-todo <item> — add new item
+
+───────────────────────────────────────────────────────
+```
+
+</process>
+
+<priority_indicators>
+| Priority | Indicator |
+|----------|-----------|
+| high | 🔴 |
+| medium | 🟡 |
+| low | 🟢 |
+| done | ✅ |
+</priority_indicators>

package/.agent/workflows/complete-milestone.md

@@ -0,0 +1,135 @@
+---
+description: Mark current milestone as complete and archive
+---
+
+# /complete-milestone Workflow
+
+<objective>
+Finalize the current milestone, archive documentation, and prepare for next milestone.
+</objective>
+
+<process>
+
+## 1. Verify All Phases Complete
+
+**PowerShell:**
+```powershell
+# Check ROADMAP.md for incomplete phases
+Select-String -Path ".gsd/ROADMAP.md" -Pattern "Status.*Not Started|Status.*In Progress"
+```
+
+**Bash:**
+```bash
+# Check ROADMAP.md for incomplete phases
+grep -E "Status.*Not Started|Status.*In Progress" ".gsd/ROADMAP.md"
+```
+
+**If incomplete phases found:**
+```
+⚠️ Cannot complete milestone — {N} phases incomplete
+
+Run /progress to see status.
+```
+
+---
+
+## 2. Run Final Verification
+
+Verify all must-haves from ROADMAP.md:
+- Run verification commands
+- Capture evidence
+- Create VERIFICATION.md if not exists
+
+---
+
+## 3. Generate Milestone Summary
+
+Create `.gsd/milestones/{name}-SUMMARY.md`:
+
+```markdown
+# Milestone: {name}
+
+## Completed: {date}
+
+## Deliverables
+- ✅ {must-have 1}
+- ✅ {must-have 2}
+
+## Phases Completed
+1. Phase 1: {name} — {date}
+2. Phase 2: {name} — {date}
+...
+
+## Metrics
+- Total commits: {N}
+- Files changed: {M}
+- Duration: {days}
+
+## Lessons Learned
+{Auto-extract from DECISIONS.md and JOURNAL.md}
+```
+
+---
+
+## 4. Archive Current State
+
+**PowerShell:**
+```powershell
+# Create milestone archive
+New-Item -ItemType Directory -Force ".gsd/milestones/{name}"
+
+# Move phase-specific files
+Move-Item ".gsd/phases/*" ".gsd/milestones/{name}/"
+```
+
+**Bash:**
+```bash
+# Create milestone archive
+mkdir -p ".gsd/milestones/{name}"
+
+# Move phase-specific files
+mv .gsd/phases/* ".gsd/milestones/{name}/"
+```
+
+---
+
+## 5. Reset for Next Milestone
+
+Clear ROADMAP.md phases section (keep header).
+Update STATE.md to show milestone complete.
+
+---
+
+## 6. Commit and Tag
+
+```bash
+git add -A
+git commit -m "docs: complete milestone {name}"
+git tag -a "{name}" -m "Milestone {name} complete"
+```
+
+---
+
+## 7. Celebrate
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► MILESTONE COMPLETE 🎉
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{name}
+
+Phases: {N} completed
+Tag: {name}
+
+───────────────────────────────────────────────────────
+
+▶ NEXT
+
+/new-milestone — Start next milestone
+/audit-milestone {name} — Review this milestone
+
+───────────────────────────────────────────────────────
+```
+
+</process>

package/.agent/workflows/debug.md

@@ -0,0 +1,235 @@
+---
+description: Systematic debugging with persistent state
+argument-hint: "[description of issue]"
+---
+
+# /debug Workflow
+
+<role>
+You are a GSD debugger orchestrator. You diagnose and fix issues systematically, leveraging fresh context to see what polluted contexts miss.
+</role>
+
+<objective>
+Systematically diagnose an issue using hypothesis-driven debugging, with persistent state to prevent circular attempts.
+</objective>
+
+<context>
+**Issue:** $ARGUMENTS (description of the problem to debug)
+
+**Skill reference:** `.agent/skills/debugger/SKILL.md`
+</context>
+
+<process>
+
+## 1. Initialize Debug Session
+
+Check for existing debug state:
+**PowerShell:**
+```powershell
+Test-Path ".gsd/DEBUG.md"
+```
+
+**Bash:**
+```bash
+test -f ".gsd/DEBUG.md"
+```
+
+If exists, load previous attempts. If not, create new session.
+
+Display banner:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► DEBUG SESSION
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Issue: {description}
+```
+
+---
+
+## 2. Document Symptom
+
+Create/update `.gsd/DEBUG.md`:
+
+```markdown
+# Debug Session: {Issue ID}
+
+## Symptom
+{Exact description of the problem}
+
+**When:** {When does it occur?}
+**Expected:** {What should happen?}
+**Actual:** {What actually happens?}
+```
+
+---
+
+## 3. Gather Evidence
+
+Collect data BEFORE forming hypotheses:
+
+**PowerShell:**
+```powershell
+# Get error details
+{relevant commands to capture error info}
+
+# Check logs
+Get-Content logs/error.log -Tail 50
+
+# Check environment
+{relevant environment checks}
+```
+
+**Bash:**
+```bash
+# Get error details
+{relevant commands to capture error info}
+
+# Check logs
+tail -50 logs/error.log
+
+# Check environment
+{relevant environment checks}
+```
+
+Document evidence in DEBUG.md.
+
+---
+
+## 4. Form Hypotheses
+
+Based on evidence, list possible causes:
+
+```markdown
+## Hypotheses
+
+| # | Hypothesis | Likelihood | Status |
+|---|------------|------------|--------|
+| 1 | {cause 1} | 80% | UNTESTED |
+| 2 | {cause 2} | 15% | UNTESTED |
+| 3 | {cause 3} | 5% | UNTESTED |
+```
+
+---
+
+## 5. Test Hypotheses
+
+Test highest likelihood first:
+
+```markdown
+## Attempts
+
+### Attempt 1
+**Testing:** H1 — {hypothesis}
+**Action:** {what you did to test}
+**Result:** {outcome}
+**Conclusion:** {CONFIRMED | ELIMINATED | INCONCLUSIVE}
+```
+
+---
+
+## 6. Apply Fix (If Root Cause Found)
+
+When root cause confirmed:
+
+1. Implement fix
+2. Run original failing scenario
+3. Verify PASSES
+4. Check for regressions
+
+Update DEBUG.md:
+```markdown
+## Resolution
+
+**Root Cause:** {what was actually wrong}
+**Fix:** {what was changed}
+**Verified:** {how fix was verified}
+**Regression Check:** {what else was tested}
+```
+
+---
+
+## 7. Handle 3-Strike Rule
+
+If 3 attempts fail on SAME approach:
+
+```
+⚠️ 3 FAILURES ON SAME APPROACH
+
+Action: STOP and reassess
+
+Options:
+1. Try fundamentally DIFFERENT approach
+2. /pause for fresh session context
+3. Ask user for additional information
+```
+
+Update DEBUG.md and recommend next steps.
+
+---
+
+## 8. Commit Resolution
+
+If fixed:
+```bash
+git add -A
+git commit -m "fix: {brief description of fix}"
+```
+
+Update STATE.md with resolution.
+
+</process>
+
+<offer_next>
+
+**If Resolved:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► BUG FIXED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Root cause: {what was wrong}
+Fix: {what was done}
+
+Committed: {hash}
+
+───────────────────────────────────────────────────────
+```
+
+**If Stuck After 3 Attempts:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► DEBUG PAUSED ⏸
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+3 attempts exhausted on current approach.
+State saved to .gsd/DEBUG.md
+
+───────────────────────────────────────────────────────
+
+Options:
+• /debug {issue} — try different approach
+• /pause — save state for fresh session
+• Provide more context about the issue
+
+───────────────────────────────────────────────────────
+```
+
+</offer_next>
+
+<related>
+## Related
+
+### Workflows
+| Command | Relationship |
+|---------|--------------|
+| `/pause` | Use after 3 failed attempts |
+| `/resume` | Start fresh with documented state |
+| `/verify` | Re-verify after fixing issues |
+
+### Skills
+| Skill | Purpose |
+|-------|---------|
+| `debugger` | Detailed debugging methodology |
+| `context-health-monitor` | 3-strike rule |
+</related>

package/.agent/workflows/discuss-phase.md

@@ -0,0 +1,103 @@
+---
+description: Identify gray areas and capture decisions before planning
+argument-hint: "[phase]"
+---
+
+# /discuss-phase Workflow
+
+<role>
+You are an expert technical product manager. You help the user firm up ambiguous requirements before planning begins.
+Your goal is to surface "gray areas" — implementation details that could go multiple ways — and get the user's explicit preference.
+</role>
+
+<objective>
+Analyze the upcoming roadmap phase, identify unstated assumptions or decisions, present options to the user, and record the outcomes in a CONTEXT file for the planner agent.
+</objective>
+
+<context>
+**Phase number:** $ARGUMENTS (optional — auto-detects next unplanned phase from roadmap if missing)
+
+**Required files:**
+- `.gsd/ROADMAP.md`
+- `.gsd/SPEC.md`
+</context>
+
+<process>
+
+## 1. Validate Target Phase
+Look for the phase in `.gsd/ROADMAP.md` (e.g., Phase 2). Extract the goal and description for this phase.
+If the phase doesn't exist, report an error.
+
+## 2. Identify Gray Areas
+Given the phase description and the overarching SPEC, identify 2-4 critical implementation details or UX/UI decisions that are not explicitly stated.
+*Example: For a login page, a gray area could be "Authentication Method" (OAuth vs Email/Password) or "Error Handling UX" (Toasts vs Inline text).*
+
+## 3. Present Gray Areas to the User
+Output a clear, structured question to the user outlining the identified areas and asking for preferences.
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► DISCUSSING PHASE {N}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+I've reviewed Phase {N}: {Phase Name}. Before we create execution plans, we need to clarify a few gray areas.
+
+### 1. {Gray Area 1 Title}
+{Brief explanation of why this matters}
+- Option A: {Description}
+- Option B: {Description}
+
+### 2. {Gray Area 2 Title}
+{Brief explanation of why this matters}
+- Option A: {Description}
+- Option B: {Description}
+
+(Or you can say "You decide" for any of these and I will use my best judgment).
+
+Waiting for your input...
+```
+
+## 4. Capture Decisions
+
+Wait for the user's response. Once received, summarize the decisions.
+
+Ensure the phase directory `.gsd/phases/{N}/` exists, then create or update `.gsd/phases/{N}/{N}-CONTEXT.md`:
+
+```markdown
+# Phase {N} - Context
+
+**Status:** Ready for planning
+
+<decisions>
+## Implementation Decisions
+
+### {Gray Area 1 Title}
+- {User's chosen direction}
+
+### {Gray Area 2 Title}
+- {User's chosen direction}
+
+### Claude's Discretion
+- {Any areas where the user deferred to your judgment}
+</decisions>
+```
+
+## 5. End and Transition
+
+Tell the user that the context is locked in.
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► DECISIONS CAPTURED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Recorded in .gsd/phases/{N}/{N}-CONTEXT.md.
+
+▶ Next Up:
+/plan {N} — create execution plans based on these decisions
+```
+</process>
+
+<offer_next>
+Recommend the `/plan {N}` command to the user so they can proceed immediately.
+</offer_next>