prjct-cli 0.5.1 → 0.7.0

package/templates/commands/test.md

@@ -1,94 +1,48 @@
 ---
-allowed-tools: [Bash, Read, Edit, Glob]
-description: "Run tests and auto-fix simple failures"
+allowed-tools: [Bash, Read, Edit]
+description: 'Run tests with auto-fix'
 ---
 
-## Global Architecture
-This command uses the global prjct architecture:
-- Data stored in: `~/.prjct-cli/projects/{id}/`
-- Config stored in: `{project}/.prjct/prjct.config.json`
-- Commands synchronized across all editors
-
-
-
-# /p:test - Smart Test Execution
-
-## Purpose
-Run tests, show failures clearly, and auto-fix obvious issues. Ship with confidence.
+# /p:test
 
 ## Usage
+
 ```
-/p:test [all|unit|e2e|failed]
+/p:test [all|unit|e2e|failed|fix]  # Default: all
 ```
 
-Default: all
+## Flow
 
-## Execution
-1. Detect test runner (jest/vitest/mocha/pytest)
-2. Run tests with appropriate command
-3. Parse and display results with clarity
-4. Auto-fix simple test failures
-5. Update `.prjct/progress/metrics.md` with coverage
+1. Detect: test runner (jest/vitest/pytest/etc)
+2. Run: tests with appropriate command
+3. Parse: results
+4. Auto-fix: simple failures (snapshots, timeouts, imports)
+5. Update: coverage in `progress/metrics.md`
 
-## Implementation
+## Response (success)
 
-**Test detection**:
-```bash
-# Auto-detect test command from package.json or config
-- npm test / npm run test
-- pytest / python -m pytest
-- go test ./...
-- cargo test
-```
-
-**Auto-fixable issues**:
-- Snapshot updates → Update automatically
-- Timeout errors → Increase timeout
-- Import errors → Fix imports
-- Expected vs received → Show diff clearly
-
-**Response format for success**:
 ```
 ✅ All tests passing!
 
-📊 Test Results:
-• Unit: 45/45 passed
-• Integration: 12/12 passed
-• E2E: 8/8 passed
-
-🎯 Coverage: 87% (+2%)
-⚡ Time: 4.2s
+📊 Results:
+• Unit: {N}/{N}
+• Integration: {N}/{N}
+• E2E: {N}/{N}
 
-🚀 Ready to ship!
-```
+🎯 Coverage: {X}%
+⚡ Time: {X}s
 
-**Response format for failures**:
+/p:ship
 ```
-❌ 3 tests failing
 
-1️⃣ UserService.test.js:
-   Expected: "John Doe"
-   Received: "John"
+## Response (failures)
 
-   💡 Auto-fix available: /p:test fix
+```
+❌ {N} tests failing
 
-2️⃣ auth.e2e.js:
-   Timeout after 5000ms
+{failure_details}
 
-   💡 Increasing timeout to 10000ms...
+💡 Auto-fix: /p:test fix
 
-📊 Summary: 62/65 passed (95%)
+📊 Summary: {passed}/{total} ({X}%)
 ```
-
-**Quick commands**:
-- `/p:test` - Run all tests
-- `/p:test failed` - Re-run only failed tests
-- `/p:test watch` - Run in watch mode
-- `/p:test fix` - Apply available auto-fixes
-
-## Features
-- Smart failure detection
-- Clear error messages
-- Auto-fix common issues
-- Coverage tracking
-- Performance monitoring

package/templates/commands/workflow.md

@@ -1,224 +1,34 @@
-# Workflow System for AI Assistants
+---
+allowed-tools: [Read, Write]
+description: 'Show workflow status'
+---
 
-## Overview
-Interactive agent workflows that orchestrate task execution with user guidance. When capabilities are missing, the system prompts for decisions rather than auto-skipping, and tracks all installation efforts as workflow tasks.
+# /p:workflow
 
-## How It Works
+## Usage
 
-### 1. Automatic Workflow Detection
-When a task is added via `/p:idea`, the system:
-- Classifies task type: ui, api, bug, refactor, feature
-- Detects project capabilities (design system, tests, docs)
-- Marks steps that need user prompting when capabilities are missing
-- Initializes workflow with all steps (required + optional with prompts)
-
-### 2. Workflow Types
-
-**UI Component** (ui):
-- design (optional - needs design system)
-- dev (required)
-- test (optional - needs test framework)
-- docs (optional - needs docs system)
-
-**API Endpoint** (api):
-- dev (required)
-- test (optional - needs test framework)
-- docs (optional - needs docs system)
-
-**Bug Fix** (bug):
-- analyze (required)
-- fix (required)
-- test (optional - needs test framework)
-
-**Refactor** (refactor):
-- refactor (required)
-- test (optional - needs test framework)
-
-**Feature** (feature):
-- design (optional - needs design system)
-- dev (required)
-- test (optional - needs test framework)
-- docs (optional - needs docs system)
-
-### 3. Task Classification
-
-Keywords that trigger specific workflows:
-
-**UI**: button, form, modal, card, component, menu, nav, input
-**API**: endpoint, api, service, route, controller
-**Bug**: bug, fix, error, issue, broken
-**Refactor**: refactor, improve, optimize, clean
-**Feature**: feature, functionality, module
-
-Default: ui
-
-### 4. Capability Detection
-
-The system detects capabilities by checking:
-
-**Design System**:
-- Folders: design/, designs/, .storybook/
-- Dependencies: @storybook/react, @storybook/vue
-- Files: *.figma
-
-**Test Framework**:
-- Dependencies: jest, vitest, mocha, @jest/core
-- Files: *.test.*, *.spec.*
-- Configs: jest.config.js, vitest.config.js
-
-**Documentation**:
-- Folders: docs/, documentation/
-- Files: README.md
-- Dependencies: typedoc, jsdoc
-
-### 5. Interactive Workflow Execution
-
-**When step requires missing capability:**
-1. System pauses and prompts user with options:
-   - Install recommended tool (based on stack detection)
-   - Skip this step
-   - Continue without capability
-   - Pause workflow
-
-2. If user chooses installation:
-   - Creates installation task (e.g., "Install Jest")
-   - Inserts task into workflow at current position
-   - Tracks installation effort as visible task
-   - Executes installation command
-   - Configures tool automatically
-   - Verifies capability is now available
-   - Continues to original step
-
-**When `/p:done` is executed:**
-- Marks current step as completed
-- Checks if next step needs prompting
-- Shows prompt if capability missing
-- Advances to next step (or completes workflow)
-- Updates now.md with next step details
-- Assigns appropriate agent for next step
-- Logs progress to memory
-
-### 6. Step Structure
-
-Each step has:
-- **name**: Step identifier
-- **agent**: Assigned AI agent specialist
-- **action**: What to do
-- **required**: Must execute (true) or optional (false)
-- **needs**: Required capability (if optional)
-- **prompt**: Should prompt user when capability missing
-- **needsPrompt**: Flag set when step needs user decision
-- **retry**: Max retry attempts (for test steps)
-- **type**: 'install' for dynamically inserted installation tasks
-
-## Commands
-
-### View Workflow Status
 ```
-/p:workflow
+/p:workflow           # Show status
+/p:workflow skip      # Skip current step
 ```
-Shows current workflow state, active step, progress.
 
-### Skip Current Step
-```
-/p:workflow skip
-```
-Skips current optional step, moves to next.
-
-## Example Workflows
-
-### Full Stack (Has Everything)
-```
-/p:idea "Create login form"
-→ Workflow: design→dev→test→docs
-→ Execute each step with /p:done
-```
-
-### Missing Test Framework (Interactive)
-```
-/p:idea "Create button component"
-→ Workflow: dev→test→docs
-→ /p:done (completes dev)
-
-⚠️  Missing test capability for "test" step
-
-📋 Recommended: Vitest, Jest + Testing Library
-💡 Reason: Quality assurance and regression prevention
-
-Options:
-1. Install recommended (npm install -D vitest @testing-library/react)
-2. Skip this step
-3. Continue without test
-4. Pause workflow
+## Flow
 
-→ User chooses: 1 (install)
-→ System creates: "Install test framework" task
-→ System executes: npm install -D vitest...
-→ System configures: vitest.config.js created
-→ Installation tracked as completed task
-→ Continues to test step
-```
-
-### User Skips Missing Capability
-```
-/p:idea "Fix auth bug"
-→ Workflow: analyze→fix→test
-→ /p:done (completes fix)
+1. Read: `workflow/state.json`
+2. Display: current step + progress
+3. Check: capabilities for next steps
 
-⚠️  Missing test capability for "test" step
-→ User chooses: 2 (skip)
-→ Step skipped, workflow completes
-```
+## Response
 
-### Installation Tracked as Task
-```
-When user installs missing tool:
-1. "Install Jest" task inserted at current position
-2. Installation runs: npm install -D jest
-3. Configuration created: jest.config.js
-4. Task marked complete with duration (e.g., 1.2 min)
-5. Installation visible in workflow progress
-6. Workflow continues to intended step
 ```
+🔄 Workflow: {task_type}
 
-## Best Practices
-
-1. **Never hallucinate capabilities** - Only use what exists
-2. **Always prompt when capability missing** - Never auto-skip, ask user first
-3. **Track all installation efforts** - Every tool install becomes a visible task
-4. **Recommend based on stack** - Detect framework and suggest appropriate tools
-5. **Clear handoffs** - Each step completes before next starts
-6. **Agent assignment** - Right specialist for each step
-7. **State tracking** - Workflow progress and installations logged to memory
+Progress: {current}/{total}
+Current: {step_name} ({agent})
+Status: {status}
 
-## Error Handling
+Next: {next_step}
+{capability_prompt_if_needed}
 
-- If workflow init fails, task is still created (degrades gracefully)
-- Missing capabilities = prompt user, don't auto-skip or fail
-- Installation failures = notify user, offer alternatives or skip
-- Test failures can retry up to configured limit
-- Workflow can be cleared manually if needed
-
-## State Management
-
-Workflow state stored in:
-```
-~/.prjct-cli/projects/{id}/workflow/state.json
+/p:done | /p:workflow skip
 ```
-
-Contains:
-- task: Task description
-- type: Workflow type
-- caps: Detected capabilities
-- steps: All workflow steps (including dynamically inserted install tasks)
-- missingCapabilities: Array of capabilities that need prompting
-- current: Current step index
-- active: Workflow active flag
-- timestamps: Created, completed
-
-Each step tracks:
-- status: pending, in_progress, completed, skipped
-- needsPrompt: Boolean flag for user decision required
-- type: 'install' for installation tasks
-- insertedAt: Timestamp for dynamically added tasks
-- skipReason: Why step was skipped (if user chose skip)