pmp-gywd 3.3.0

package/commands/gywd/research-phase.md

@@ -0,0 +1,91 @@
+---
+name: GYWD:research-phase
+description: Research how to implement a phase before planning
+argument-hint: "[phase]"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - WebFetch
+  - WebSearch
+  - mcp__context7__*
+---
+
+<objective>
+Comprehensive research on HOW to implement a phase before planning.
+
+This is for niche/complex domains where Claude's training data is sparse or outdated. Research discovers:
+- What libraries exist for this problem
+- What architecture patterns experts use
+- What the standard stack looks like
+- What problems people commonly hit
+- What NOT to hand-roll (use existing solutions)
+
+Output: RESEARCH.md with ecosystem knowledge that informs quality planning.
+</objective>
+
+<execution_context>
+@~/.claude/get-your-work-done/workflows/research-phase.md
+@~/.claude/get-your-work-done/templates/research.md
+@~/.claude/get-your-work-done/references/research-pitfalls.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+**Load project state:**
+@.planning/STATE.md
+
+**Load roadmap:**
+@.planning/ROADMAP.md
+
+**Load phase context if exists:**
+Check for `.planning/phases/XX-name/{phase}-CONTEXT.md` - bonus context from discuss-phase.
+</context>
+
+<process>
+1. Validate phase number argument (error if missing or invalid)
+2. Check if phase exists in roadmap - extract phase description
+3. Check if RESEARCH.md already exists (offer to update or use existing)
+4. Load CONTEXT.md if it exists (bonus context for research direction)
+5. Follow research-phase.md workflow:
+   - Analyze phase to identify knowledge gaps
+   - Determine research domains (architecture, ecosystem, patterns, pitfalls)
+   - Execute comprehensive research via Context7, official docs, WebSearch
+   - Cross-verify all findings
+   - Create RESEARCH.md with actionable ecosystem knowledge
+6. Offer next steps (plan the phase)
+</process>
+
+<when_to_use>
+**Use research-phase for:**
+- 3D graphics (Three.js, WebGL, procedural generation)
+- Game development (physics, collision, AI, procedural content)
+- Audio/music (Web Audio API, DSP, synthesis)
+- Shaders (GLSL, Metal, ISF)
+- ML/AI integration (model serving, inference, pipelines)
+- Real-time systems (WebSockets, WebRTC, sync)
+- Specialized frameworks with active ecosystems
+- Any domain where "how do experts do this" matters
+
+**Skip research-phase for:**
+- Standard web dev (auth, CRUD, REST APIs)
+- Well-known patterns (forms, validation, testing)
+- Simple integrations (Stripe, SendGrid with clear docs)
+- Commodity features Claude handles well
+</when_to_use>
+
+<success_criteria>
+- [ ] Phase validated against roadmap
+- [ ] Domain/ecosystem identified from phase description
+- [ ] Comprehensive research executed (Context7 + official docs + WebSearch)
+- [ ] All WebSearch findings cross-verified with authoritative sources
+- [ ] RESEARCH.md created with ecosystem knowledge
+- [ ] Standard stack/libraries identified
+- [ ] Architecture patterns documented
+- [ ] Common pitfalls catalogued
+- [ ] What NOT to hand-roll is clear
+- [ ] User knows next steps (plan phase)
+</success_criteria>

package/commands/gywd/resume-work.md

@@ -0,0 +1,40 @@
+---
+name: GYWD:resume-work
+description: Resume work from previous session with full context restoration
+allowed-tools:
+  - Read
+  - Bash
+  - Write
+  - AskUserQuestion
+  - SlashCommand
+---
+
+<objective>
+Restore complete project context and resume work seamlessly from previous session.
+
+Routes to the resume-project workflow which handles:
+
+- STATE.md loading (or reconstruction if missing)
+- Checkpoint detection (.continue-here files)
+- Incomplete work detection (PLAN without SUMMARY)
+- Status presentation
+- Context-aware next action routing
+  </objective>
+
+<execution_context>
+@~/.claude/get-your-work-done/workflows/resume-project.md
+</execution_context>
+
+<process>
+**Follow the resume-project workflow** from `@~/.claude/get-your-work-done/workflows/resume-project.md`.
+
+The workflow handles all resumption logic including:
+
+1. Project existence verification
+2. STATE.md loading or reconstruction
+3. Checkpoint and incomplete work detection
+4. Visual status presentation
+5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
+6. Routing to appropriate next command
+7. Session continuity updates
+   </process>

package/commands/gywd/rollback.md

@@ -0,0 +1,179 @@
+---
+name: GYWD:rollback
+description: Rollback to a previous checkpoint or phase
+argument-hint: "[phase-number|plan-id|'last']"
+---
+
+<objective>
+Safely rollback work to a previous checkpoint when something goes wrong.
+
+Rollback types:
+- **Phase rollback**: Undo entire phase
+- **Plan rollback**: Undo specific plan
+- **Last rollback**: Undo most recent plan
+
+Uses git history to restore code state while preserving planning artifacts for learning.
+</objective>
+
+<context>
+Target: $ARGUMENTS
+
+Options:
+- Phase number: `3` - Rollback to before phase 3
+- Plan ID: `03-02` - Rollback to before plan 03-02
+- `last` - Rollback the most recent plan
+- No args - Interactive selection
+</context>
+
+<process>
+## 1. Parse Target
+
+If no arguments:
+```
+## Rollback Options
+
+Recent checkpoints:
+
+1. [last] Plan 03-02: Payment webhooks (2 hours ago)
+2. [03-01] Plan 03-01: Stripe integration (yesterday)
+3. [phase-2] Phase 2 complete (3 days ago)
+4. [phase-1] Phase 1 complete (1 week ago)
+
+Select: _
+```
+
+## 2. Identify Rollback Point
+
+Find the git commit/tag for the checkpoint:
+- Phases have tags: `gywd-phase-{n}-complete`
+- Plans have commits: Search for `docs({phase}-{plan}): complete`
+
+## 3. Show Impact Analysis
+
+```markdown
+## Rollback Impact: Plan 03-02
+
+**Target:** Before "Payment webhooks" implementation
+**Commit:** abc1234
+**Files affected:** 5
+
+### Changes to Revert
+
+| File | Action | Lines |
+|------|--------|-------|
+| src/webhooks/stripe.ts | DELETE | -120 |
+| src/routes/webhooks.ts | DELETE | -45 |
+| src/services/payment.ts | MODIFY | -30 |
+| tests/webhooks.test.ts | DELETE | -80 |
+| package.json | MODIFY | -2 deps |
+
+### Planning Files
+
+These will be PRESERVED (not rolled back):
+- .planning/phases/03-payment/03-02-PLAN.md
+- .planning/phases/03-payment/03-02-SUMMARY.md (will be updated)
+- .planning/STATE.md (will be updated)
+
+### Confirm Rollback?
+
+This will:
+1. Revert code to commit abc1234
+2. Mark plan 03-02 as "rolled back" in STATE.md
+3. Add rollback note to SUMMARY.md
+4. Create new commit documenting rollback
+
+[Y/n]: _
+```
+
+## 4. Execute Rollback
+
+```bash
+# Create rollback branch for safety
+git checkout -b rollback-03-02-{timestamp}
+
+# Revert changes (keeping history)
+git revert --no-commit abc1234..HEAD
+
+# Commit rollback
+git commit -m "rollback(03-02): revert payment webhooks
+
+Reason: {user-provided or 'Manual rollback requested'}
+
+Rolled back commits:
+- abc1234: feat(03-02): implement webhook handlers
+- def5678: feat(03-02): add webhook tests
+
+Planning artifacts preserved for reference."
+```
+
+## 5. Update Planning State
+
+Update STATE.md:
+```markdown
+## Rollbacks
+
+| Plan | Date | Reason | Branch |
+|------|------|--------|--------|
+| 03-02 | 2024-01-15 | Webhook approach didn't work | rollback-03-02-1705312345 |
+```
+
+Update SUMMARY.md (add note):
+```markdown
+## Rollback Note
+
+**Status:** ROLLED BACK
+**Date:** 2024-01-15
+**Reason:** {reason}
+**Recovery branch:** rollback-03-02-1705312345
+
+The approach in this plan was reverted. See alternative approach in plan 03-03.
+```
+
+## 6. Provide Recovery Options
+
+```markdown
+## Rollback Complete
+
+Code reverted to before plan 03-02.
+
+### Recovery Options
+
+If you need the rolled-back code:
+```
+git checkout rollback-03-02-1705312345
+```
+
+### Next Steps
+
+1. `/gywd:plan-phase 3` - Re-plan this phase
+2. `/gywd:memory add pattern "Webhooks: avoid approach X"` - Remember lesson
+3. Continue with alternative approach
+```
+</process>
+
+<safety_features>
+**Before rollback:**
+- Creates safety branch
+- Shows full impact analysis
+- Requires confirmation
+
+**During rollback:**
+- Uses git revert (preserves history)
+- Never uses --hard reset
+- Keeps planning files
+
+**After rollback:**
+- Documents reason
+- Creates recovery path
+- Updates project state
+</safety_features>
+
+<success_criteria>
+- [ ] Shows clear impact analysis
+- [ ] Creates safety branch before changes
+- [ ] Uses git revert (not reset)
+- [ ] Preserves planning files
+- [ ] Documents rollback reason
+- [ ] Updates STATE.md with rollback record
+- [ ] Provides recovery options
+</success_criteria>

package/commands/gywd/status.md

@@ -0,0 +1,42 @@
+---
+name: GYWD:status
+description: Quick one-line project status check
+---
+
+<objective>
+Display a quick, single-line project status without verbose output.
+
+Perfect for checking where you are at a glance.
+</objective>
+
+<process>
+1. Check if `.planning/` directory exists
+   - If not: Output "No GYWD project initialized. Run /gywd:new-project to start."
+
+2. Check if `.planning/STATE.md` exists
+   - If not: Output "Project exists but no state. Run /gywd:create-roadmap."
+
+3. Read STATE.md and extract:
+   - Current phase number and name
+   - Overall progress percentage
+   - Last activity
+
+4. Output single-line status in format:
+   ```
+   [██████░░░░] 60% | Phase 3/5: Core Features | Last: 2 hours ago
+   ```
+
+5. If issues exist in ISSUES.md, append count:
+   ```
+   [██████░░░░] 60% | Phase 3/5: Core Features | 3 issues pending
+   ```
+</process>
+
+<output_format>
+Single line. No headers. No suggestions. Just status.
+
+Examples:
+- `[░░░░░░░░░░] 0% | Not started | Run /gywd:new-project`
+- `[████░░░░░░] 40% | Phase 2/5: Authentication | Last: today`
+- `[██████████] 100% | Complete | Ready for /gywd:complete-milestone`
+</output_format>

package/commands/gywd/sync-github.md

@@ -0,0 +1,234 @@
+---
+name: GYWD:sync-github
+description: Sync GYWD project state with GitHub issues, PRs, and milestones
+argument-hint: "[issues|prs|milestones|all]"
+---
+
+<objective>
+Bidirectional sync between GYWD planning files and GitHub:
+
+**From GYWD → GitHub:**
+- Create GitHub issues from ISSUES.md
+- Create GitHub milestones from ROADMAP.md
+- Create PRs for completed phases
+
+**From GitHub → GYWD:**
+- Import GitHub issues to ISSUES.md
+- Sync issue status changes
+- Link PR merges to phase completion
+</objective>
+
+<context>
+Sync type: $ARGUMENTS
+
+Options:
+- `issues` - Sync issues bidirectionally
+- `prs` - Create PRs for completed work
+- `milestones` - Sync milestones with GitHub
+- `all` - Full sync (default)
+- `status` - Show sync status without changes
+</context>
+
+<prerequisites>
+Requires:
+- `gh` CLI installed and authenticated
+- Git remote configured to GitHub
+- Repository write access
+</prerequisites>
+
+<process>
+## status (check sync state)
+
+```markdown
+## GitHub Sync Status
+
+**Repository:** cyberbloke9/my-project
+**Last sync:** 2024-01-15 14:30
+
+### Issues
+
+| GYWD | GitHub | Status |
+|------|--------|--------|
+| #1 Auth bug | #12 | ✅ Synced |
+| #2 Performance | #15 | ✅ Synced |
+| #3 New feature | - | ⬆️ Needs push |
+| - | #18 (bug) | ⬇️ Needs import |
+
+### Milestones
+
+| GYWD | GitHub | Status |
+|------|--------|--------|
+| v1.0 MVP | v1.0 | ✅ Synced |
+| v1.1 Features | - | ⬆️ Needs push |
+
+### PRs
+
+| Phase | PR | Status |
+|-------|-----|--------|
+| Phase 1 | #5 | ✅ Merged |
+| Phase 2 | #8 | 🔄 Open |
+| Phase 3 | - | 📋 Ready to create |
+```
+
+## issues
+
+### Push to GitHub
+
+For each issue in ISSUES.md without GitHub link:
+```bash
+gh issue create \
+  --title "Issue title" \
+  --body "Description from ISSUES.md" \
+  --label "from-gywd"
+```
+
+Update ISSUES.md with GitHub issue number:
+```markdown
+## #3 Add dark mode [GitHub: #19]
+
+Status: Open
+Created: 2024-01-15
+...
+```
+
+### Import from GitHub
+
+```bash
+# Get issues labeled for import
+gh issue list --label "needs-planning" --json number,title,body
+```
+
+Add to ISSUES.md:
+```markdown
+## #4 Mobile responsive [GitHub: #20]
+
+Status: Open
+Source: GitHub import
+Priority: Medium
+...
+```
+
+## milestones
+
+### Push to GitHub
+
+```bash
+gh api repos/{owner}/{repo}/milestones \
+  --method POST \
+  -f title="v1.1 Features" \
+  -f description="Phase 4-7 features" \
+  -f due_on="2024-02-01"
+```
+
+### Sync Progress
+
+Update milestone progress based on closed issues:
+```markdown
+## Milestone Sync
+
+v1.0 MVP: 80% complete (8/10 issues closed)
+v1.1 Features: 20% complete (2/10 issues closed)
+```
+
+## prs
+
+### Create PR for Phase
+
+When phase completes, offer to create PR:
+
+```markdown
+## Create PR for Phase 3?
+
+**Branch:** feature/phase-3-payment
+**Target:** main
+**Changes:** 12 files, +450/-20 lines
+
+### Suggested PR Description
+
+## Summary
+- Implemented Stripe payment integration
+- Added webhook handling
+- Created payment history API
+
+## Test Plan
+- [x] Unit tests pass
+- [x] Integration tests pass
+- [ ] Manual checkout flow test
+
+## Related Issues
+Closes #12, #15
+
+---
+
+Create PR? [Y/n]: _
+```
+
+```bash
+gh pr create \
+  --title "feat: Phase 3 - Payment Integration" \
+  --body "..." \
+  --base main \
+  --head feature/phase-3-payment
+```
+
+### Link Merged PRs
+
+When PR merges, update STATE.md:
+```markdown
+## Completed Phases
+
+| Phase | PR | Merged |
+|-------|-----|--------|
+| Phase 1 | #5 | 2024-01-10 |
+| Phase 2 | #8 | 2024-01-12 |
+| Phase 3 | #11 | 2024-01-15 |
+```
+
+## all (full sync)
+
+1. Check status
+2. Push new issues to GitHub
+3. Import new GitHub issues
+4. Sync milestones
+5. Offer to create PRs for completed work
+6. Update sync timestamp
+
+Output:
+```markdown
+## Sync Complete
+
+| Action | Count |
+|--------|-------|
+| Issues pushed | 2 |
+| Issues imported | 1 |
+| Milestones synced | 1 |
+| PRs created | 1 |
+
+Next sync: Run `/gywd:sync-github` anytime
+```
+</process>
+
+<configuration>
+Settings in config.json:
+```json
+{
+  "github": {
+    "auto_sync": false,
+    "import_labels": ["needs-planning", "enhancement"],
+    "export_label": "from-gywd",
+    "create_prs": "prompt",
+    "milestone_sync": true
+  }
+}
+```
+</configuration>
+
+<success_criteria>
+- [ ] Shows current sync status
+- [ ] Pushes local issues to GitHub
+- [ ] Imports GitHub issues locally
+- [ ] Syncs milestones bidirectionally
+- [ ] Creates PRs for completed phases
+- [ ] Updates planning files with GitHub links
+- [ ] Handles auth/permission errors gracefully
+</success_criteria>

package/commands/gywd/verify-work.md

@@ -0,0 +1,71 @@
+---
+name: GYWD:verify-work
+description: Guide manual user acceptance testing of recently built features
+argument-hint: "[optional: phase or plan number, e.g., '4' or '04-02']"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Edit
+  - Write
+  - AskUserQuestion
+---
+
+<objective>
+Guide the user through manual acceptance testing of recently built features.
+
+Purpose: Validate that what Claude thinks was built actually works from the user's perspective. The USER performs all testing — Claude generates the test checklist, guides the process, and captures issues.
+
+Output: Validation of features, any issues logged to phase-scoped ISSUES.md
+</objective>
+
+<execution_context>
+@~/.claude/get-your-work-done/workflows/verify-work.md
+@~/.claude/get-your-work-done/templates/uat-issues.md
+</execution_context>
+
+<context>
+Scope: $ARGUMENTS (optional)
+- If provided: Test specific phase or plan (e.g., "4" or "04-02")
+- If not provided: Test most recently completed plan
+
+**Load project state:**
+@.planning/STATE.md
+
+**Load roadmap:**
+@.planning/ROADMAP.md
+</context>
+
+<process>
+1. Validate arguments (if provided, parse as phase or plan number)
+2. Find relevant SUMMARY.md (specified or most recent)
+3. Follow verify-work.md workflow:
+   - Extract testable deliverables
+   - Generate test checklist
+   - Guide through each test via AskUserQuestion
+   - Collect and categorize issues
+   - Log issues to `.planning/phases/XX-name/{phase}-{plan}-ISSUES.md`
+   - Present summary with verdict
+4. Offer next steps based on results:
+   - If all passed: Continue to next phase
+   - If issues found: `/gywd:plan-fix {phase} {plan}` to create fix plan
+</process>
+
+<anti_patterns>
+- Don't run automated tests (that's for CI/test suites)
+- Don't make assumptions about test results — USER reports outcomes
+- Don't skip the guidance — walk through each test
+- Don't dismiss minor issues — log everything user reports
+- Don't fix issues during testing — capture for later
+</anti_patterns>
+
+<success_criteria>
+- [ ] Test scope identified from SUMMARY.md
+- [ ] Checklist generated based on deliverables
+- [ ] User guided through each test
+- [ ] All test results captured (pass/fail/partial/skip)
+- [ ] Any issues logged to phase-scoped ISSUES.md (not global)
+- [ ] Summary presented with verdict
+- [ ] User knows next steps based on results
+</success_criteria>