prjct-cli 0.5.1 → 0.6.0

package/templates/commands/context.md

@@ -1,105 +1,36 @@
 ---
-allowed-tools: [Read, Glob, Bash]
-description: "Show project context and recent activity"
+allowed-tools: [Read]
+description: "Project context and activity"
 ---
 
-## 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:context
 
+## Flow
+1. Read: all layers (core, analysis, planning, progress, memory)
+2. Aggregate: project overview + recent activity
+3. Display: comprehensive context
 
-
-# /p:context - Project Context
-
-## Purpose
-Display project context including type, current task, and recent activity.
-
-## Usage
-```
-/p:context
+## Response
 ```
+🌍 PROJECT CONTEXT
+━━━━━━━━━━━━━━━━━
 
-## Execution
-1. Aggregate context from all project layers
-2. Reference analysis for technical context
-3. Show current task and planning alignment
-4. Display recent activity from memory layer
-5. Provide cross-layer insights and suggestions
-
-## Implementation
-
-1. **Layer aggregation**:
-   - **Core Layer**: Current task from `.prjct/core/now.md`, queue from `.prjct/core/next.md`
-   - **Analysis Layer**: Project insights from `.prjct/analysis/repo-summary.md`
-   - **Planning Layer**: Roadmap status from `.prjct/planning/roadmap.md`
-   - **Progress Layer**: Recent metrics from `.prjct/progress/metrics.md`
-   - **Memory Layer**: Activity history from `.prjct/memory/context.jsonl`
-
-2. **Enhanced context reading**:
-   - Project type and architecture from analysis layer
-   - Strategic alignment from planning layer
-   - Performance metrics from progress layer
-   - Decision history from memory layer
+📦 PROJECT
+Type: {type}
+Stack: {stack}
 
-3. **Comprehensive response format**:
-   ```
-   🌍 PROJECT CONTEXT
-   ━━━━━━━━━━━━━━━━━━━━━━━
+🎯 CURRENT FOCUS
+Task: {task}
+Started: {time_ago}
 
-   📦 PROJECT OVERVIEW
-   Type: Next.js Application
-   Location: /Users/dev/projects/app
-   Framework: React 18, TypeScript
-   Architecture: [from analysis layer]
+🔄 RECENT ACTIVITY
+• {event}: {desc} ({time_ago})
+• {event}: {desc} ({time_ago})
 
-   🎯 CURRENT FOCUS
-   Task: Building user dashboard
-   Started: 45 minutes ago
-   Strategic alignment: High (roadmap priority #2)
+💡 PLANNING
+Queue: {N} tasks
+Ideas: {M} captured
 
-   📈 RECENT PROGRESS
-   Velocity: 1.4 features/day
-   Streak: 5 days shipping
-   Quality: 95% success rate
-
-   🔄 RECENT ACTIVITY (from memory layer):
-   • shipped: Authentication system (2h ago)
-   • done: API endpoints (3h ago)
-   • idea: Add real-time updates (4h ago)
-   • now: Building user dashboard (45m ago)
-   • decision: Chose Next.js over Nuxt (yesterday)
-
-   💡 PLANNING STATUS
-   Queue: 3 tasks pending
-   Ideas: 7 captured
-   Roadmap progress: 23% complete
-
-   🧠 KEY INSIGHTS
-   Recent decisions: 3 logged
-   Learning areas: Architecture patterns
-   Growth momentum: +15% complexity handling
-
-   📂 LAYER NAVIGATION:
-   - Core: .prjct/core/ (focus & priorities)
-   - Analysis: .prjct/analysis/ (technical insights)
-   - Planning: .prjct/planning/ (strategy & roadmap)
-   - Progress: .prjct/progress/ (metrics & shipped)
-   - Memory: .prjct/memory/ (decisions & history)
-
-   🎯 NEXT SUGGESTED ACTION:
-   Continue with current task or /p:done if complete
-   ```
-
-4. **Project insights**:
-   - Dependencies summary
-   - Test coverage if available
-   - Build status
-   - Last deploy info
+/p:now | /p:status
+```
 
-5. **Smart suggestions**:
-   Based on context, suggest:
-   - "Long task - consider breaking down"
-   - "Good time to ship and take a break"
-   - "Review queue priorities"

package/templates/commands/design.md

@@ -1,113 +1,35 @@
 ---
-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]
-```
-
-## Global Architecture
-
-This command operates on global data stored in `~/.prjct-cli/projects/{project-id}/`.
-
-### Steps
-
-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
-
-## Response Format
-
 ```
-🎨 ✨ 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]"
+/p:design [target] [--type architecture|api|component|database|flow]
 ```
 
-## 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
-
-### Database
-- Schema design
-- Entity relationships
-- Indexing strategy
-- Migration plans
+## Flow
+1. Parse: target + type
+2. Generate: ASCII diagrams
+3. Create: specifications
+4. Save: `designs/{target}-{type}.md`
 
-### Flow
-- User journey diagrams
-- State machine flows
-- Process workflows
-- Integration flows
+## Types
+- **architecture**: System design, components, data flow
+- **api**: Endpoint specs, schemas, auth
+- **component**: Interfaces, props, state
+- **database**: Schema, relationships, indexes
+- **flow**: User journeys, workflows
 
-## Examples
-
-Design system architecture:
-```
-/p:design authentication --type architecture
+## Response
 ```
+🎨 Design complete!
 
-Design API endpoints:
-```
-/p:design user-management --type api --format spec
-```
+📐 {target} - {type}
+📄 Saved: designs/{target}-{type}.md
 
-Design database schema:
-```
-/p:design products --type database --format diagram
+/p:now "Implement {target}"
 ```
 
-Complete design with all formats:
-```
-/p:design payment-system --type architecture --format all
-```

package/templates/commands/done.md

@@ -1,193 +1,28 @@
 ---
-allowed-tools: [Read, Write, Edit, TodoWrite]
+allowed-tools: [Read, Write]
 description: "Complete task, clear focus"
 ---
 
 # /p:done
 
-## Context Validation
+## Validation
+- Requires: `.prjct/prjct.config.json` exists
+- Requires: `core/now.md` has content
+- Else: "Not working on anything. Use /p:now or /p:next"
 
-**Prerequisites:**
-- Project must be initialized (`.prjct/prjct.config.json` exists)
-- Active task must exist (`core/now.md` has content)
+## Flow
+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`
 
-**If context is missing, Claude provides conversational response:**
+## Response
 ```
-✨ You're not working on anything right now!
+✅ {task} ({duration})
 
-Want to start something?
-• Tell me what you want to build
-• Say "show me what's next"
-• Or use: /p:now | /p:next
-
-Let's ship something!
-```
-
-**Validation happens automatically through CLAUDE.md instructions - Claude checks context before executing!**
-
-## Usage
-```
-/p:done
-```
-
-## 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/fix.md

@@ -1,87 +1,48 @@
 ---
-allowed-tools: [Read, Grep, Bash, Edit]
-description: "Quick troubleshooting and automatic fixes"
+allowed-tools: [Read, Bash, Edit]
+description: "Quick troubleshooting 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 - Quick Fix & Troubleshooting
-
-## Purpose
-Instantly diagnose and fix common issues. Get unstuck in seconds, not minutes.
+# /p:fix
 
 ## Usage
 ```
-/p:fix [error message or description]
+/p:fix              # Diagnose current issue
+/p:fix [error]      # Fix specific error
 ```
 
-## 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`
+## Flow
+1. Read: `core/now.md` → get context
+2. Parse: error message OR diagnose current state
+3. Detect: common patterns (deps, config, syntax, tests)
+4. Apply: automatic fix OR suggest solution
+5. Verify: test fix works
+6. Log: `memory/context.jsonl`
 
 ## Common Fixes
+- **Dependencies**: `npm install` missing packages
+- **Config**: Fix malformed JSON/YAML
+- **Syntax**: ESLint/Prettier auto-fix
+- **Tests**: Update snapshots, fix imports
+- **Git**: Resolve merge conflicts
 
-**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
+## Response (auto-fixed)
 ```
+✅ Fixed: {error_type}
 
-**Response format for auto-fix**:
-```
-🔧 Fixed automatically!
+{fix_details}
 
-Problem: Missing import for useState
-Solution: Added import from 'react'
-File: components/UserForm.tsx:1
-
-✅ Error resolved - continue working!
+Verify: {command_to_test}
 ```
 
-**Response format for guided fix**:
+## Response (manual)
 ```
-🔍 Issue identified: Cannot read property 'id' of undefined
-
-📍 Location: services/auth.js:45
-🐛 Cause: user might be null
+🔍 Diagnosed: {issue}
 
-💡 Quick fix:
-if (!user?.id) {
-  return null;
-}
+Suggested fixes:
+1. {fix_option_1}
+2. {fix_option_2}
 
-Apply with: /p:fix apply
+/p:done after fixing
 ```
 
-## Smart Features
-- Learns from previous fixes
-- Suggests preventive measures
-- Links to relevant documentation
-- Tracks fix patterns in memory