prjct-cli 0.8.6 → 0.9.1

package/templates/commands/suggest.md

@@ -7,168 +7,48 @@ description: 'Context-aware suggestions based on project state and momentum'
 
 ## Purpose
 
-Analyze project state and recommend next best actions based on:
-- Current task status
-- Queue state
-- Time since last ship
-- Recent velocity
-- Patterns and momentum
-
-## Usage
-
-```
-/p:suggest
-```
+Analyze project state and recommend next actions based on current task, queue, last ship time, velocity, and momentum patterns.
 
 ## Flow
 
-1. **Read state files**:
-   - `core/now.md` → Current task
-   - `core/next.md` → Queue
-   - `progress/shipped.md` → Recent ships
-   - `planning/roadmap.md` → Active features
-   - Sessions from last 7 days (if available)
-
-2. **Calculate metrics**:
-   - Days since last ship
-   - Active task duration
-   - Queue size
-   - Velocity (features/week)
-   - Completion rate
-
-3. **Detect patterns**:
-   - Long-running task (>1 day)
-   - Stale queue (not updated recently)
-   - High velocity (shipping frequently)
-   - Low activity (no movement)
-   - Blocked tasks
-
-4. **Generate recommendations**:
-   - Immediate action (what to do RIGHT NOW)
-   - Urgency alerts (if any)
-   - Momentum tips (maintain or improve)
-   - Strategic suggestions (longer-term)
-
-## Analysis Logic
-
-### Scenario 1: No Active Task + Queue Has Tasks
-
-**Pattern**: Ready to work, tasks available
-
-**Recommendation**:
-```
-⚡ ACCIÓN INMEDIATA
-Tienes {N} tareas esperando
-→ /p:next (ver prioridades)
-→ /p:build 1 (empezar top priority)
-```
-
-### Scenario 2: Active Task + Long Duration (>4h)
-
-**Pattern**: Might be stuck or need break
-
-**Recommendation**:
-```
-⏱️  ALERTA DE TIEMPO
-Tarea "{task}" lleva {duration}
-
-¿Estás atorado?
-→ /p:stuck "{descripción}" (pedir ayuda)
-→ /p:done (si ya terminaste y olvidaste marcar)
-
-¿Es muy grande?
-→ Considera dividirla en tareas más pequeñas
-```
-
-### Scenario 3: No Ships in 3+ Days
-
-**Pattern**: Losing momentum
-
-**Recommendation**:
-```
-🔥 URGENTE: {N} días sin ship
-
-Acción recomendada:
-→ Completa algo HOY (aunque sea pequeño)
-→ /p:next → pick quick win → /p:ship
-
-Momentum = Motivation
-No dejes que se enfríe!
-```
-
-### Scenario 4: Empty Queue + No Active Task
-
-**Pattern**: Need planning
+1. **Read state files**: `core/now.md`, `core/next.md`, `progress/shipped.md`, `planning/roadmap.md`, sessions (last 7 days)
+2. **Calculate metrics**: Days since ship, active task duration, queue size, velocity (features/week), completion rate
+3. **Detect patterns**: Long-running task (>1 day), stale queue, high velocity, low activity, blocked
+4. **Generate recommendations**: Immediate action, urgency alerts, momentum tips, strategic suggestions
 
-**Recommendation**:
-```
-💡 NECESITAS PLANEAR
-
-Opciones:
-
-1. Agregar nueva feature
-   /p:feature "{descripción}"
+## Scenario Patterns
 
-2. Analizar proyecto
-   /p:analyze
-   → Descubre TODOs y mejoras
+**1. No Active Task + Queue Has Tasks**
+→ Ready to work: `/p:next` → `/p:build 1`
 
-3. Revisar roadmap
-   /p:roadmap
-   → Ver features planificadas
+**2. Active Task + Long Duration (>4h)**
+→ Might be stuck: `/p:stuck "{desc}"` or divide task into smaller parts
+→ If forgot to mark: `/p:done`
 
-4. Reportar bug
-   /p:bug "{descripción}"
-```
-
-### Scenario 5: High Velocity (2+ ships/week)
+**3. No Ships in 3+ Days**
+→ Losing momentum: Complete something TODAY, pick quick win from `/p:next` → `/p:ship` same day
 
-**Pattern**: Great momentum!
+**4. Empty Queue + No Active Task**
+→ Need planning: `/p:feature "{desc}"` or `/p:analyze` or `/p:roadmap` or `/p:bug "{desc}"`
 
-**Recommendation**:
-```
-🚀 EXCELENTE RITMO!
+**5. High Velocity (2+ ships/week)**
+→ Great momentum: Maintain rhythm, consider tests/docs, quality checks
 
-Velocidad: {X} features/semana
-
-Mantén el momentum:
-→ Sigue con el siguiente task
-→ Considera agregar tests si no los tienes
-→ Documenta mientras shipeas
-
-¡Vas muy bien! 🎉
-```
-
-### Scenario 6: Queue Growing (10+ tasks)
-
-**Pattern**: Over-planning, under-doing
-
-**Recommendation**:
-```
-⚠️  COLA MUY GRANDE ({N} tareas)
-
-Recomendación:
-→ STOP agregando tareas
-→ START completándolas
-
-Acción:
-/p:build 1 → /p:done → repeat
-
-Ship > Plan
-```
+**6. Queue Growing (10+ tasks)**
+→ Over-planning: STOP adding, START completing. Ship > Plan.
 
 ## Response Format
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
+💡 PERSONALIZED SUGGESTIONS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📊 ANÁLISIS:
-  • Tarea activa: {current_task | "ninguna"}
-  • En cola: {N} tareas
-  • Último ship: {time_ago}
-  • Velocidad: {X} features/semana
+📊 ANALYSIS:
+  • Active task: {current_task | "none"}
+  • Queue: {N} tasks
+  • Last ship: {time_ago}
+  • Velocity: {X} features/week
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
@@ -176,9 +56,9 @@ Ship > Plan
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-🎯 TE RECOMIENDO:
+🎯 RECOMMENDATIONS:
 
-1. ⚡ ACCIÓN INMEDIATA
+1. ⚡ IMMEDIATE ACTION
    {immediate_action}
    → {command_1}
    → {command_2}
@@ -195,361 +75,22 @@ Ship > Plan
 
 {motivational_message}
 
-¿Qué prefieres hacer?
-```
-
-## Examples
-
-### Example 1: Ready to Work
-
-```
-/p:suggest
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 ANÁLISIS:
-  • Tarea activa: ninguna
-  • En cola: 5 tareas
-  • Último ship: hace 1 día
-  • Velocidad: 3 features/semana
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 TE RECOMIENDO:
-
-1. ⚡ ACCIÓN INMEDIATA
-   Tienes 5 tareas esperando y buen momentum
-   → /p:next (ver prioridades)
-   → /p:build 1 (empezar top priority)
-
-2. 🚀 MOMENTUM
-   Estás en excelente ritmo (3 features/semana)
-   → Mantén el flow
-   → Shiped ayer, hoy puedes completar otra
-
-3. 💡 CALIDAD
-   Con esta velocidad, considera:
-   → Agregar tests si no los tienes
-   → Documentar mientras shipeas
-   → Code review de features recientes
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¡Vas muy bien! Sigue así 🎉
-
-¿Empezamos con /p:next?
-```
-
-### Example 2: Stuck on Task
-
-```
-/p:suggest
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 ANÁLISIS:
-  • Tarea activa: "implement websocket connection"
-  • Duración: 6 horas
-  • En cola: 3 tareas
-  • Último ship: hace 3 días
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚠️  ALERTA: Tarea larga + Sin ships recientes
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 TE RECOMIENDO:
-
-1. ⚡ ACCIÓN INMEDIATA
-   ¿Estás atorado con websockets?
-
-   Opciones:
-   → /p:stuck "websocket issues" (pedir ayuda)
-   → /p:done (si ya terminaste y olvidaste)
-
-   ¿La tarea es muy grande?
-   → Considera dividirla:
-     - Setup básico de websocket
-     - Implementar eventos
-     - Testing y manejo de errores
-
-2. 🔥 URGENTE
-   3 días sin ship → Momentum en riesgo
-
-   → Completa ALGO hoy (aunque sea pequeño)
-   → Ship > Perfect
-   → Puedes iterar después
-
-3. 💡 ALTERNATIVA
-   Si websockets está bloqueado:
-   → /p:next (ver otras tareas)
-   → Trabaja en algo más mientras investigas
-   → Mantén el momentum
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-No te quedes atascado! Pide ayuda o ship algo más pequeño.
-
-¿Necesitas ayuda con websockets?
-```
-
-### Example 3: Losing Momentum
-
-```
-/p:suggest
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 ANÁLISIS:
-  • Tarea activa: ninguna
-  • En cola: 8 tareas
-  • Último ship: hace 5 días ⚠️
-  • Velocidad: 0.4 features/semana
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🔥 URGENTE: 5 DÍAS SIN SHIP
-
-El momentum se está perdiendo!
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 TE RECOMIENDO:
-
-1. ⚡ ACCIÓN INMEDIATA (HOY)
-   Completa UNA tarea pequeña
-
-   → /p:next (busca quick win)
-   → /p:build {la más fácil}
-   → /p:done → /p:ship MISMO DÍA
-
-   Objetivo: Romper el ciclo de inactividad
-
-2. 🎯 ESTRATEGIA
-   Tienes 8 tareas en cola
-   → Demasiado planning, poco doing
-
-   STOP: Agregar más tareas
-   START: Completar las existentes
-
-   Ship > Plan
-
-3. 💡 MANTÉN MOMENTUM
-   Una vez que ships hoy:
-   → Ship algo cada 1-2 días
-   → Tareas pequeñas > Tareas grandes
-   → Celebra cada win (por pequeño que sea)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Momentum = Motivation
-¡Vamos a shipear algo HOY! 🚀
-
-¿Listo para ver tu cola y elegir un quick win?
-```
-
-### Example 4: Need Planning
-
-```
-/p:suggest
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 ANÁLISIS:
-  • Tarea activa: ninguna
-  • En cola: 0 tareas
-  • Último ship: hace 2 horas ✅
-  • Velocidad: 4 features/semana
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 TE RECOMIENDO:
-
-1. 💡 PLANEAR SIGUIENTE FEATURE
-   Acabas de ship → Excelente!
-   Cola vacía → Necesitas planear
-
-   Opciones:
-
-   A) Agregar nueva feature
-      /p:feature "{descripción}"
-      → Análisis de valor
-      → Task breakdown
-      → Auto-start
-
-   B) Analizar proyecto
-      /p:analyze
-      → Descubre TODOs automáticamente
-      → Identifica mejoras
-      → Genera tareas
-
-   C) Revisar roadmap
-      /p:roadmap
-      → Ver features planificadas
-      → Decidir siguiente
-
-2. 🚀 MOMENTUM EXCELENTE
-   4 features/semana → Top tier!
-
-   → Mantén este ritmo
-   → Considera refactors si no los has hecho
-   → Tests, docs, optimizaciones
-
-3. 🎯 CALIDAD
-   Con alta velocidad, asegura:
-   → Code quality (linting, formatting)
-   → Test coverage
-   → Documentation
-   → No technical debt
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¡Excelente trabajo! Sigue así 🎉
-
-¿Qué feature quieres agregar?
-```
-
-### Example 5: Over-Planning
-
-```
-/p:suggest
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 SUGERENCIAS PERSONALIZADAS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 ANÁLISIS:
-  • Tarea activa: ninguna
-  • En cola: 15 tareas ⚠️
-  • Último ship: hace 1 día
-  • Velocidad: 2 features/semana
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚠️  ALERTA: COLA MUY GRANDE
-
-Ratio planning/doing desbalanceado
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 TE RECOMIENDO:
-
-1. ⚡ ACCIÓN INMEDIATA
-   STOP → Agregar más tareas
-   START → Completar las existentes
-
-   → /p:next (ver top 5)
-   → /p:build 1
-   → /p:done
-   → Repeat
-
-   Objetivo: Reducir cola a <5 tareas
-
-2. 🎯 ESTRATEGIA
-   Con 15 tareas y velocidad de 2/semana:
-   → Necesitas 7+ semanas para completar
-   → Muchas tareas se volverán obsoletas
-
-   Mejor enfoque:
-   → Completa 5-7 tareas
-   → Reevalúa el resto
-   → Elimina las que ya no son relevantes
-
-3. 💡 PRINCIPIO
-   Ship Fast No BS
-
-   → Tareas en cola NO agregan valor
-   → Solo las completadas cuentan
-   → Small batches > Big queues
-
-   Execution > Planning
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Menos planning, más shipping! 🚀
-
-¿Listo para empezar a vaciar esa cola?
+What would you like to do?
 ```
 
 ## Urgency Levels
 
-### 🟢 Green (All Good)
-- Active task or ready to start
-- Shipped within last 2 days
-- Good velocity (2+ features/week)
-
-**Message**: Positive reinforcement, keep momentum
-
-### 🟡 Yellow (Attention Needed)
-- Task running >4 hours
-- 3-4 days since last ship
-- Queue growing (>7 tasks)
-
-**Message**: Gentle nudge, suggest action
-
-### 🔴 Red (Urgent)
-- 5+ days since last ship
-- Task running >24 hours
-- Queue >10 tasks with no activity
-
-**Message**: Direct call to action, break the pattern
-
-## Key Principles
-
-1. **Data-driven**: Base suggestions on actual metrics
-2. **Actionable**: Always provide specific commands
-3. **Motivational**: Encourage without being annoying
-4. **Honest**: If momentum is low, say it
-5. **Pattern recognition**: Detect stuck/blocked scenarios
-6. **Contextual**: Suggestions fit current state
-7. **Bilingual**: Support both English and Spanish
+**🟢 Green** (All good): Active task or ready, shipped <2 days, velocity 2+ features/week → Positive reinforcement
+**🟡 Yellow** (Attention): Task >4h, 3-4 days since ship, queue >7 tasks → Gentle nudge
+**🔴 Red** (Urgent): 5+ days since ship, task >24h, queue >10 + no activity → Direct call to action
 
 ## Validation
 
-- **Requires init**: Must have prjct project
-- **Read-only**: Never modifies files
-- **No parameters**: Just analyzes current state
+- Requires: `.prjct/prjct.config.json` exists
+- Read-only: Never modifies files
+- No parameters: Analyzes current state
 
 ## Edge Cases
 
-### Incomplete data
-```
-📊 Limited data available
-
-Based on what I can see:
-{partial_analysis}
-
-Tip: Use prjct more to get better suggestions!
-- /p:build → Track tasks
-- /p:done → Record completions
-- /p:ship → Celebrate wins
-```
-
-### First time usage
-```
-👋 First time using /p:suggest!
-
-I'll analyze your project and suggest next steps.
-
-{standard_analysis}
-
-Tip: Use /p:suggest anytime you're wondering "what should I do now?"
-```
-
-## Success Criteria
-
-After using `/p:suggest`, user should:
-- ✅ Know exactly what to do next
-- ✅ Understand WHY that's the best action
-- ✅ Feel motivated to act
-- ✅ Have specific commands to run
-- ✅ Understand their momentum/velocity
+**Incomplete data**: Show partial analysis + tip to use prjct more
+**First time**: Explain purpose + standard analysis

package/templates/commands/sync.md

@@ -1,34 +1,17 @@
 ---
 allowed-tools: [Read, Write, Bash, TodoWrite]
-description: 'Sync project state and generate dynamic agents'
+description: 'Sync state + generate agents'
 ---
 
 # /p:sync
 
 ## Flow
+1. Execute `/p:analyze`
+2. Read `analysis/repo-summary.md`
+3. Generate agents per technology → `agents/`
+4. Log to memory
 
-1. Run: `/p:analyze` → get current state
-2. **Read**: `analysis/repo-summary.md`
-3. **Generate**: Dynamic agents for each technology
-4. Log: changes to `memory/context.jsonl`
-
-## Agent Generation
-
-**See `templates/agents/AGENTS.md` for complete reference** with examples and guidelines.
-
-Use `generator.generateDynamicAgent(name, config)` for each specialist.
+Use: `generateDynamicAgent(name, config)`
 
 ## Response
-
-```
-🔄 Sync complete!
-
-🤖 Agents Generated:
-• {agent_name_1} - {role}
-• {agent_name_2} - {role}
-
-📋 Based on: analysis/repo-summary.md
-💡 See templates/agents/AGENTS.md for generation reference
-
-/p:context
-```
+`🔄 Synced | Generated: {agents} | Next: /p:context`

package/templates/commands/work.md

@@ -0,0 +1,44 @@
+---
+allowed-tools: [Read, Write, GetTimestamp]
+description: 'Show current task or start new one'
+timestamp-rule: 'GetTimestamp() for all timestamps'
+required-agent: auto-detect
+enforce-agent: true
+---
+
+# /p:work
+
+## Flow
+
+**No params**: Show active task from `core/stack.jsonl`
+**With task**: Start new (pause current if exists)
+**With number**: Start task #N from `core/next.md`
+
+### Starting Task
+1. Check active → Pause if exists
+2. Parse input → String or number
+3. **ASSIGN AGENT** → Detect expertise, filter context (70-90% reduction)
+4. Create entry → status='active', agent, filtered_context
+5. Update → `core/stack.jsonl` + `core/now.md`
+6. Log → Agent usage to memory
+
+## Responses
+
+**Active**: `🎯 {task} | {agent} | {duration}`
+**Empty**: `💤 No active task | {paused_count} paused`
+**Started**: `🚀 {task} | Agent: {agent}`
+**Switched**: `⏸️ Paused {old} → Started {new}`
+
+## Agent Detection
+Keywords → Agent:
+- UI/frontend/React → `fe`
+- API/backend/database → `be`
+- design/UX → `ux`
+- test/QA/bug → `qa`
+- docs/README → `docs`
+- else → `general`
+
+## Errors
+**Active exists**: Show options (pause/done/switch)
+**Invalid #**: Task not in queue
+**Migration**: Replaces /p:now and /p:build

package/templates/commands/workflow.md

@@ -1,34 +1,12 @@
 ---
 allowed-tools: [Read, Write]
-description: 'Show workflow status'
+description: 'Workflow status'
 ---
 
 # /p:workflow
 
-## Usage
-
-```
-/p:workflow           # Show status
-/p:workflow skip      # Skip current step
-```
-
 ## Flow
-
-1. Read: `workflow/state.json`
-2. Display: current step + progress
-3. Check: capabilities for next steps
+Read `workflow/state.json` → Show progress
 
 ## Response
-
-```
-🔄 Workflow: {task_type}
-
-Progress: {current}/{total}
-Current: {step_name} ({agent})
-Status: {status}
-
-Next: {next_step}
-{capability_prompt_if_needed}
-
-/p:done | /p:workflow skip
-```
+`🔄 {task} | Step {N}/{total}: {step} ({agent}) | Skip: /p:workflow skip`