prjct-cli 0.5.0 → 0.6.0

package/templates/commands/recap.md

@@ -1,86 +1,34 @@
 ---
-allowed-tools: [Read, Glob]
-description: "Show project status overview"
+allowed-tools: [Read]
+description: "Project status overview"
 ---
 
-## 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:recap
 
+## Flow
+1. Read: all data layers (core, progress, planning, analysis, memory)
+2. Aggregate: metrics and status from each layer
+3. Display: comprehensive overview
 
-
-# /p:recap - Project Recap
-
-## Purpose
-Display a comprehensive overview of project status and progress.
-
-## Usage
+## Response
 ```
-/p:recap
-```
-
-## Execution
-1. Read current task from `.prjct/core/now.md`
-2. Aggregate metrics from `.prjct/progress/metrics.md`
-3. Count shipped features from `.prjct/progress/shipped.md`
-4. Count queue items from `.prjct/core/next.md`
-5. Count ideas from `.prjct/planning/ideas.md`
-6. Reference project analysis and context
-7. Display comprehensive layered summary
-
-## Implementation
+📊 PROJECT RECAP
+━━━━━━━━━━━━━━━━
 
-1. **Gather cross-layer metrics**:
-   - **Core Layer**: Current task and duration, next queue
-   - **Progress Layer**: Shipped features, metrics, velocity trends
-   - **Planning Layer**: Ideas count, roadmap progress
-   - **Analysis Layer**: Repository insights, technical context
-   - **Memory Layer**: Decision history, learnings
+🎯 FOCUS
+Current: {task} ({duration})
+Queue: {N} tasks
 
-2. **Enhanced response format**:
-   ```
-   📊 PROJECT RECAP
-   ━━━━━━━━━━━━━━━━━━━
+📈 PROGRESS
+Shipped: {X} this week
+Velocity: {X.X} features/day
 
-   🎯 FOCUS
-   Current: [task] (2h 15m)
-   Queue: [N] tasks pending
+💡 PLANNING
+Ideas: {M} captured
+Roadmap: {X}% complete
 
-   📈 PROGRESS
-   Shipped: [X] this week, [Y] total
-   Velocity: [X.X] features/day
-   Streak: [N] days shipping
+{motivational_message}
 
-   💡 PLANNING
-   Ideas: [M] captured
-   Roadmap: [X]% complete
-
-   🔍 INSIGHTS
-   Repository: [project_type] with [tech_stack]
-   Architecture: [key_patterns]
-
-   🧠 MEMORY
-   Decisions: [N] logged
-   Learnings: [key_insights]
-
-   [Motivational message based on metrics]
-
-   📂 Quick Access:
-   - Core: .prjct/core/ (focus & priorities)
-   - Progress: .prjct/progress/ (metrics & shipped)
-   - Planning: .prjct/planning/ (ideas & roadmap)
-   - Analysis: .prjct/analysis/ (technical insights)
-   ```
-
-3. **Motivational messages**:
-   - High velocity: "🔥 You're on fire! Keep shipping!"
-   - Many ideas: "💡 Creative flow is strong!"
-   - Long streak: "🏆 Consistency champion!"
-   - Empty queue: "🎆 Time to dream bigger!"
+/p:now | /p:status | /p:next
+```
 
-## Visual Elements
-- Use progress bars for completion
-- Show week-over-week trends
-- Highlight achievements

package/templates/commands/roadmap.md

@@ -1,107 +1,38 @@
 ---
-allowed-tools: [Read, Write, Edit, TodoWrite]
-description: "Strategic planning and feature roadmap management"
+allowed-tools: [Read, Write]
+description: "Strategic roadmap management"
 ---
 
-## 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:roadmap - Strategic Planning
-
-## Purpose
-Plan features, track strategic progress, and stay aligned with goals. Zero PM overhead.
+# /p:roadmap
 
 ## Usage
 ```
-/p:roadmap [show|add|complete|next]
+/p:roadmap [show|add|complete|next]  # Default: show
 ```
 
-Default: show
-
-## Execution
-
-### `/p:roadmap` or `/p:roadmap show`
-Display current roadmap with progress
-
-### `/p:roadmap add <feature>`
-Add feature to roadmap with smart prioritization
-
-### `/p:roadmap complete <feature>`
-Mark feature as shipped and celebrate
-
-### `/p:roadmap next`
-Show next priority item to work on
-
-## Implementation
-
-**Roadmap structure** in `.prjct/planning/roadmap.md`:
-```markdown
-# Product Roadmap
+## Flow
+1. Parse: action (show/add/complete/next)
+2. Read: `planning/roadmap.md`
+3. Execute: based on action
+4. Update: roadmap file if needed
 
-## 🚀 Current Sprint (Week X)
-- [x] User authentication
-- [ ] Dashboard redesign
-- [ ] API optimization
-
-## 📅 Next Up
-- [ ] Real-time notifications
-- [ ] Data export feature
-- [ ] Mobile responsive design
-
-## 🌟 Future Vision
-- [ ] AI recommendations
-- [ ] Team collaboration
-- [ ] Analytics dashboard
-```
-
-**Smart prioritization**:
-- Impact vs effort matrix
-- User value scoring
-- Technical dependencies
-- Strategic alignment
-
-**Response format for show**:
+## Response (show)
 ```
 📍 PRODUCT ROADMAP
 
-🚀 Current Sprint (23% complete)
-├── ✅ User authentication
-├── 🔄 Dashboard redesign (in progress)
-└── ⏳ API optimization
+🚀 Current Sprint ({X}% complete)
+├── ✅ {feature}
+├── 🔄 {feature} (in progress)
+└── ⏳ {feature}
 
-📅 Next Up (3 features)
-├── Real-time notifications
-├── Data export feature
-└── Mobile responsive design
-
-📊 Progress Metrics:
-• Sprint velocity: 1.4 features/week
-• On track for: Dec 15 completion
-• Strategic alignment: High
-
-💡 Start next: /p:now "Dashboard redesign"
-```
-
-**Response format for add**:
-```
-✅ Added to roadmap: "Payment integration"
+📅 Next Up ({N} features)
+├── {feature}
+└── {feature}
 
-📍 Prioritized as: Next Up #1
-⚡ Estimated effort: Medium (3-5 days)
-🎯 Impact score: High
-🔗 Dependencies: User authentication ✅
+📊 Progress:
+• Velocity: {X.X} features/week
+• On track: {date}
 
-📋 Updated roadmap in .prjct/planning/roadmap.md
+/p:now "{next_feature}"
 ```
 
-## Features
-- Visual progress tracking
-- Smart prioritization
-- Sprint management
-- Velocity tracking
-- Strategic alignment

package/templates/commands/ship.md

@@ -1,181 +1,46 @@
 ---
-allowed-tools: [Read, Write, Edit, TodoWrite]
-description: "Ship a feature"
+allowed-tools: [Read, Write, Bash]
+description: "Ship feature with Git commit/push"
 ---
 
 # /p:ship
 
 ## Usage
 ```
-/p:ship <feature>
+/p:ship              # Current task
+/p:ship <feature>    # Named feature
 ```
 
-## Execution
+## Flow
+1. Get: feature name (from arg or `core/now.md`)
+2. Git: `add .` → check status
+3. Create: commit message with metadata
+4. Commit: with message
+5. Prompt: "Push? (y/n)"
+6. If yes: `git push`
+7. Update: `progress/shipped.md`, clear `core/now.md`
+8. Log: `memory/context.jsonl`
 
-1. Add to `~/.prjct-cli/projects/{id}/progress/shipped.md`:
-   ```markdown
-   ## Week [W], [YEAR]
-   - ✅ [feature] ([timestamp])
-   ```
-
-2. **Trigger Scribe Agent** (Documentation):
-   - Get git changes for the feature: `git diff --name-only`
-   - Invoke Scribe agent to document the shipped feature
-   - Show documentation draft to user
-   - **Request confirmation** before saving
-   - Save to `analysis/feature-docs/[feature-id].md` if confirmed
-
-3. Update `progress/metrics.md` (count, velocity, streak)
-4. Update `core/context.md`
-5. Log to `memory/context.jsonl`:
-   ```json
-   {"action":"ship","feature":"[desc]","timestamp":"[ISO]","week":"[w]","layer":"progress","total":[n],"documented":true}
-   ```
-
-6. Response:
-   ```
-   🚀 [feature name] shipped!
-
-   📈 This week: [count] | Total: [total]
-   Velocity: [X] features/day
-
-   Keep the momentum!
-   • "start next task" → Keep building
-   • "see my progress" → View stats
-   • "plan ahead" → Strategic thinking
-
-   Or: /p:now | /p:recap | /p:roadmap
-   ```
-
-## Scribe Agent Workflow
-
-When a feature is shipped, the Scribe agent is automatically invoked to document changes:
-
-### Step 1: Detect Changes
-```javascript
-const gitIntegration = require('../core/git-integration')
-
-// Get files changed for this feature
-const changes = await gitIntegration.getChangesSince(featureStartTime)
-```
-
-### Step 2: Generate Documentation
-Invoke Scribe agent with prompt:
+## Commit Message
 ```
-Document the following shipped feature:
-
-Feature: "[feature description]"
-Shipped: [timestamp]
-Files changed:
-${changes.files.join('\n')}
+feat: {feature_name}
 
-Generate release documentation including:
-1. Feature overview and user impact
-2. Technical implementation summary
-3. Key files and components affected
-4. Breaking changes or migration notes (if any)
-5. Usage examples
+Agent: {agent}
+Dev: @{github_dev}
+Complexity: {complexity}
+Time: {actual_time}
 
-Keep it concise and user-focused (< 300 words).
+Generated-by: prjct/cli
+Co-Authored-By: @{github_dev}
 ```
 
-### Step 3: Show Draft & Request Confirmation
+## Response
 ```
-📝 Scribe Agent Feature Documentation
-
-## Feature: [feature description]
-
-**Shipped**: [date]
-**Impact**: [user-facing impact]
-
-**Overview**:
-[AI-generated feature summary]
-
-**Technical Details**:
-- [Implementation highlights]
-- [Key components]
+🚀 {feature} shipped!
 
-**Usage**:
-[Examples if applicable]
+✅ Committed {+ pushed}
+{agent_icon} {agent} • {actual_time}
 
-**Breaking Changes**: [None / List]
-
-─────────────────────────────────────
-
-Save this documentation? (y/n): _
+/p:next | /p:status
 ```
 
-### Step 4: Save if Confirmed
-```javascript
-if (userConfirms) {
-  const docPath = `~/.prjct-cli/projects/{id}/analysis/feature-docs/${featureId}.md`
-  await saveDocumentation(docPath, documentation)
-  console.log('✅ Feature documentation saved!')
-} else {
-  console.log('ℹ️  Documentation discarded')
-}
-```
-
-## Example with Scribe
-
-```
-/p:ship "authentication system"
-
-🚀 authentication system shipped!
-
-📝 Scribe Agent is documenting your feature...
-
-─────────────────────────────────────────────
-
-## Feature: authentication system
-
-**Shipped**: 2025-10-02
-**Impact**: Users can now securely log in and manage sessions
-
-**Overview**:
-Implemented JWT-based authentication with login, registration, and password reset. Added middleware for protected routes and session management with automatic token refresh.
-
-**Technical Details**:
-- JWT authentication with bcrypt password hashing
-- Login/register/reset endpoints in auth.controller.ts
-- JWT middleware for route protection
-- Redis-based session management with 7-day expiry
-- Email verification workflow
-
-**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
-
-**Usage**:
-```javascript
-// Protected route example
-app.get('/api/profile', jwtMiddleware, profileController.get)
-```
-
-─────────────────────────────────────────────
-
-Save this documentation? (y/n): y
-
-✅ Feature documentation saved to analysis/feature-docs/!
-
-📈 This week: 3 | Total: 15
-Velocity: 2.1 features/day
-
-Keep the momentum!
-• "start next task" → Keep building
-• "see my progress" → View stats
-
-Or: /p:now | /p:recap
-```
-
-## Notes
-
-- Scribe agent uses git history to understand feature scope
-- Documentation is saved per-feature for release notes
-- User confirmation prevents unwanted documentation
-- Can skip documentation by saying "no"
-- Feature docs help with changelog generation and onboarding

package/templates/commands/status.md

@@ -0,0 +1,40 @@
+---
+allowed-tools: [Read]
+description: "KPI dashboard with ASCII graphics"
+---
+
+# /p:status
+
+## Flow
+1. Read: all core files + progress files
+2. Calculate: metrics (sprint %, tasks complete, days since ship, etc.)
+3. Render: `ASCIIGraphics.createDashboard(data)`
+
+## Data Structure
+```js
+{
+  sprintProgress: (complete / total) * 100,
+  tasksComplete: count,
+  tasksTotal: count,
+  ideasCount: count,
+  daysSinceShip: days,
+  currentTask: string,
+  taskTime: 'Xh Ym ago'
+}
+```
+
+## Output (Catppuccin Mocha)
+```
+┌─ Project Status ────────────────┐
+│ Sprint Progress  [████░] 80%    │
+│ Tasks Complete   12/15          │
+│ Ideas Backlog    8              │
+│ Days Since Ship  3              │
+├─ Current Focus ─────────────────┤
+│ → {current_task}                │
+│   Started: {time_ago}           │
+└─────────────────────────────────┘
+```
+
+**Colors**: Mauve borders, Teal progress, Sapphire highlights, Green/Yellow/Red for status
+

package/templates/commands/stuck.md

@@ -10,39 +10,27 @@ description: "Get unstuck"
 /p:stuck <issue>
 ```
 
-## Execution
-
-1. Detect issue type (bug/design/perf/feature)
-2. Check context:
-   - `~/.prjct-cli/projects/{id}/analysis/repo-summary.md`
-   - `~/.prjct-cli/projects/{id}/memory/context.jsonl`
-3. Log to `memory/context.jsonl`:
-   ```json
-   {"action":"stuck","issue":"[desc]","category":"[type]","approach":"[steps]","status":"in_progress"}
-   ```
-
-4. Response by type:
-
-   **Bug**: `🔍 1. Check logs 2. Isolate problem 3. Search error`
-
-   **Design**: `🎨 1. Define requirements 2. Start simple 3. Ship MVP`
-
-   **Performance**: `⚡ 1. Profile first 2. Fix slowest 3. Cache operations`
-
-   **Default**: `💡 1. Break into tasks 2. Start smallest 3. Ship it`
-
-5. Suggest breakdown + next actions:
-   ```
-   💡 [Type-specific guidance above]
+## Flow
+1. Detect: issue type (bug/design/perf/feature)
+2. Check: context from analysis + memory
+3. Provide: type-specific guidance
+4. Suggest: breakdown + next actions
+5. Log: `memory/context.jsonl`
+
+## Guidance by Type
+- **Bug**: 🔍 Check logs → Isolate → Search error
+- **Design**: 🎨 Define requirements → Start simple → Ship MVP
+- **Performance**: ⚡ Profile first → Fix slowest → Cache ops
+- **Default**: 💡 Break into tasks → Start smallest → Ship it
+
+## Response
+```
+💡 {type_guidance}
 
-   Let's break it down:
-   1. [subtask 1] (~15min)
-   2. [subtask 2] (~30min)
+Let's break it down:
+1. {subtask} (~{time})
+2. {subtask} (~{time})
 
-   Ready to start?
-   • "start the first part" → Begin small
-   • "add these as tasks" → Queue them
-   • "think more" → Capture ideas
+/p:now "{first}" | /p:task
+```
 
-   Or: /p:now "[first subtask]" | /p:task | /p:idea
-   ```