prjct-cli 0.33.5 → 0.35.0

package/templates/commands/bug.md

@@ -10,6 +10,8 @@ backend-sync: 'sync/pending.json'
 
 # /p:bug - Report Bug with Auto-Start
 
+**ARGUMENTS**: $ARGUMENTS
+
 ## Usage
 
 ```

package/templates/commands/github.md

@@ -5,6 +5,8 @@ description: 'GitHub Issues integration via MCP'
 
 # p. github - GitHub Issues Integration
 
+**ARGUMENTS**: $ARGUMENTS
+
 Manage GitHub Issues directly from prjct using MCP.
 
 ## Context Variables
@@ -50,17 +52,65 @@ IF file not found:
 
 ---
 
-## Step 2: Check MCP Tools
+## Step 2: Check GITHUB_TOKEN
+
+```
+CHECK: Is GITHUB_TOKEN env var set?
+
+IF not set:
+  OUTPUT: "GitHub requires a Personal Access Token."
+  OUTPUT: ""
+  OUTPUT: "1. Create token at: https://github.com/settings/tokens"
+  OUTPUT: "2. Select 'repo' scope"
+  OUTPUT: "3. Set env var: export GITHUB_TOKEN=ghp_..."
+  OUTPUT: "4. Run `p. github setup` again"
+  STOP
+```
+
+---
+
+## Step 3: Install MCP Server (if needed)
+
+```
+READ: ~/.claude/settings.json (create {} if not exists)
+CHECK: Does mcpServers.github exist?
+
+IF not exists:
+  READ: templates/mcp-config.json
+  EXTRACT: mcpServers.github
+
+  MERGE into ~/.claude/settings.json:
+  {
+    "mcpServers": {
+      "github": {
+        "command": "npx",
+        "args": ["-y", "@modelcontextprotocol/server-github"],
+        "env": {
+          "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
+        }
+      }
+    }
+  }
+
+  WRITE: ~/.claude/settings.json
+
+  OUTPUT: "✅ Installed GitHub MCP server"
+  OUTPUT: ""
+  OUTPUT: "⚠️ Restart Claude Code to activate the MCP server."
+  OUTPUT: "Then run `p. github setup` again to complete configuration."
+  STOP
+```
+
+---
+
+## Step 4: Check MCP Tools Available
 
 ```
 CHECK: Are mcp__github__* tools available?
 
 IF not available:
-  OUTPUT: "GitHub MCP not configured."
-  OUTPUT: "1. Set GITHUB_TOKEN env var (needs repo scope)"
-  OUTPUT: "2. Add to ~/.claude/settings.json:"
-  OUTPUT: '{"mcpServers":{"github":{"command":"npx","args":["-y","@modelcontextprotocol/server-github"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"${GITHUB_TOKEN}"}}}}'
-  OUTPUT: "3. Restart Claude Code."
+  OUTPUT: "GitHub MCP is installed but not yet active."
+  OUTPUT: "Restart Claude Code, then run `p. github setup` again."
   STOP
 ```
 
@@ -70,7 +120,13 @@ IF not available:
 
 ### Flow
 
-1. **Verify MCP tools available**
+1. **Check token + Install MCP + Verify tools**
+   ```
+   Execute Step 2 (check GITHUB_TOKEN)
+   Execute Step 3 (auto-install MCP if needed)
+   Execute Step 4 (verify tools active)
+   IF not available: Prompt restart and STOP
+   ```
 
 2. **Detect repo from git remote**
    ```bash

package/templates/commands/jira.md

@@ -5,6 +5,8 @@ description: 'JIRA issue tracker integration'
 
 # p. jira - JIRA Integration
 
+**ARGUMENTS**: $ARGUMENTS
+
 Manage JIRA issues directly from prjct.
 
 ## Context Variables
@@ -68,7 +70,38 @@ IF file not found:
 
 ---
 
-## Step 2: Detect Auth Mode
+## Step 2: Install MCP Server (if needed)
+
+```
+READ: ~/.claude/settings.json (create {} if not exists)
+CHECK: Does mcpServers.Atlassian exist?
+
+IF not exists:
+  READ: templates/mcp-config.json
+  EXTRACT: mcpServers.Atlassian
+
+  MERGE into ~/.claude/settings.json:
+  {
+    "mcpServers": {
+      "Atlassian": {
+        "command": "npx",
+        "args": ["-y", "mcp-remote@latest", "https://mcp.atlassian.com/v1/sse"]
+      }
+    }
+  }
+
+  WRITE: ~/.claude/settings.json
+
+  OUTPUT: "✅ Installed Atlassian MCP server"
+  OUTPUT: ""
+  OUTPUT: "⚠️ Restart Claude Code to activate the MCP server."
+  OUTPUT: "Then run `p. jira setup` again to complete configuration."
+  STOP
+```
+
+---
+
+## Step 3: Detect Auth Mode
 
 ```
 # Check API Token first
@@ -79,6 +112,12 @@ IF JIRA_API_TOKEN is set:
 ELSE IF mcp__atlassian__jira_* tools available:
   SET: authMode = "mcp"
 
+# MCP installed but not active
+ELSE IF mcpServers.Atlassian exists in settings.json:
+  OUTPUT: "Atlassian MCP is installed but not yet active."
+  OUTPUT: "Restart Claude Code, then run `p. jira setup` again."
+  STOP
+
 # Neither available
 ELSE:
   OUTPUT: "JIRA not configured. Run `p. jira setup` first."
@@ -91,10 +130,11 @@ ELSE:
 
 ### Flow
 
-1. **Detect available auth methods**
+1. **Install MCP + Detect auth mode**
    ```
-   CHECK: JIRA_API_TOKEN env var
-   CHECK: Atlassian MCP tools available
+   Execute Step 2 (auto-install MCP if needed)
+   Execute Step 3 (detect auth mode)
+   IF MCP not active: Prompt restart and STOP
    ```
 
 2. **If MCP available (preferred)**

package/templates/commands/linear.md

@@ -5,6 +5,8 @@ description: 'Linear issue tracker integration via MCP'
 
 # p. linear - Linear Integration
 
+**ARGUMENTS**: $ARGUMENTS
+
 Manage Linear issues directly from prjct using MCP (no SDK needed).
 
 ## Context Variables
@@ -50,16 +52,45 @@ IF file not found:
 
 ---
 
-## Step 2: Check MCP Tools
+## Step 2: Install MCP Server (if needed)
+
+```
+READ: ~/.claude/settings.json (create {} if not exists)
+CHECK: Does mcpServers.linear exist?
+
+IF not exists:
+  READ: templates/mcp-config.json
+  EXTRACT: mcpServers.linear
+
+  MERGE into ~/.claude/settings.json:
+  {
+    "mcpServers": {
+      "linear": {
+        "command": "npx",
+        "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"]
+      }
+    }
+  }
+
+  WRITE: ~/.claude/settings.json
+
+  OUTPUT: "✅ Installed Linear MCP server"
+  OUTPUT: ""
+  OUTPUT: "⚠️ Restart Claude Code to activate the MCP server."
+  OUTPUT: "Then run `p. linear setup` again to complete configuration."
+  STOP
+```
+
+---
+
+## Step 3: Check MCP Tools Available
 
 ```
 CHECK: Are mcp__linear__* tools available?
 
 IF not available:
-  OUTPUT: "Linear MCP not configured."
-  OUTPUT: "Add to ~/.claude/settings.json or .mcp.json:"
-  OUTPUT: '{"mcpServers":{"linear":{"command":"npx","args":["-y","mcp-remote","https://mcp.linear.app/mcp"]}}}'
-  OUTPUT: "Then restart Claude Code."
+  OUTPUT: "Linear MCP is installed but not yet active."
+  OUTPUT: "Restart Claude Code, then run `p. linear setup` again."
   STOP
 ```
 
@@ -69,10 +100,11 @@ IF not available:
 
 ### Flow
 
-1. **Verify MCP tools available**
+1. **Install MCP + Verify tools available**
    ```
-   CHECK: mcp__linear__* tools exist
-   IF not: Show MCP config instructions, STOP
+   Execute Step 2 (auto-install if needed)
+   Execute Step 3 (verify tools active)
+   IF not available: Prompt restart and STOP
    ```
 
 2. **Test connection (triggers OAuth if needed)**

package/templates/commands/monday.md

@@ -5,6 +5,8 @@ description: 'Monday.com issue tracker integration via MCP'
 
 # p. monday - Monday.com Integration
 
+**ARGUMENTS**: $ARGUMENTS
+
 Manage Monday.com boards directly from prjct using MCP.
 
 ## Context Variables
@@ -49,16 +51,45 @@ IF file not found:
 
 ---
 
-## Step 2: Check MCP Tools
+## Step 2: Install MCP Server (if needed)
+
+```
+READ: ~/.claude/settings.json (create {} if not exists)
+CHECK: Does mcpServers.monday exist?
+
+IF not exists:
+  READ: templates/mcp-config.json
+  EXTRACT: mcpServers.monday
+
+  MERGE into ~/.claude/settings.json:
+  {
+    "mcpServers": {
+      "monday": {
+        "command": "npx",
+        "args": ["-y", "@mondaydotcomorg/monday-api-mcp"]
+      }
+    }
+  }
+
+  WRITE: ~/.claude/settings.json
+
+  OUTPUT: "✅ Installed Monday.com MCP server"
+  OUTPUT: ""
+  OUTPUT: "⚠️ Restart Claude Code to activate the MCP server."
+  OUTPUT: "Then run `p. monday setup` again to complete configuration."
+  STOP
+```
+
+---
+
+## Step 3: Check MCP Tools Available
 
 ```
 CHECK: Are mcp__monday__* tools available?
 
 IF not available:
-  OUTPUT: "Monday MCP not configured."
-  OUTPUT: "Add to ~/.claude/settings.json or .mcp.json:"
-  OUTPUT: '{"mcpServers":{"monday":{"command":"npx","args":["-y","@mondaydotcomorg/monday-api-mcp"]}}}'
-  OUTPUT: "Then restart Claude Code."
+  OUTPUT: "Monday MCP is installed but not yet active."
+  OUTPUT: "Restart Claude Code, then run `p. monday setup` again."
   STOP
 ```
 
@@ -68,7 +99,12 @@ IF not available:
 
 ### Flow
 
-1. **Verify MCP tools available**
+1. **Install MCP + Verify tools available**
+   ```
+   Execute Step 2 (auto-install MCP if needed)
+   Execute Step 3 (verify tools active)
+   IF not available: Prompt restart and STOP
+   ```
 
 2. **Test connection (triggers OAuth if needed)**
    ```

package/templates/commands/p.md

@@ -1,6 +1,6 @@
 ---
 description: 'prjct CLI - Developer momentum tool'
-allowed-tools: [Read, Write, Edit, Bash, Glob, Grep, Task, AskUserQuestion, TodoWrite]
+allowed-tools: [Read, Write, Edit, Bash, Glob, Grep, Task, AskUserQuestion, TodoWrite, WebFetch]
 ---
 
 # prjct Command Router
@@ -14,25 +14,72 @@ allowed-tools: [Read, Write, Edit, Bash, Glob, Grep, Task, AskUserQuestion, Todo
    ```bash
    npm root -g
    ```
-3. Read template from npm package:
+3. **Run Orchestrator** (for task-related commands):
+   - Read: `{npmRoot}/prjct-cli/templates/agentic/orchestrator.md`
+   - Execute orchestrator Steps 1-5 to load agents and skills
+4. Read command template:
    ```
    {npmRoot}/prjct-cli/templates/commands/{command}.md
    ```
-4. Execute template with `commandArgs` as input
+5. Execute template with `commandArgs` + orchestrator context
+
+## Orchestrator Integration
+
+For these commands, run orchestrator FIRST:
+- `task`, `done`, `ship` - Core workflow
+- `bug`, `plan`, `prd`, `spec`, `design` - Planning
+- `review`, `merge` - Git operations
+
+Skip orchestrator for:
+- `init`, `sync`, `setup` - Project config (no task context)
+- `dash`, `next`, `history` - Read-only views
+- `linear`, `jira`, `github`, `monday` - Integrations (own logic)
 
 ## Example
 
 ARGUMENTS = "task fix the login bug"
-- command = "task"
-- commandArgs = "fix the login bug"
-- npm root -g → `/opt/homebrew/lib/node_modules`
-- Read: `/opt/homebrew/lib/node_modules/prjct-cli/templates/commands/task.md`
-- Execute with: "fix the login bug"
+
+1. command = "task"
+2. commandArgs = "fix the login bug"
+3. npm root -g → `/opt/homebrew/lib/node_modules`
+4. **Orchestrator**:
+   - Analyze: "login bug" → domains: [frontend, backend]
+   - Load agents: frontend.md, backend.md
+   - Invoke skills: ui-design, api-design
+5. Read: `/opt/homebrew/lib/node_modules/prjct-cli/templates/commands/task.md`
+6. Execute with: "fix the login bug" + orchestrator context
 
 ## Available Commands
 
-`task` `done` `ship` `sync` `init` `idea` `dash` `next` `pause` `resume` `bug` `linear` `feature` `prd` `plan` `review` `merge` `git` `test` `cleanup` `design` `analyze` `history` `enrich` `update`
+**Core**: `task` `done` `ship` `pause` `resume`
+**Project**: `init` `sync` `setup` `dash`
+**Planning**: `plan` `prd` `spec` `design` `enrich`
+**Queue**: `next` `idea` `bug`
+**Integrations**: `linear` `jira` `github` `monday`
+**Git**: `git` `merge` `review`
+**Analysis**: `analyze` `history` `impact`
+**Utils**: `cleanup` `update` `verify` `test` `undo` `redo` `serve` `auth` `skill`
+
+## Orchestrator Output
+
+When orchestrator runs, output:
+
+```
+🎯 Task: {commandArgs}
+
+📦 Context:
+├── Agents: {loadedAgents}
+├── Skills: {activeSkills}
+└── Domain: {primaryDomain}
+```
+
+Then proceed with command execution.
 
 ## Action
 
-NOW run `npm root -g` and read the command template.
+NOW:
+1. Run `npm root -g`
+2. Check if command needs orchestrator
+3. If yes: Read and execute orchestrator.md
+4. Read the command template
+5. Execute with full context