prjct-cli 1.22.0 → 1.24.0

package/templates/commands/done.md

@@ -1,291 +0,0 @@
----
-allowed-tools: [Read, Write, Bash, AskUserQuestion]
----
-
-# p. done
-
-## Step 1: Resolve Project Paths
-
-```bash
-# Get projectId from local config
-cat .prjct/prjct.config.json | grep -o '"projectId"[[:space:]]*:[[:space:]]*"[^"]*"' | cut -d'"' -f4
-```
-
-Set `globalPath = ~/.prjct-cli/projects/{projectId}`
-
-## Step 2: Read Current State
-
-READ `{globalPath}/storage/state.json`
-
-```
-IF no currentTask OR currentTask is null:
-  OUTPUT: "No active task. Use `p. task` to start one."
-  STOP
-```
-
-## Step 3: Handle Subtasks
-
-```
-IF currentTask.subtasks exists AND has items:
-  current = currentTask.subtasks[currentTask.currentSubtaskIndex]
-  remaining = subtasks where status != "completed"
-
-  IF remaining.length > 1:
-    # More subtasks after current one
-    AskUserQuestion:
-      question: "Subtask complete. What next?"
-      header: "Done"
-      options:
-        - label: "Next subtask (Recommended)"
-          description: "Mark current done, move to next"
-        - label: "Complete all remaining"
-          description: "Mark entire task as done"
-        - label: "Continue current"
-          description: "Keep working on this subtask"
-
-    IF "Continue current":
-      OUTPUT: "Continuing: {current subtask}"
-      STOP
-
-    IF "Next subtask" OR "Complete all remaining":
-      # ═══════════════════════════════════════════════════════════════
-      # MANDATORY HANDOFF COLLECTION (PRJ-262)
-      # Every subtask MUST provide handoff data before completing.
-      # This enables the next subtask to start with full context.
-      # ═══════════════════════════════════════════════════════════════
-
-      GOTO: Step 3.5 (Collect Handoff)
-
-      # After collecting handoff, mark current subtask as completed:
-      currentTask.subtasks[currentSubtaskIndex].status = "completed"
-      currentTask.subtasks[currentSubtaskIndex].output = "{handoff.output}"
-      currentTask.subtasks[currentSubtaskIndex].summary = {
-        "title": "{current subtask description}",
-        "description": "{what was accomplished}",
-        "filesChanged": [{path, action}...],
-        "whatWasDone": ["item1", "item2", ...],
-        "outputForNextAgent": "{context for next subtask}",
-        "notes": "{optional notes}"
-      }
-
-      IF "Next subtask":
-        currentTask.currentSubtaskIndex++
-        currentTask.subtasks[currentSubtaskIndex].status = "active"
-        currentTask.description = currentTask.subtasks[currentSubtaskIndex].description
-
-        WRITE state.json
-
-        # Show previous subtask handoff to establish context
-        OUTPUT:
-        """
-        ✅ Subtask complete: {completed subtask}
-
-        Progress: {completed}/{total} subtasks
-
-        ### Handoff
-        {outputForNextAgent}
-
-        Current: {next subtask description}
-
-        Next: Continue working, then `p. done`
-        """
-        STOP
-
-      # If "Complete all" - fall through to complete task (handoff still collected)
-```
-
-## Step 3.5: Collect Handoff (MANDATORY for subtask completion)
-
-**⛔ DO NOT skip this step. Every subtask completion MUST include handoff data.**
-
-The LLM should analyze the work done during this subtask and produce:
-
-### 1. Get Files Changed
-
-```bash
-# Files changed during this subtask (uncommitted + recent commits on branch)
-git diff --name-only HEAD 2>/dev/null
-git diff --name-only --cached 2>/dev/null
-```
-
-Categorize each file as `created`, `modified`, or `deleted`.
-
-### 2. Summarize Work Done
-
-Based on the code changes and task context, produce:
-- **whatWasDone**: Array of 1-5 bullet points describing key accomplishments
-- **outputForNextAgent**: A paragraph explaining context the next subtask needs:
-  - What was built/changed and why
-  - Key decisions made and their rationale
-  - Any patterns established that subsequent work should follow
-  - Known issues or edge cases to watch for
-
-### 3. Validation
-
-```
-IF whatWasDone is empty:
-  ⛔ STOP. At least one item is required.
-  Re-analyze the work and provide at minimum 1 bullet point.
-
-IF outputForNextAgent is empty:
-  ⛔ STOP. Context for next subtask is required.
-  Even if this is the last subtask, provide a summary for the done/ship step.
-```
-
-### 4. Store Handoff
-
-The handoff data is stored in the subtask's `summary` field in state.json.
-This data persists across sessions and feeds into the next subtask's prompt context.
-
----
-
-## Step 4: Complete Task
-
-Generate timestamp:
-```bash
-node -e "console.log(new Date().toISOString())"
-```
-
-Calculate duration from `currentTask.startedAt` to now.
-
-Update state:
-```
-# Mark all subtasks as completed
-FOR each subtask in currentTask.subtasks:
-  subtask.status = "completed"
-
-# Update task status
-currentTask.status = "completed"
-currentTask.completedAt = "{timestamp}"
-
-# Move to previousTask
-previousTask = currentTask
-currentTask = null
-```
-
-WRITE `{globalPath}/storage/state.json`:
-
-## Step 4.5: Capture Learnings & Value (LLM Knowledge)
-
-**⚠️ This data is for LLM future reference, not human documentation.**
-
-Based on the work completed, analyze the code changes and capture:
-
-### Learnings (Technical Knowledge for Future LLM Sessions)
-
-Identify and record:
-- **Patterns** - Any new code patterns introduced or discovered
-- **Approaches** - How problems were solved (implementation strategies)
-- **Decisions** - Why certain approaches were chosen over alternatives
-- **Gotchas** - Things that could trip up future work on similar tasks
-
-### Value Contribution
-
-Assess what value this task brings to the project:
-- **Type**: feature | bugfix | performance | dx | refactor | infrastructure
-- **Impact**: high | medium | low
-- **Description**: 1-2 sentences on the value added
-
-### Get Files Changed
-
-```bash
-git diff --name-only HEAD~1 2>/dev/null || git diff --name-only --cached
-```
-
-### Generate Tags
-
-Extract tags from the task context:
-- Domain tags (frontend, backend, api, database, etc.)
-- Feature tags (auth, ui, testing, etc.)
-- Technical tags (refactor, performance, security, etc.)
-
-### Write to Learnings File
-
-APPEND to `{globalPath}/memory/learnings.jsonl`:
-```jsonl
-{"taskId":"{id}","linearId":"{linearId or null}","timestamp":"{timestamp}","learnings":{"patterns":["pattern 1","pattern 2"],"approaches":["how X was solved"],"decisions":["why Y was chosen over Z"],"gotchas":["watch out for X"]},"value":{"type":"feature","impact":"high","description":"Brief description of value added"},"filesChanged":["path/to/file1.ts"],"tags":["domain-tag","feature-tag"]}
-```
-
-**Note**: This local cache enables future semantic retrieval without API latency. Will eventually feed into vector DB for cross-session LLM knowledge transfer.
-
----
-```json
-{
-  "currentTask": null,
-  "previousTask": {
-    "id": "{task.id}",
-    "description": "{task.parentDescription}",
-    "type": "{task.type}",
-    "status": "completed",
-    "startedAt": "{task.startedAt}",
-    "completedAt": "{timestamp}",
-    "subtasks": [...],
-    "branch": "{task.branch}",
-    "linearId": "{task.linearId or null}"
-  },
-  "pausedTasks": []
-}
-```
-
-## Step 5: Sync Issue Tracker Status (REQUIRED - DO NOT SKIP)
-
-**⛔ This step is MANDATORY if there's a linked issue. NEVER skip this.**
-
-**⛔ WRITE TO REMOTE ONLY - Do NOT re-read issue from API (token efficiency)**
-
-The linearId/externalId is already in `previousTask` from local state.json.
-Only send status update to remote API.
-
-```
-IF previousTask.linearId exists:
-  # ═══════════════════════════════════════════════════════════════
-  # USE prjct CLI DIRECTLY - NOT $PRJCT_CLI (may be unset)
-  # ═══════════════════════════════════════════════════════════════
-  RUN: prjct linear done "{linearId}"
-  RUN: prjct linear comment "{linearId}" "✅ Task completed. Ready for ship."
-
-  OUTPUT: "Linear: {linearId} → Done ✓"
-
-ELSE IF previousTask.externalId AND previousTask.externalProvider == "jira":
-  RUN: prjct jira transition "{externalId}" "Done"
-  RUN: prjct jira comment "{externalId}" "✅ Task completed. Ready for ship."
-
-  OUTPUT: "JIRA: {externalId} → Done ✓"
-
-ELSE:
-  # No issue tracker linked - that's OK, prjct works without it
-  # Just skip the sync step silently
-```
-
-## Step 6: Log Event
-
-APPEND to `{globalPath}/memory/events.jsonl`:
-```json
-{"type":"task_completed","taskId":"{id}","description":"{parentDescription}","timestamp":"{timestamp}","duration":"{duration}"}
-```
-
-## Step 7: Count Stats
-
-```bash
-# Count files changed
-git diff --stat HEAD~1 2>/dev/null | tail -1 || echo "0 files"
-
-# Count commits on branch
-git rev-list --count HEAD ^main 2>/dev/null || echo "0"
-```
-
----
-
-## Output
-
-```
-✅ {task description} ({duration})
-
-Files: {count} | Commits: {count}
-{linearId ? "Linear: {linearId} → Done" : ""}
-
-Next:
-- More work? → `p. task "description"`
-- Ready to ship? → `p. ship`
-- See queue → `p. next`
-```

package/templates/commands/enrich.md

@@ -1,174 +0,0 @@
----
-allowed-tools: [Read, Write, Bash, Task, AskUserQuestion]
----
-
-# p. enrich "$ARGUMENTS"
-
-Transform vague tickets into technical PRDs with AI-powered analysis.
-
-## How This Works
-
-User types `p. enrich PRJ-123` → Claude fetches ticket → Analyzes codebase → Generates PRD → Publishes back
-
-**Examples**:
-- `p. enrich PRJ-123` → Enrich Linear issue
-- `p. enrich "vague description"` → Analyze without fetching
-
----
-
-## CRITICAL - Execution Pattern
-
-**NEVER use MCP tools** (`mcp__linear__*`, `mcp__jira__*`).
-**ALWAYS use SDK via CLI helper.**
-
-### CLI Helper for Linear
-
-```bash
-PRJCT_CLI=$(npm root -g)/prjct-cli
-PROJECT_ID=$(cat .prjct/prjct.config.json | jq -r '.projectId')
-
-# Fetch issue
-ISSUE=$(bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID get PRJ-123)
-
-# Update description with PRD
-bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID update PRJ-123 '{"description":"..."}'
-
-# Or add as comment
-bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID comment PRJ-123 "## PRD\n..."
-```
-
----
-
-## Step 1: Parse Input
-
-Detect input format:
-- `PRJ-123` → Linear issue (team key prefix)
-- `"text"` → No fetch, analyze text directly
-
----
-
-## Step 2: Fetch Ticket
-
-```bash
-# For Linear
-ISSUE=$(bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID get "$IDENTIFIER")
-```
-
-Extract: `id`, `title`, `description`, `status`, `priority`
-
----
-
-## Step 3: Analyze Codebase
-
-```
-USE Task(Explore) "very thorough":
-- Find similar implementations
-- Identify affected files
-- Assess risks and dependencies
-
-READ agents/*.md for domain patterns
-```
-
----
-
-## Step 4: Classify & Estimate
-
-**Type**: Bug | Story | Improvement | Spike | Chore
-
-**Story Points**:
-| Points | Complexity |
-|--------|------------|
-| 1-2 | Trivial - single file, obvious fix |
-| 3-5 | Small - few files, clear scope |
-| 8 | Medium - multiple files, some unknowns |
-| 13 | Large - significant changes, needs design |
-| 21+ | Epic - break down further |
-
----
-
-## Step 5: Generate PRD
-
-```markdown
-## Overview
-{1-2 sentence summary of the technical approach}
-
-## Classification
-- **Type**: {type}
-- **Points**: {points}
-- **Risk**: Low/Medium/High
-
-## Technical Approach
-{Detailed implementation plan}
-
-## Files to Modify
-- `path/to/file.ts` - {what changes}
-- ...
-
-## Acceptance Criteria
-- [ ] {criterion 1}
-- [ ] {criterion 2}
-- ...
-
-## LLM Prompt
-{Copy-paste ready prompt for any AI tool to implement this}
-```
-
----
-
-## Step 6: Ask Publication Method
-
-```
-ASK: "How should I publish the PRD?"
-OPTIONS:
-  - "Update description" (replace existing)
-  - "Add as comment" (preserve original)
-  - "Just show me" (don't publish)
-```
-
----
-
-## Step 7: Publish
-
-```bash
-# Update description
-bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID update PRJ-123 '{"description":"# PRD\n..."}'
-
-# Or add comment
-bun $PRJCT_CLI/core/cli/linear.ts --project $PROJECT_ID comment PRJ-123 "## PRD\n..."
-```
-
----
-
-## Step 8: Save Locally
-
-```bash
-WRITE: {globalPath}/storage/enriched/{id}.json
-```
-
-```json
-{
-  "id": "PRJ-123",
-  "enrichedAt": "2026-01-29T...",
-  "type": "story",
-  "points": 5,
-  "filesAffected": ["src/auth.ts", "src/login.tsx"],
-  "prd": "..."
-}
-```
-
----
-
-## Output
-
-```
-✅ Enriched: PRJ-123 - {title}
-
-Type: Story | Points: 5 | Files: 3
-
-Published: Updated description
-
-Next:
-- Start work? → `p. linear start 123` or `p. task "PRJ-123"`
-- Enrich another? → `p. enrich PRJ-124`
-- See backlog → `p. linear`
-```