@vfarcic/dot-ai 0.106.0 → 0.108.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vfarcic/dot-ai",
-  "version": "0.106.0",
+  "version": "0.108.0",
   "description": "AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance",
   "mcpName": "io.github.vfarcic/dot-ai",
   "main": "dist/index.js",

package/shared-prompts/prd-close.md

@@ -0,0 +1,306 @@
+---
+name: prd-close
+description: Close a PRD that is already implemented or no longer needed
+category: project-management
+---
+
+# Close PRD
+
+Close a PRD that is already implemented (in previous work or external projects) or is no longer needed. This workflow updates the PRD status, archives it, updates the GitHub issue, and commits directly to main without triggering CI.
+
+## When to Use This Command
+
+**Use `/prd-close` when:**
+- ✅ PRD functionality is already implemented in a separate project or previous work
+- ✅ PRD is no longer relevant (superseded, requirements changed, out of scope)
+- ✅ PRD requirements are satisfied by existing functionality
+- ✅ No new code implementation is needed in this repository
+
+**DO NOT use `/prd-close` when:**
+- ❌ You just finished implementing the PRD (use `/prd-done` instead)
+- ❌ PRD has active implementation work in progress
+- ❌ There are uncommitted code changes that need to be part of a PR
+
+## Usage
+
+```bash
+# Interactive mode - will prompt for PRD number and closure reason
+/prd-close
+
+# With PRD number
+/prd-close 20
+
+# With PRD number and reason
+/prd-close 20 "Already implemented by dot-ai-controller"
+```
+
+## Workflow Steps
+
+### Step 1: Identify PRD and Reason
+
+**If PRD number not provided:**
+- Check conversation context for recent PRD discussion
+- Check git branch for PRD indicators (e.g., `feature/prd-X`)
+- If unclear, prompt user for PRD number
+
+**Closure Reason Categories:**
+- **Already Implemented**: Functionality exists in external project or previous work
+- **No Longer Needed**: Requirements changed, out of scope, or superseded
+- **Duplicate**: Another PRD covers the same functionality
+- **Deferred**: Moved to future version or different project
+
+**Required Information:**
+- PRD number
+- Closure reason (brief description)
+- Implementation reference (if already implemented): link to repo, PR, or documentation
+
+### Step 2: Read and Validate PRD
+
+Read the current PRD file from `prds/[number]-*.md`:
+
+**Validation checks:**
+- [ ] PRD file exists and is readable
+- [ ] Confirm with user that this PRD should be closed
+- [ ] Verify closure reason makes sense given PRD content
+- [ ] Ask user for implementation evidence (if "already implemented")
+
+**Present PRD summary to user:**
+```markdown
+## PRD #X: [Title]
+**Status**: [Current Status]
+**Created**: [Date]
+
+**Summary**: [Brief description of what PRD requested]
+
+**Proposed Action**: Close as [reason]
+**Implementation Reference**: [If applicable]
+
+Proceed with closure? (yes/no)
+```
+
+### Step 3: Update PRD File
+
+Update the PRD metadata and add completion work log:
+
+**Metadata Updates:**
+```markdown
+**Status**: Complete [or] No Longer Needed [or] Duplicate
+**Last Updated**: [Current Date]
+**Completed**: [Current Date] [or] **Closed**: [Current Date]
+```
+
+**Add Work Log Entry:**
+```markdown
+### [Date]: PRD Closure - [Reason Category]
+**Duration**: N/A (administrative closure)
+**Status**: [Complete/Closed]
+
+**Closure Summary**:
+[Explain why PRD is being closed]
+
+**Implementation Evidence**: [If applicable]
+[Link to external project, previous PR, or existing functionality]
+
+**Key Points**:
+- [What was requested in original PRD]
+- [How/where it was implemented, or why no longer needed]
+- [Any gaps or differences from original requirements]
+
+[If "Already Implemented"]
+**Functionality Delivered**:
+- [Feature 1] - Implemented in [location/project]
+- [Feature 2] - Implemented in [location/project]
+
+[If "No Longer Needed"]
+**Reason for Closure**:
+- [Why requirements changed]
+- [What superseded this PRD]
+```
+
+### Step 4: Move PRD to Archive
+
+Move the PRD file to the done directory:
+
+```bash
+# Create done directory if it doesn't exist
+mkdir -p prds/done
+
+# Move PRD file
+git mv prds/[number]-[name].md prds/done/
+```
+
+### Step 5: Update GitHub Issue
+
+**Reopen issue temporarily to update:**
+```bash
+gh issue reopen [number]
+```
+
+**Update issue description with new PRD path and status:**
+```bash
+gh issue edit [number] --body "$(cat <<'EOF'
+## PRD: [Title]
+
+**Problem**: [Original problem statement]
+
+**Solution**: [Original solution statement]
+
+**Detailed PRD**: See [prds/done/[number]-[name].md](./prds/done/[number]-[name].md)
+
+**Priority**: [Original Priority]
+
+**Status**: ✅ **[COMPLETE/CLOSED]** - [Brief reason]
+EOF
+)"
+```
+
+### Step 6: Close GitHub Issue
+
+Close the issue with comprehensive closure comment:
+
+```bash
+gh issue close [number] --comment "$(cat <<'EOF'
+## ✅ PRD #[number] Closed - [Reason Category]
+
+[Detailed explanation of why PRD is being closed]
+
+### [If "Already Implemented"]
+**Implementation Details**
+
+This PRD requested [functionality]. **All core requirements are satisfied** by [implementation reference].
+
+| Requirement | Implementation | Status |
+|-------------|----------------|--------|
+| [Requirement 1] | [Where implemented] | ✅ Complete |
+| [Requirement 2] | [Where implemented] | ✅ Complete |
+
+**Implementation Reference**: [Link to project/repo/PR]
+
+[If there are gaps]
+**Not Implemented** (deferred or out of scope):
+- [Feature X] - [Why not needed or deferred]
+
+### [If "No Longer Needed"]
+**Reason for Closure**
+
+[Explain why requirements changed, what superseded this, or why it's out of scope]
+
+**Alternative Approach**: [If applicable]
+[What replaced this PRD or how needs are met differently]
+
+### Files
+
+**PRD Location**: `prds/done/[number]-[name].md`
+**Status**: [Complete/Closed]
+**Closed**: [Date]
+EOF
+)"
+```
+
+### Step 7: Commit and Push
+
+**Commit changes directly to main with skip CI:**
+
+```bash
+# Stage all changes
+git add .
+
+# Verify what will be committed
+git status
+
+# Commit with skip CI flag
+git commit -m "docs(prd-[number]): close PRD #[number] - [brief reason] [skip ci]
+
+- Moved PRD to prds/done/ directory
+- Updated PRD status to [Complete/Closed]
+- Added work log documenting [closure reason]
+- Updated GitHub issue description with new path
+- [Implementation details or reason]
+
+Closes #[number]"
+
+# Push to remote
+git push origin main
+```
+
+**Important**:
+- Always use `[skip ci]` flag to avoid unnecessary CI runs for documentation changes
+- Include issue reference (`Closes #[number]`) to link commit to issue
+
+## Example Scenarios
+
+### Example 1: Already Implemented in External Project
+
+```bash
+/prd-close 20 "Implemented by dot-ai-controller"
+```
+
+**Closure Comment:**
+```markdown
+## ✅ PRD #20 Closed - Already Implemented
+
+This PRD requested proactive Kubernetes cluster monitoring with AI-powered remediation.
+**Core functionality (60-80%) is already implemented** by the separate
+[dot-ai-controller](https://github.com/vfarcic/dot-ai-controller) project.
+
+| Requirement | Implementation | Status |
+|-------------|----------------|--------|
+| Continuous health checks | Event-based monitoring via K8s events | ✅ Complete |
+| Intelligent alerting | Slack notifications with AI analysis | ✅ Complete |
+| Automated remediation | Automatic/manual modes with confidence thresholds | ✅ Complete |
+| Anomaly detection | AI-powered event analysis | ✅ Complete |
+
+**Not Implemented** (advanced features, may be future PRD):
+- Continuous metrics monitoring (Prometheus-style)
+- Predictive analytics with baseline learning
+- Multi-channel alerting (email, PagerDuty)
+```
+
+### Example 2: Duplicate PRD
+
+```bash
+/prd-close 45 "Duplicate of PRD #44"
+```
+
+**Closure Comment:**
+```markdown
+## 🔄 PRD #45 Closed - Duplicate
+
+This PRD covers the same functionality as PRD #44. Consolidating all work
+under PRD #44 to avoid fragmentation.
+
+**Action**: Continue work on PRD #44 instead.
+```
+
+### Example 3: No Longer Needed
+
+```bash
+/prd-close 12 "Requirements changed, out of scope"
+```
+
+**Closure Comment:**
+```markdown
+## ⏸️ PRD #12 Closed - No Longer Needed
+
+After discussion, this approach no longer aligns with project direction.
+Requirements have evolved and this PRD is out of scope.
+
+**Alternative Approach**: Using [different solution/approach] instead.
+```
+
+## Success Criteria
+
+✅ **PRD file updated** with completion/closure metadata and work log
+✅ **PRD archived** to `prds/done/` directory
+✅ **GitHub issue updated** with new PRD path
+✅ **GitHub issue closed** with comprehensive closure comment
+✅ **Changes committed to main** with skip CI flag
+✅ **Changes pushed to remote** repository
+
+## Notes
+
+- **No PR required**: This workflow commits directly to main for documentation-only changes
+- **Skip CI**: Always include `[skip ci]` to avoid unnecessary CI runs
+- **Comprehensive documentation**: Ensure work log and issue comment clearly explain closure
+- **Implementation references**: Link to external projects, repos, or PRs where functionality exists
+- **Gap acknowledgment**: Be honest about what's implemented vs. what's missing

package/shared-prompts/prd-create.md

@@ -116,4 +116,66 @@ Work through the PRD template focusing on project management, milestone tracking
 6. **Milestone Definition**: Define 5-10 major milestones that represent meaningful progress
 7. **Review & Validation**: Ensure completeness and clarity
 
-**CRITICAL**: Steps 2-4 must happen in this exact order to avoid the chicken-and-egg problem of needing the issue ID for the filename.
+**CRITICAL**: Steps 2-4 must happen in this exact order to avoid the chicken-and-egg problem of needing the issue ID for the filename.
+
+## Next Steps After PRD Creation
+
+After completing the PRD, present the user with numbered options:
+
+```
+✅ PRD Created Successfully!
+
+**PRD File**: prds/[issue-id]-[feature-name].md
+**GitHub Issue**: #[issue-id]
+
+What would you like to do next?
+
+**1. Start working on this PRD now**
+   Begin implementation immediately (recommended if you're ready to start)
+
+**2. Commit and push PRD for later**
+   Save the PRD and work on it later (will use [skip ci] flag)
+
+Please enter 1 or 2:
+```
+
+### Option 1: Start Working Now
+
+If user chooses option 1, execute: **prd-start [issue-id]**
+
+This will help identify the first task and set up the development workflow.
+
+### Option 2: Commit and Push for Later
+
+If user chooses option 2:
+
+```bash
+# Stage the PRD file
+git add prds/[issue-id]-[feature-name].md
+
+# Commit with skip CI flag to avoid unnecessary CI runs
+git commit -m "docs(prd-[issue-id]): create PRD #[issue-id] - [feature-name] [skip ci]
+
+- Created PRD for [brief feature description]
+- Defined [X] major milestones
+- Documented problem, solution, and success criteria
+- Ready for implementation"
+
+# Push to main
+git push origin main
+```
+
+**Confirmation Message:**
+```
+✅ PRD committed and pushed to main
+
+The PRD is now available in the repository. To start working on it later, execute:
+prd-start [issue-id]
+```
+
+## Important Notes
+
+- **Option 1**: Best when you have time to begin implementation immediately
+- **Option 2**: Best when creating multiple PRDs or planning future work
+- **Skip CI flag**: Always use `[skip ci]` when committing PRD-only changes
+- **Issue reference**: Include issue number in commit message for traceability