@vfarcic/dot-ai 0.145.1 → 0.147.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vfarcic/dot-ai",
3
- "version": "0.145.1",
3
+ "version": "0.147.0",
4
4
  "description": "AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance",
5
5
  "mcpName": "io.github.vfarcic/dot-ai",
6
6
  "main": "dist/index.js",
@@ -34,6 +34,8 @@ Close a PRD that is already implemented (in previous work or external projects)
34
34
  /prd-close 20 "Already implemented by dot-ai-controller"
35
35
  ```
36
36
 
37
+ **Note**: If any `gh` command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
38
+
37
39
  ## Workflow Steps
38
40
 
39
41
  ### Step 1: Identify PRD and Reason
@@ -122,13 +124,11 @@ Update the PRD metadata and add completion work log:
122
124
  Move the PRD file to the done directory and update roadmap:
123
125
 
124
126
  ```bash
125
- # Create done directory if it doesn't exist
126
- mkdir -p prds/done
127
-
128
- # Move PRD file
129
127
  git mv prds/[number]-[name].md prds/done/
130
128
  ```
131
129
 
130
+ **Note**: If the move fails because `prds/done/` doesn't exist, create it with `mkdir -p prds/done` and retry.
131
+
132
132
  **Update ROADMAP.md (if it exists):**
133
133
  - [ ] Check if `docs/ROADMAP.md` exists
134
134
  - [ ] Remove the closed PRD from the roadmap (search for "PRD #[number]")
@@ -106,6 +106,8 @@ Work through the PRD template focusing on project management, milestone tracking
106
106
  - **Focus on major milestones**: Create 5-10 meaningful milestones rather than exhaustive micro-tasks
107
107
  - **Think cross-functionally**: Consider impact on different teams, systems, and stakeholders
108
108
 
109
+ **Note**: If any `gh` command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
110
+
109
111
  ## Workflow
110
112
 
111
113
  1. **Concept Discussion**: Get the basic idea and validate the need
@@ -118,7 +120,7 @@ Work through the PRD template focusing on project management, milestone tracking
118
120
 
119
121
  **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.
120
122
 
121
- ### Step 5: Update ROADMAP.md (If It Exists)
123
+ ## Update ROADMAP.md (If It Exists)
122
124
 
123
125
  After creating the PRD, check if `docs/ROADMAP.md` exists. If it does, add the new feature to the appropriate timeframe section based on PRD priority:
124
126
  - **High Priority** → Short-term section
@@ -8,6 +8,8 @@ category: project-management
8
8
 
9
9
  Complete the PRD implementation workflow including branch management, pull request creation, and issue closure.
10
10
 
11
+ **Note**: If any `gh` command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
12
+
11
13
  ## Workflow Steps
12
14
 
13
15
  ### 0. Implementation Type Detection
@@ -8,6 +8,8 @@ category: project-management
8
8
 
9
9
  Fetch all open GitHub issues from this project that have the 'PRD' label.
10
10
 
11
+ **Note**: If any `gh` command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
12
+
11
13
  ## Process
12
14
 
13
15
  1. **Fetch Issues**: Use GitHub CLI to get all open issues with PRD label