prjct-cli 1.47.0 → 1.47.4

package/templates/baseline/patterns/typescript.json

@@ -1,18 +0,0 @@
-{
-  "items": [
-    {
-      "name": "Prefer strict typing contracts",
-      "description": "Functions and component props should be explicitly typed; avoid implicit any boundaries.",
-      "severity": "high",
-      "language": "TypeScript",
-      "confidence": 0.88
-    },
-    {
-      "name": "Type-first API surfaces",
-      "description": "Exported modules should define reusable domain types for inputs and outputs.",
-      "severity": "medium",
-      "language": "TypeScript",
-      "confidence": 0.8
-    }
-  ]
-}

package/templates/commands/analyze.md

@@ -1,11 +0,0 @@
----
-allowed-tools: [Bash]
----
-
-# p. analyze $ARGUMENTS
-
-```bash
-prjct analyze $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/auth.md

@@ -1,15 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. auth $ARGUMENTS
-
-Supports: `login`, `logout`, `status` (default: show status).
-
-```bash
-prjct auth $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.
-
-For `login`: ASK for API key if needed.

package/templates/commands/bug.md

@@ -1,28 +0,0 @@
----
-allowed-tools: [Bash, Task, AskUserQuestion]
----
-
-# p. bug $ARGUMENTS
-
-## Step 1: Validate
-If $ARGUMENTS is empty, ASK the user for a bug description.
-
-## Step 2: Report and explore
-```bash
-prjct bug "$ARGUMENTS" --md
-```
-
-Search the codebase for affected files.
-
-## Step 3: Fix now or queue
-ASK: "Fix this bug now?" Fix now / Queue for later
-
-If fix now: create branch `bug/{slug}` and start working.
-If queue: done -- bug is tracked.
-
-## Presentation
-Format bug reports as:
-
-1. `**Bug reported**: {description}`
-2. Show affected files with `code formatting` for paths
-3. Present fix/queue options clearly

package/templates/commands/cleanup.md

@@ -1,11 +0,0 @@
----
-allowed-tools: [Bash, Read, Edit]
----
-
-# p. cleanup $ARGUMENTS
-
-```bash
-prjct cleanup $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/dash.md

@@ -1,16 +0,0 @@
----
-allowed-tools: [Bash]
----
-
-# p. dash $ARGUMENTS
-
-Supports views: `compact`, `week`, `month`, `roadmap` (default: full dashboard).
-
-```bash
-prjct dash ${ARGUMENTS || ""} --md
-```
-
-Follow the instructions in the CLI output.
-
-## Presentation
-Present dashboard data using the tables and sections from CLI markdown. Keep it scannable — the dashboard should be a quick status overview.

package/templates/commands/design.md

@@ -1,11 +0,0 @@
----
-allowed-tools: [Bash, Read, Write]
----
-
-# p. design $ARGUMENTS
-
-```bash
-prjct design $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/done.md

@@ -1,46 +0,0 @@
----
-allowed-tools: [Bash, Read, AskUserQuestion]
----
-
-# p. done
-
-## Step 1: Complete via CLI
-```bash
-prjct done --md
-```
-If CLI output is JSON with `options`, present the options to the user and execute the chosen command.
-
-## Step 2: Verify completion
-- Review files changed: `git diff --name-only HEAD`
-- Ensure work is complete and tested
-
-## Step 3: Pattern compliance check
-
-If a Pattern Commitment table was created during the "Pattern commitment" step of the task workflow, review each committed pattern against the actual changes:
-
-| Pattern | Status | Evidence |
-|---------|--------|----------|
-| (name) | FOLLOWED | `path/file.ts:line` — used correct abstraction |
-| (name) | VIOLATED | reason — e.g., needed `use client` for interactivity |
-
-Report any VIOLATED pattern with a clear reason. The user decides whether to accept the violation.
-
-If no commitment table exists (e.g., project not synced, or patterns were empty), skip this step.
-
-## Step 4: Handoff context
-Summarize what was done and what the next subtask needs to know.
-
-## Step 5: Follow CLI next steps → Ship
-After completing, you MUST ask:
-ASK: "Subtask done. Ready to ship or continue to next subtask?"
-- Ship now → execute `p. ship` workflow (load and follow `~/.claude/commands/p/ship.md`)
-- Next subtask → continue working
-- Pause → execute `p. pause`
-
-## Presentation
-Format your completion summary as:
-
-1. `**Subtask complete**: {what was done}`
-2. Brief summary of changes (2-3 lines max)
-3. If next subtask exists, preview what's next
-4. Show next commands as a table

package/templates/commands/enrich.md

@@ -1,20 +0,0 @@
----
-allowed-tools: [Bash, Read, Task, AskUserQuestion]
----
-
-# p. enrich $ARGUMENTS
-
-## Step 1: Validate
-If $ARGUMENTS is empty, ASK for an issue ID or description.
-
-## Step 2: Fetch and analyze
-```bash
-prjct enrich "$ARGUMENTS" --md
-```
-
-Search the codebase for similar implementations and affected files.
-
-## Step 3: Publish
-ASK: "Update description / Add as comment / Just show me"
-
-Follow the CLI instructions for publishing.

package/templates/commands/git.md

@@ -1,17 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. git $ARGUMENTS
-
-Supports: `commit`, `push`, `sync`, `undo`.
-
-## BLOCKING: Never commit/push to main/master.
-
-```bash
-prjct git $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.
-
-Every commit MUST include footer: `Generated with [p/](https://www.prjct.app/)`

package/templates/commands/history.md

@@ -1,13 +0,0 @@
----
-allowed-tools: [Bash]
----
-
-# p. history $ARGUMENTS
-
-Supports: `undo`, `redo` (default: show snapshot history).
-
-```bash
-prjct history $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/idea.md

@@ -1,13 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. idea $ARGUMENTS
-
-If $ARGUMENTS is empty, ASK the user for their idea.
-
-```bash
-prjct idea "$ARGUMENTS" --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/impact.md

@@ -1,13 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. impact $ARGUMENTS
-
-Supports: `list`, `summary`, or specific feature ID (default: most recent ship).
-
-```bash
-prjct impact $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output. When collecting effort data, success metrics, and learnings, ask the user for input.

package/templates/commands/init.md

@@ -1,11 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. init $ARGUMENTS
-
-```bash
-prjct init $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/jira.md

@@ -1,94 +0,0 @@
----
-allowed-tools: ["*"]
----
-
-# p. jira $ARGUMENTS
-
-Jira is MCP-only — no API tokens, no REST calls.
-
-## Step 0: Check MCP readiness (ALWAYS, except for `setup`)
-
-Look for tools starting with `mcp__jira` or `mcp__atlassian` in your tool list.
-
-**If tools ARE available** → proceed with the requested operation below.
-
-**If NOT available** → run `prjct jira status --md` and follow the instructions in the output.
-The CLI auto-validates tokens, auto-migrates from legacy versions, and auto-cleans corrupted state. Trust its diagnosis.
-
-**Do NOT attempt MCP tool calls if Jira tools are not in your tool list.**
-
----
-
-## Setup (`p. jira setup`)
-
-Run step by step:
-
-### Step 1: Write MCP config + auto-repair
-```bash
-prjct jira setup --md
-```
-
-Setup now auto-cleans corrupted tokens and auto-migrates from legacy mcp-remote versions.
-If setup reports "ready" → skip to Step 3.
-
-### Step 2: Complete OAuth in terminal (only if setup says OAuth is required)
-
-Tell the user to open a NEW terminal and run this **exact** command (version pinned to match mcp.json):
-```
-npx -y mcp-remote@0.1.38 https://mcp.atlassian.com/v1/mcp
-```
-
-This will:
-1. Print an OAuth URL
-2. Try to open the browser automatically
-3. If browser doesn't open → copy-paste the URL manually
-
-Tell the user: **Complete the authorization in the browser, then come back here.**
-
-Wait for the user to confirm they completed OAuth before continuing.
-
-### Step 2.5: Verify OAuth worked
-```bash
-prjct jira verify --md
-```
-
-This scans `~/.mcp-auth/`, validates tokens, auto-migrates from legacy versions, and gives a clear READY / NOT READY verdict.
-If NOT READY → follow the instructions in the output.
-
-### Step 3: Restart Claude Code
-
-Tell the user: "Close and reopen Claude Code. The Jira MCP tools will be ready."
-
-After restart, Jira MCP tools are available — no more auth needed.
-
----
-
-## Status (`p. jira status`)
-
-```bash
-prjct jira status --md
-```
-
----
-
-## Sprint / Backlog
-
-```bash
-prjct jira sprint --md   # → JQL for active sprint
-prjct jira backlog --md  # → JQL for backlog
-```
-
-Use the returned JQL with the Jira MCP search tool (available after setup + restart).
-Show sprint and backlog issues **separately**:
-- `## 🏃 Active Sprint` for sprint issues
-- `## 📋 Backlog` for backlog issues
-
----
-
-## Issue Operations (list / get / create / update / start / done)
-
-Use Jira MCP tools directly. No REST API, no API tokens.
-
-- `start <KEY>`: transition to In Progress via MCP → `prjct task "<title>" --md`
-- `done <KEY>`: transition to Done via MCP → `prjct done --md`
-- `list`: fetch assigned issues via MCP → show as table

package/templates/commands/learnings.md

@@ -1,11 +0,0 @@
----
-allowed-tools: [Bash]
----
-
-# p. learnings
-
-```bash
-prjct learnings --md
-```
-
-Follow the instructions in the CLI output.

package/templates/commands/linear.md

@@ -1,88 +0,0 @@
----
-allowed-tools: ["*"]
----
-
-# p. linear $ARGUMENTS
-
-Linear is MCP-only — no SDK, no API tokens.
-
-## Step 0: Check MCP readiness (ALWAYS, except for `setup`)
-
-Look for tools starting with `mcp__linear` in your tool list.
-
-**If tools ARE available** → proceed with the requested operation below.
-
-**If NOT available** → run `prjct linear status --md` and follow the instructions in the output.
-The CLI auto-validates tokens, auto-migrates from legacy versions, and auto-cleans corrupted state. Trust its diagnosis.
-
-**Do NOT attempt MCP tool calls if Linear tools are not in your tool list.**
-
----
-
-## Setup (`p. linear setup`)
-
-Run step by step:
-
-### Step 1: Write MCP config + auto-repair
-```bash
-prjct linear setup --md
-```
-
-Setup now auto-cleans corrupted tokens and auto-migrates from legacy mcp-remote versions.
-If setup reports "ready" → skip to Step 3.
-
-### Step 2: Complete OAuth in terminal (only if setup says OAuth is required)
-
-Tell the user to open a NEW terminal and run this **exact** command (version pinned to match mcp.json):
-```
-npx -y mcp-remote@0.1.38 https://mcp.linear.app/mcp
-```
-
-This will:
-1. Print an OAuth URL
-2. Try to open the browser automatically
-3. If browser doesn't open → copy-paste the URL manually
-
-Tell the user: **Complete the authorization in the browser, then come back here.**
-
-Wait for the user to confirm they completed OAuth before continuing.
-
-### Step 2.5: Verify OAuth worked
-```bash
-prjct linear verify --md
-```
-
-This scans `~/.mcp-auth/`, validates tokens, auto-migrates from legacy versions, and gives a clear READY / NOT READY verdict.
-If NOT READY → follow the instructions in the output.
-
-### Step 3: Restart Claude Code
-
-Tell the user: "Close and reopen Claude Code. The Linear MCP tools will be ready."
-
-After restart, Linear MCP tools are available — no more auth needed.
-
----
-
-## Status (`p. linear status`)
-
-```bash
-prjct linear status --md
-```
-
----
-
-## Issue Operations (list / get / start / done / update / comment / create)
-
-Use Linear MCP tools directly. No SDK, no API tokens.
-
-- `start <ID>`: move to In Progress via MCP → `prjct task "<title>" --md`
-- `done <ID>`: move to Done via MCP → `prjct done --md`
-- `list`: fetch assigned issues via MCP → show as table with ID, title, status, priority
-
----
-
-## Sync (`p. linear sync`)
-
-1. Fetch assigned issues via Linear MCP tools
-2. For each untracked issue: `prjct task "<title>" --md`
-3. Show sync summary

package/templates/commands/merge.md

@@ -1,25 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. merge
-
-## Pre-flight (BLOCKING)
-Verify: active task exists, PR exists, PR is approved, CI passes, no conflicts.
-
-## Step 1: Get merge plan
-```bash
-prjct merge --md
-```
-
-## Step 2: Get approval (BLOCKING)
-ASK: "Merge this PR?" Yes / No
-
-## Step 3: Execute
-```bash
-gh pr merge {prNumber} --squash --delete-branch
-git checkout main && git pull origin main
-```
-
-## Step 4: Update issue tracker
-If linked to Linear/JIRA, mark as Done via CLI.

package/templates/commands/next.md

@@ -1,12 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. next $ARGUMENTS
-
-```bash
-prjct next $ARGUMENTS --md
-```
-If CLI output is JSON with `options`, present the options to the user and execute the chosen command.
-
-Follow the instructions in the CLI output.

package/templates/commands/p.md

@@ -1,62 +0,0 @@
----
-description: 'prjct CLI - Context layer for AI agents'
-allowed-tools: [Read, Write, Edit, Bash, Glob, Grep, Task, AskUserQuestion, TodoWrite, WebFetch]
----
-
-# prjct Command Router
-
-**ARGUMENTS**: $ARGUMENTS
-
-All commands use the `p.` prefix.
-
-## Quick Reference
-
-| Command | Description |
-|---------|-------------|
-| `p. task <desc>` | Start a task |
-| `p. done` | Complete current subtask |
-| `p. ship [name]` | Ship feature with PR + version bump |
-| `p. sync` | Analyze project, regenerate agents |
-| `p. pause` | Pause current task |
-| `p. resume` | Resume paused task |
-| `p. next` | Show priority queue |
-| `p. idea <desc>` | Quick idea capture |
-| `p. bug <desc>` | Report bug with auto-priority |
-| `p. linear` | Linear integration (via MCP) |
-| `p. jira` | JIRA integration (via MCP) |
-
-## Execution
-
-```
-1. PARSE: $ARGUMENTS → extract command (first word)
-2. GET npm root: npm root -g
-3. LOAD template: {npmRoot}/prjct-cli/templates/commands/{command}.md
-4. EXECUTE template
-```
-
-## Command Aliases
-
-| Input | Redirects To |
-|-------|--------------|
-| `p. undo` | `p. history undo` |
-| `p. redo` | `p. history redo` |
-
-## State Context
-
-All state is managed by the `prjct` CLI via SQLite (prjct.db).
-Templates should use CLI commands for data operations — never read/write JSON storage files directly.
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Unknown command | "Unknown command: {command}. Run `p. help` for available commands." |
-| No project | "No prjct project. Run `p. init` first." |
-| Template not found | "Template not found: {command}.md" |
-
-## NOW: Execute
-
-1. Parse command from $ARGUMENTS
-2. Handle aliases (undo → history undo, redo → history redo)
-3. Run `npm root -g` to get template path
-4. Load and execute command template

package/templates/commands/p.toml

@@ -1,37 +0,0 @@
-# prjct Command Router for Gemini CLI
-description = "prjct - Context layer for AI coding agents"
-
-prompt = """
-# prjct Command Router
-
-You are using prjct, a context layer for AI coding agents.
-
-**ARGUMENTS**: {{args}}
-
-## Instructions
-
-1. Parse arguments: first word = `command`, rest = `commandArgs`
-2. Get npm global root by running: `npm root -g`
-3. Read the command template from:
-   `{npmRoot}/prjct-cli/templates/commands/{command}.md`
-4. Execute the template with `commandArgs` as input
-
-## Example
-
-If 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 template with: "fix the login bug"
-
-## Available Commands
-
-task, done, ship, sync, init, idea, dash, next, pause, resume, bug,
-linear, jira, feature, prd, plan, review, merge, git, test, cleanup,
-design, analyze, history, enrich, update
-
-## Action
-
-NOW run `npm root -g` and read the appropriate command template.
-"""

package/templates/commands/pause.md

@@ -1,16 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. pause $ARGUMENTS
-
-If no reason provided, ask the user:
-
-Ask the user: "Why are you pausing?" with options: Blocked, Switching task, Break, Researching
-
-```bash
-prjct pause "$ARGUMENTS" --md
-```
-If CLI output is JSON with `options`, present the options to the user and execute the chosen command.
-
-Follow the instructions in the CLI output.

package/templates/commands/plan.md

@@ -1,13 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. plan $ARGUMENTS
-
-Supports: `quarter`, `prioritize`, `add <prd-id>`, `capacity` (default: show status).
-
-```bash
-prjct plan $ARGUMENTS --md
-```
-
-Follow the instructions in the CLI output. When selecting features or adjusting capacity, ask the user for input.

package/templates/commands/prd.md

@@ -1,21 +0,0 @@
----
-allowed-tools: [Bash, Read, Write, AskUserQuestion, Task]
----
-
-# p. prd $ARGUMENTS
-
-## Step 1: Validate
-If $ARGUMENTS is empty, ASK the user for a feature title.
-
-## Step 2: Create PRD via CLI
-```bash
-prjct prd "$ARGUMENTS" --md
-```
-
-## Step 3: Follow CLI methodology
-The CLI guides through discovery, sizing, and phase execution.
-Search the codebase for architecture patterns.
-
-## Step 4: Get approval
-Show the PRD summary and get explicit approval.
-ASK: "Add to roadmap now?" Yes / No (keep as draft)

package/templates/commands/resume.md

@@ -1,12 +0,0 @@
----
-allowed-tools: [Bash, AskUserQuestion]
----
-
-# p. resume $ARGUMENTS
-
-```bash
-prjct resume $ARGUMENTS --md
-```
-If CLI output is JSON with `options`, present them to the user with AskUserQuestion and execute the chosen command.
-
-Follow the instructions in the CLI output. If the CLI says to switch branches, do so.

package/templates/commands/review.md

@@ -1,20 +0,0 @@
----
-allowed-tools: [Bash, Read, AskUserQuestion]
----
-
-# p. review $ARGUMENTS
-
-## Step 1: Run review
-```bash
-prjct review $ARGUMENTS --md
-```
-
-## Step 2: Analyze changes
-Read changed files and check for security issues, logic errors, and missing error handling.
-
-## Step 3: Create/check PR
-If no PR exists, create one with `gh pr create`.
-If PR exists, check approval status with `gh pr view`.
-
-## Step 4: Follow CLI next steps
-The CLI output indicates what to do next (fix issues, wait for approval, merge).