prjct-cli 0.5.1 → 0.7.0

package/templates/commands/design.md

@@ -1,113 +1,38 @@
 ---
-name: p:design
-description: Design system architecture, APIs, and component interfaces
+allowed-tools: [Read, Write]
+description: 'Design architecture and APIs'
 ---
 
-# /p:design - System Architecture and Design
-
-Create technical designs with visual diagrams and implementation guides for system architecture, APIs, components, databases, and user flows.
+# /p:design
 
 ## Usage
 
 ```
-/p:design [target] [--type architecture|api|component|database|flow] [--format diagram|spec|code|all]
+/p:design [target] [--type architecture|api|component|database|flow]
 ```
 
-## Global Architecture
+## Flow
 
-This command operates on global data stored in `~/.prjct-cli/projects/{project-id}/`.
+1. Parse: target + type
+2. Generate: ASCII diagrams
+3. Create: specifications
+4. Save: `designs/{target}-{type}.md`
 
-### Steps
+## Types
 
-1. Parse design target and type (architecture, api, component, database, flow)
-2. Generate appropriate ASCII diagrams and visual representations
-3. Create technical specifications with technology stack and patterns
-4. Generate implementation templates and interfaces
-5. Save designs to `~/.prjct-cli/projects/{id}/designs/` directory
-6. Display formatted design with overview, specs, and implementation guide
-7. Link designs to tasks and track implementation progress
+- **architecture**: System design, components, data flow
+- **api**: Endpoint specs, schemas, auth
+- **component**: Interfaces, props, state
+- **database**: Schema, relationships, indexes
+- **flow**: User journeys, workflows
 
-## Response Format
+## Response
 
 ```
-🎨 ✨ Design Complete! ✨ 🎨
-
-📐 Design: [Target Name]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🏗️ Architecture Overview:
-[ASCII diagram or description]
-
-📋 Technical Specifications:
-• Technology Stack: [stack details]
-• Design Patterns: [patterns used]
-• Key Components: [component list]
-
-📦 Implementation Guide:
-1. Set up project structure
-2. Implement core models
-3. Build API endpoints
-4. Create UI components
-
-📁 Files Created:
-• ~/.prjct-cli/projects/{id}/designs/[target]-architecture.md
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ Design ready for implementation!
-
-💡 Next: /p:now "Implement [target]"
-```
-
-## Design Types
-
-### Architecture
-- System architecture diagrams
-- Component relationships
-- Data flow and communication patterns
-- Scalability considerations
-
-### API
-- Endpoint specifications
-- Request/response schemas
-- Authentication and authorization
-- Rate limiting and caching
-
-### Component
-- Component interfaces
-- Props and state management
-- Lifecycle and hooks
-- Styling and theming
+🎨 Design complete!
 
-### Database
-- Schema design
-- Entity relationships
-- Indexing strategy
-- Migration plans
+📐 {target} - {type}
+📄 Saved: designs/{target}-{type}.md
 
-### Flow
-- User journey diagrams
-- State machine flows
-- Process workflows
-- Integration flows
-
-## Examples
-
-Design system architecture:
-```
-/p:design authentication --type architecture
-```
-
-Design API endpoints:
-```
-/p:design user-management --type api --format spec
-```
-
-Design database schema:
-```
-/p:design products --type database --format diagram
-```
-
-Complete design with all formats:
-```
-/p:design payment-system --type architecture --format all
+/p:now "Implement {target}"
 ```

package/templates/commands/done.md

@@ -1,193 +1,30 @@
 ---
-allowed-tools: [Read, Write, Edit, TodoWrite]
-description: "Complete task, clear focus"
+allowed-tools: [Read, Write]
+description: 'Complete task, clear focus'
 ---
 
 # /p:done
 
-## Context Validation
+## Validation
 
-**Prerequisites:**
-- Project must be initialized (`.prjct/prjct.config.json` exists)
-- Active task must exist (`core/now.md` has content)
+- Requires: `.prjct/prjct.config.json` exists
+- Requires: `core/now.md` has content
+- Else: "Not working on anything. Use /p:now or /p:next"
 
-**If context is missing, Claude provides conversational response:**
-```
-✨ You're not working on anything right now!
-
-Want to start something?
-• Tell me what you want to build
-• Say "show me what's next"
-• Or use: /p:now | /p:next
+## Flow
 
-Let's ship something!
-```
+1. Read: `core/now.md` → calculate duration
+2. Clear: `core/now.md`
+3. Update: `progress/metrics.md`, `core/context.md`
+4. Log: `memory/context.jsonl`
 
-**Validation happens automatically through CLAUDE.md instructions - Claude checks context before executing!**
+## Response
 
-## Usage
-```
-/p:done
 ```
+✅ {task} ({duration})
 
-## Execution
-
-**Only runs if context validation passes ✅**
-
-1. Read task from `~/.prjct-cli/projects/{id}/core/now.md`, calculate duration
-2. Clear `core/now.md`
-3. **Trigger Scribe Agent** (Documentation):
-   - Get git changes since task started: `git diff --name-only`
-   - Invoke Scribe agent to document changes
-   - Show documentation draft to user
-   - **Request confirmation** before saving
-   - Save to `analysis/task-docs/[task-id].md` if confirmed
-4. Update `progress/metrics.md`, `core/context.md`
-5. Log to `memory/context.jsonl`:
-   ```json
-   {"action":"done","task":"[task]","started":"[t1]","completed":"[t2]","duration":"[min]","documented":true,"layer":"core"}
-   ```
-6. Response:
-   ```
-   ✅ [task description] ([duration])
-
-   What's next?
-   • "start [next task]" → Begin working
-   • "ship this feature" → Track & celebrate
-   • "add new idea" → Brainstorm
-
-   Or use: /p:now | /p:ship | /p:idea
-   ```
-
-   Or if queue empty:
-   ```
-   ✅ [task description] ([duration])
-
-   Queue is empty! What now?
-   • "add a task" → Plan next work
-   • "brainstorm ideas" → Creative mode
-   • "see my progress" → View achievements
-
-   Or: /p:idea | /p:next | /p:recap
-   ```
-
-## Scribe Agent Workflow
-
-When a task is completed, the Scribe agent is automatically invoked to document changes:
-
-### Step 1: Detect Changes
-```javascript
-const gitIntegration = require('../core/git-integration')
-const taskStartTime = readTaskStartTime()
-
-// Get files changed since task started
-const changes = await gitIntegration.getChangesSince(taskStartTime)
-```
-
-### Step 2: Generate Documentation
-Invoke Scribe agent with prompt:
-```
-Document the following task completion:
-
-Task: "[task description]"
-Duration: [duration]
-Files changed:
-${changes.files.join('\n')}
-
-Generate documentation including:
-1. Brief summary of what was implemented
-2. Key technical decisions
-3. Files affected and their purpose
-4. Any breaking changes or important notes
-
-Keep it concise (< 200 words).
+Next?
+• "start {task}" → work
+• "ship {feature}" → celebrate
+• /p:now | /p:ship
 ```
-
-### Step 3: Show Draft & Request Confirmation
-```
-📝 Scribe Agent Documentation Draft
-
-## Task: [task description]
-
-**Implemented**: [date]
-**Duration**: [duration]
-
-**Summary**:
-[AI-generated summary]
-
-**Technical Details**:
-- [Key decisions]
-- [Files modified]
-
-**Usage**:
-[Examples if applicable]
-
-─────────────────────────────────────
-
-Save this documentation? (y/n): _
-```
-
-### Step 4: Save if Confirmed
-```javascript
-if (userConfirms) {
-  const docPath = `~/.prjct-cli/projects/{id}/analysis/task-docs/${taskId}.md`
-  await saveDocumentation(docPath, documentation)
-  console.log('✅ Documentation saved!')
-} else {
-  console.log('ℹ️  Documentation discarded')
-}
-```
-
-## Example with Scribe
-
-```
-/p:done
-
-✅ implement login authentication (2h 15m)
-
-📝 Scribe Agent is documenting your changes...
-
-─────────────────────────────────────────────
-
-## Task: implement login authentication
-
-**Implemented**: 2025-10-02
-**Duration**: 2h 15m
-
-**Summary**:
-Implemented JWT-based authentication system with login and registration endpoints. Added middleware for protected routes and session management.
-
-**Technical Details**:
-- Added auth service with bcrypt password hashing
-- Created login/register API endpoints in auth.controller.ts
-- Implemented JWT middleware for route protection
-- Added user session management with Redis
-
-**Files Modified**:
-- src/features/auth/auth.service.ts (new)
-- src/features/auth/auth.controller.ts (new)
-- src/middleware/jwt.middleware.ts (new)
-- src/config/redis.config.ts (modified)
-
-**Breaking Changes**: None
-
-─────────────────────────────────────────────
-
-Save this documentation? (y/n): y
-
-✅ Documentation saved to task-docs!
-
-What's next?
-• "start next task" → Begin working
-• "ship authentication" → Track & celebrate
-
-Or use: /p:now | /p:ship
-```
-
-## Notes
-
-- Scribe agent uses git history to understand changes
-- Documentation is saved per-task for reference
-- User confirmation prevents unwanted docs
-- Can skip documentation by saying "no"
-- Documentation helps with onboarding and code reviews

package/templates/commands/feature.md

@@ -0,0 +1,113 @@
+---
+allowed-tools: [Read, Write, Bash]
+description: 'Value analysis + roadmap + task breakdown + auto-start'
+---
+
+# /p:feature
+
+## Usage
+
+```
+/p:feature "<description>"
+```
+
+## What It Does
+
+1. **Value analysis**: Impact/effort/timing analysis
+2. **Roadmap**: Positioning in project roadmap
+3. **Task breakdown**: Smart breakdown into logical tasks
+4. **Auto-start**: First task starts automatically
+
+## Flow
+
+1. Analyze value (impact/effort/timing)
+2. Position in roadmap
+3. Break down into logical tasks (as many as needed)
+4. **Write to session**: Append to `planning/sessions/{YYYY-MM}/{YYYY-MM-DD}.jsonl`
+5. **Update index**: Add to `planning/roadmap.md` (lightweight, last 30 days only)
+6. **Queue tasks**: Write to `core/next.md`
+7. Auto-start first task
+
+## Session Log Format
+
+Append to `planning/sessions/{YYYY-MM}/{YYYY-MM-DD}.jsonl`:
+
+```jsonl
+{"ts":"2025-10-04T14:30:00Z","type":"feature_add","name":"{feature}","tasks":{N},"impact":"{high/med/low}","effort":"{Xh}","status":"queued"}
+```
+
+## Index Update
+
+Append to `planning/roadmap.md` (keep only last 30 days):
+
+```markdown
+## Queued
+- [ ] {feature_name} ({N} tasks, {Xh} estimated) - Added 2025-10-04
+```
+
+If roadmap.md > 30 days old entries, archive them to `planning/archive/roadmap-{YYYY-MM}.md`
+
+## Value Analysis
+
+```
+Feature: {description}
+
+Value Analysis:
+• Impact: {high/medium/low}
+• Effort: {hours estimation}
+• Timing: {now/later/blocked_by}
+• Recommendation: {do_now/defer/needs_X_first}
+```
+
+## Task Breakdown
+
+```
+Roadmap: {feature_name}
+
+Tasks:
+1. [ ] {task_1}
+2. [ ] {task_2}
+3. [ ] {task_3}
+... (as many as needed)
+
+Estimated: {total_hours}h
+```
+
+## Response
+
+```
+✅ Feature roadmap created!
+
+{feature_name}
+📊 Value: {impact} | Effort: {hours}h
+⏰ Recommendation: {timing_advice}
+
+Tasks:
+1. {task_1}
+2. {task_2}
+...
+
+¿Empezamos con tarea 1?
+
+/p:done (when task complete) | /p:ship (when feature complete)
+```
+
+## Example
+
+```
+User: p. feature "agregar unit testing"
+
+Claude analyzes:
+- Impact: HIGH (quality improvement)
+- Effort: 8h
+- Timing: NOW (before shipping more features)
+
+Tasks created:
+1. Setup Jest/Vitest configuration
+2. Write tests for core utilities
+3. Write tests for components
+4. Add CI/CD test runner
+5. Update docs with testing guide
+
+"¿Empezamos con tarea 1: Setup Jest/Vitest?"
+```

package/templates/commands/fix.md

@@ -1,87 +1,79 @@
 ---
-allowed-tools: [Read, Grep, Bash, Edit]
-description: "Quick troubleshooting and automatic fixes"
+allowed-tools: [Read, Bash, Edit]
+description: 'Troubleshooting, guidance, and fixes'
 ---
 
-## 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:fix
 
+## Usage
 
+```
+/p:fix              # Diagnose current issue or get unstuck
+/p:fix [error]      # Fix specific error
+/p:stuck [issue]    # Alias for fix (guidance mode)
+```
 
-# /p:fix - Quick Fix & Troubleshooting
+## Flow
 
-## Purpose
-Instantly diagnose and fix common issues. Get unstuck in seconds, not minutes.
+1. Read: `core/now.md` + `analysis/` → get context
+2. Parse: error message OR issue description
+3. Detect: issue type (error/bug/design/perf/feature/blocked)
+4. Apply: automatic fix OR provide guidance
+5. Verify: test fix works (if auto-fix)
+6. Log: `memory/context.jsonl`
 
-## Usage
-```
-/p:fix [error message or description]
-```
+## Auto-Fix (Technical Errors)
 
-## Execution
-1. Analyze error type (syntax/type/runtime/build)
-2. Search for error patterns in codebase
-3. Apply automatic fix if safe and obvious
-4. Provide manual fix steps if complex
-5. Log solution to `.prjct/memory/context.jsonl`
-
-## Common Fixes
-
-**Auto-fixable**:
-- Missing semicolons, brackets, quotes
-- Import statements for undefined variables
-- Package.json dependencies
-- Simple type errors
-- Linting issues
-
-**Guided fixes**:
-- Null/undefined errors → Add null checks
-- Module not found → Install package or fix path
-- Build failures → Check configs and deps
-- Test failures → Show diff and fix approach
-
-## Implementation
-
-**Error detection**:
-```bash
-# Check for common issues
-- npm run lint 2>&1
-- npm run typecheck 2>&1
-- Check recent git changes
-- Analyze error stack trace
-```
+- **Dependencies**: `npm install` missing packages
+- **Config**: Fix malformed JSON/YAML
+- **Syntax**: ESLint/Prettier auto-fix
+- **Tests**: Update snapshots, fix imports
+- **Git**: Resolve merge conflicts
+
+## Guidance (When Stuck)
+
+- **Bug**: 🔍 Check logs → Isolate → Search error → Test fix
+- **Design**: 🎨 Define requirements → Start simple → Ship MVP → Iterate
+- **Performance**: ⚡ Profile first → Fix slowest → Cache ops → Measure
+- **Blocked**: 💡 Break into tasks → Start smallest → Ship incrementally
+- **Default**: Break down → Prioritize → Start → Ship
+
+## Response (auto-fixed)
 
-**Response format for auto-fix**:
 ```
-🔧 Fixed automatically!
+✅ Fixed: {error_type}
+
+{fix_details}
 
-Problem: Missing import for useState
-Solution: Added import from 'react'
-File: components/UserForm.tsx:1
+Verify: {command_to_test}
 
-✅ Error resolved - continue working!
+/p:test | /p:done
 ```
 
-**Response format for guided fix**:
+## Response (guidance)
+
 ```
-🔍 Issue identified: Cannot read property 'id' of undefined
+💡 {type_guidance}
+
+Let's break it down:
+1. {subtask} (~{time})
+2. {subtask} (~{time})
+3. {subtask} (~{time})
 
-📍 Location: services/auth.js:45
-🐛 Cause: user might be null
+Start with: /p:now "{first_subtask}"
 
-💡 Quick fix:
-if (!user?.id) {
-  return null;
-}
+/p:now | /p:task
+```
+
+## Response (manual diagnosis)
 
-Apply with: /p:fix apply
 ```
+🔍 Diagnosed: {issue}
 
-## Smart Features
-- Learns from previous fixes
-- Suggests preventive measures
-- Links to relevant documentation
-- Tracks fix patterns in memory
+Suggested fixes:
+1. {fix_option_1}
+2. {fix_option_2}
+3. {fix_option_3}
+
+/p:done after fixing
+```