prjct-cli 0.8.4 → 0.8.8

package/templates/commands/ask.md

@@ -7,380 +7,67 @@ description: 'Conversational intent to action translator - helps users understan
 
 ## Purpose
 
-Translate natural language intent into actionable prjct command flows. Helps users who know WHAT they want but don't know HOW to do it with prjct.
-
-## Usage
-
-```
-/p:ask "<what you want to do>"
-```
+Translate natural language intent into actionable prjct command flows. Helps users who know WHAT they want but don't know HOW.
 
 ## Flow
 
 1. **Understand intent**: Parse user's natural language description
-2. **Analyze context**: Read project state (core/now.md, core/next.md, planning/roadmap.md)
+2. **Analyze context**: Read project state (`core/now.md`, `core/next.md`, `planning/roadmap.md`)
 3. **Recommend flow**: Suggest specific command sequence with explanations
-4. **Offer templates**: If applicable, show examples from similar use cases
-5. **Ask confirmation**: Interactive - don't execute automatically
+4. **Ask confirmation**: Interactive - don't execute automatically
 
 ## Intent Categories
 
-Claude analyzes and maps to one of these patterns:
-
-### 1. Feature Development
-Keywords: "add", "implement", "create", "build", "agregar", "implementar", "crear"
+**1. Feature Development**: "add", "implement", "create", "build"
+→ `/p:feature "{desc}"` → `/p:done` (iterate) → `/p:ship "{name}"`
 
-**Recommended flow:**
-```
-1. /p:feature "{description}"
-   → Value analysis (impact/effort/timing)
-   → Task breakdown
-   → Auto-start first task
-
-2. /p:done (after each task)
-
-3. /p:ship "{feature name}" (when complete)
-```
+**2. Performance/Optimization**: "optimize", "improve", "faster", "memory leak"
+→ `/p:feature "optimize {area}"` → `/p:build 1` → `/p:done` → `/p:ship "optimization"`
 
-### 2. Performance/Optimization
-Keywords: "optimize", "improve", "faster", "performance", "memory leak", "optimizar", "mejorar"
+**3. Bug Fixing**: "bug", "error", "fix", "broken", "not working"
+→ `/p:bug "{desc}"` → `/p:build "{bug task}"` → `/p:done` → `/p:ship "bug fixes"`
 
-**Recommended flow:**
-```
-1. /p:feature "optimize {area}"
-   → Break down into measurable tasks:
-     • Profile and identify bottlenecks
-     • Implement specific optimizations
-     • Measure improvements
-     • Document findings
-
-2. /p:build 1 (start with profiling)
-
-3. /p:done (iterate through tasks)
-
-4. /p:ship "performance optimization"
-```
-
-### 3. Bug Fixing
-Keywords: "bug", "error", "fix", "broken", "not working", "arreglar", "error"
-
-**Recommended flow:**
-```
-1. /p:bug "{description}"
-   → Auto-prioritized based on severity
-   → Added to queue
+**4. Design/Architecture**: "design", "architecture", "structure", "plan"
+→ `/p:design {target} --type {architecture|api|component|database|flow}` → `/p:feature "implement {design}"` → `/p:build 1`
 
-2. /p:build "{bug task}" (if high priority)
-
-3. /p:done (when fixed)
-
-4. /p:ship "bug fixes" (if part of larger batch)
-```
-
-### 4. Design/Architecture
-Keywords: "design", "architecture", "structure", "plan", "diseñar", "arquitectura"
-
-**Recommended flow:**
-```
-1. /p:design {target} --type {architecture|api|component|database|flow}
-   → Create design document
-   → Plan implementation
-
-2. /p:feature "implement {design}"
-   → Convert design to tasks
-
-3. /p:build 1 (start implementation)
-```
-
-### 5. Lost/Confused
-Keywords: "don't know", "help", "stuck", "what should", "no sé", "ayuda"
-
-**Recommended flow:**
-```
-1. /p:suggest
-   → Context-aware recommendations
-   → Shows current state
-   → Suggests next best action
-
-OR
-
-2. /p:help
-   → Interactive guide
-   → Shows available commands
-   → Examples
-```
+**5. Lost/Confused**: "don't know", "help", "stuck", "what should"
+→ `/p:suggest` (context-aware recommendations) OR `/p:help` (interactive guide)
 
 ## Response Format
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Entiendo: {interpreted_intent}
+🎯 I understand: {interpreted_intent}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-📊 TU CONTEXTO:
-  • Estado actual: {current_state}
-  • Tareas activas: {active_tasks}
-  • Último ship: {time_ago}
+📊 YOUR CONTEXT:
+  • Current state: {current_state}
+  • Active tasks: {active_tasks}
+  • Last ship: {time_ago}
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-💡 RECOMENDACIÓN DE FLUJO:
+💡 RECOMMENDED FLOW:
 
 {step_by_step_command_flow}
 
-Cada paso explicado:
+Each step explained:
 → {command_1}: {why_this_command}
 → {command_2}: {what_it_does}
 → {command_3}: {expected_outcome}
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-✨ EJEMPLOS SIMILARES:
-
-"{similar_example_1}"
-"{similar_example_2}"
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¿Quieres que ejecute el paso 1?
-[Sí] [No, solo dame las tareas] [Necesito más ayuda]
-```
-
-## Examples
-
-### Example 1: Performance Optimization
-
-**Input:**
-```
-/p:ask "quiero mejorar el performance y evitar memory leaks"
-```
-
-**Output:**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Entiendo: optimización de performance + solución de memory leaks
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 TU CONTEXTO:
-  • Estado actual: sin tarea activa
-  • Tareas en cola: 3
-  • Último ship: hace 2 días
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💡 RECOMENDACIÓN DE FLUJO:
-
-1. /p:feature "optimizar performance y memory leaks"
-
-   Claude analizará y creará tareas como:
-   • Setup profiler (Chrome DevTools/React DevTools)
-   • Identificar memory leaks con heap snapshots
-   • Optimizar re-renders innecesarios
-   • Implementar memoization (useMemo, useCallback)
-   • Code splitting para reducir bundle size
-   • Medir mejoras y documentar
-
-2. /p:build 1
-   → Empezar con el profiling (necesitas datos primero)
-
-3. /p:done
-   → Después de cada tarea completada
-
-4. /p:ship "performance optimization"
-   → Cuando hayas terminado todas las mejoras
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-✨ POR QUÉ ESTE FLUJO:
-
-→ /p:feature: Analiza el valor (impacto alto, esfuerzo medio)
-             Recomienda timing (hacer ahora antes de más features)
-             Breakdown inteligente (primero medir, luego optimizar)
-
-→ /p:build:   Asigna agente apropiado (probablemente FE)
-             Tracking de tiempo
-             Focus en una tarea a la vez
-
-→ /p:done:    Registra progreso
-             Mantiene momentum
-             Mueve a siguiente tarea
-
-→ /p:ship:    Commit + push + celebración
-             Actualiza docs
-             Registra el logro
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¿Empezamos con /p:feature para analizar el valor y crear las tareas?
-```
-
-### Example 2: New Feature
-
-**Input:**
-```
-/p:ask "I want to add user authentication"
+Would you like me to execute step 1?
 ```
 
-**Output:**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 I understand: implement user authentication system
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 YOUR CONTEXT:
-  • Current state: working on "navbar redesign"
-  • Queue: 2 tasks
-  • Last ship: 1 day ago
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚠️  IMPORTANTE: Tienes tarea activa
-
-Opciones:
-
-A) TERMINAR PRIMERO (Recomendado)
-   1. /p:done → Terminar "navbar redesign"
-   2. /p:feature "user authentication"
-   3. /p:build 1 → Empezar auth
-
-B) GUARDAR PARA DESPUÉS
-   1. /p:feature "user authentication"
-      → Se agrega a la cola
-   2. Continúa con navbar
-   3. /p:done cuando termines navbar
-   4. /p:build "authentication" cuando estés listo
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💡 RECOMENDACIÓN:
-
-Termina navbar primero (mantiene focus)
-Luego /p:feature "authentication" hará:
-
-• Análisis de valor (impacto: HIGH)
-• Stack analysis (sugiere: Clerk, Auth0, o custom JWT)
-• Task breakdown:
-  - Setup auth provider
-  - Implement login/signup UI
-  - Protected routes
-  - Session management
-  - Testing
-
-• Auto-start primera tarea
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¿Qué prefieres: A) Terminar navbar primero, o B) Agregar a cola?
-```
-
-### Example 3: Lost/Confused
-
-**Input:**
-```
-/p:ask "no sé qué hacer ahora"
-```
-
-**Output:**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Entiendo: necesitas orientación sobre qué hacer
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 TU CONTEXTO:
-  • Estado actual: sin tarea activa ✅
-  • Tareas en cola: 5 tareas esperando
-  • Último ship: hace 4 días ⚠️
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💡 TE RECOMIENDO:
-
-1. VER TU COLA DE TAREAS
-   /p:next
-   → Muestra las 5 tareas top priority
-   → Ya están priorizadas y listas para trabajar
-
-2. EMPEZAR LA TAREA #1
-   /p:build 1
-   → Empieza automáticamente la tarea top priority
-   → Asigna agente apropiado
-   → Tracking de tiempo
-
-3. VER SUGERENCIAS INTELIGENTES
-   /p:suggest
-   → Analiza tu contexto completo
-   → Recomienda basado en:
-     - Tiempo sin ship (4 días)
-     - Velocidad reciente
-     - Urgencias
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎯 MI SUGERENCIA ESPECÍFICA:
-
-Han pasado 4 días sin ship → Es momento de completar algo
-
-Opción A: Trabaja en tareas de cola
-   /p:next → /p:build 1 → /p:done → /p:ship
-
-Opción B: Crea algo nuevo rápido
-   /p:feature "quick win" → /p:build 1 → ship today
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-¿Qué prefieres?
-1. Ver qué hay en cola (/p:next)
-2. Sugerencias personalizadas (/p:suggest)
-3. Contarme qué tienes en mente
-```
-
-## Key Principles
-
-1. **Conversational**: Natural language, not technical
-2. **Educational**: Explain WHY each command
-3. **Contextual**: Always check project state first
-4. **Interactive**: Ask confirmation, offer choices
-5. **No auto-execution**: Show the path, let user decide
-6. **Bilingual**: Support English and Spanish naturally
-7. **Examples**: Show similar use cases when relevant
-
 ## Validation
 
-- **Optional**: Can run without project initialized
-- **If not initialized**: Suggest `/p:init` first
+- **Optional**: Can run without project initialized (suggests `/p:init` if needed)
 - **Read-only**: Never modifies files, only recommends
 
 ## Edge Cases
 
-### No prjct project
-```
-⚠️  No prjct project here
-
-First, initialize:
-/p:init                    # For existing project
-/p:init "your idea"        # For new project
-
-Then I can help you!
-```
-
-### Very vague request
-```
-🤔 Puedes darme más detalles?
-
-Qué quieres hacer:
-• Agregar nueva funcionalidad?
-• Arreglar algo que no funciona?
-• Mejorar el código existente?
-• No estás seguro?
-
-Cuéntame más y te ayudo a encontrar el comando correcto!
-```
-
-## Success Criteria
-
-After using `/p:ask`, user should:
-- ✅ Understand WHAT commands to use
-- ✅ Understand WHY those commands
-- ✅ Understand the SEQUENCE of actions
-- ✅ Feel confident to proceed
-- ✅ Learn the system while using it
+**No prjct project**: Suggest `/p:init` or `/p:init "idea"` first
+**Vague request**: Ask for more details - feature? bug? optimization? not sure?
+**Active task exists**: Offer options - finish first (recommended) or add to queue

package/templates/commands/build.md

@@ -1,6 +1,7 @@
 ---
-allowed-tools: [Read, Write]
+allowed-tools: [Read, Write, GetTimestamp]
 description: 'Start task with agent assignment'
+timestamp-rule: 'CRITICAL - ALWAYS use GetTimestamp() tool for id and started fields. NEVER generate timestamps manually.'
 ---
 
 # /p:build
@@ -16,18 +17,20 @@ description: 'Start task with agent assignment'
 2. Detect: `TaskSchema.detectAgent(task)` + complexity
 3. Get: GitHub dev from `git config user.name` + remote
 4. Create: task metadata with agent, complexity, estimate
-5. Write: `core/now.md` with frontmatter
+5. Write: `core/now.md` with frontmatter (use GetTimestamp() for id and started)
 
 ## Frontmatter
 
+**Use GetTimestamp() tool for both id and started fields:**
+
 ```yaml
 ---
-id: task-{timestamp}
+id: task-{GetTimestamp()}
 agent: {detected_agent}
 dev: @{github_username}
 complexity: {trivial|simple|moderate|complex|epic}
 estimated: {time_range}
-started: {iso_timestamp}
+started: {GetTimestamp()}
 ---
 {task_description}
 ```

package/templates/commands/feature.md

@@ -1,6 +1,7 @@
 ---
-allowed-tools: [Read, Write, Bash]
+allowed-tools: [Read, Write, Bash, GetTimestamp, GetDate]
 description: 'Value analysis + roadmap + task breakdown + auto-start'
+timestamp-rule: 'CRITICAL - ALWAYS use GetTimestamp() and GetDate() tools for ALL timestamps and dates. NEVER generate dates manually. LLM does not know current date.'
 ---
 
 # /p:feature
@@ -21,128 +22,16 @@ description: 'Value analysis + roadmap + task breakdown + auto-start'
 
 ## Interactive Mode (No Parameters)
 
-When executed without parameters, `/p:feature` enters interactive mode with quick start templates.
+When executed without parameters, show 6 category templates:
 
-### Response: Interactive Mode
+**1. 🎨 UI/UX**: dark mode, redesign, responsiveness, animations
+**2. ⚡ Performance**: load time, memory leaks, code splitting, API speed
+**3. 🔐 Features**: authentication, payments, admin dashboard, notifications
+**4. 🧪 Quality**: unit tests, E2E testing, error tracking, coverage
+**5. 🐛 Bug Fixes**: refactoring, memory leaks, deprecated code, error handling
+**6. 📚 Docs**: API docs, onboarding, developer setup, examples
 
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-💡 WHAT FEATURE DO YOU WANT TO ADD?
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-You can describe freely or choose a template:
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📋 QUICK START TEMPLATES:
-
-1. 🎨 UI/UX Improvements
-   Examples:
-   • "add dark mode"
-   • "redesign dashboard"
-   • "improve mobile responsiveness"
-   • "add animations and transitions"
-
-2. ⚡ Performance Optimization
-   Examples:
-   • "optimize page load time"
-   • "reduce memory leaks"
-   • "implement code splitting"
-   • "improve API response time"
-
-3. 🔐 Features & Functionality
-   Examples:
-   • "implement user authentication"
-   • "add payment system"
-   • "create admin dashboard"
-   • "implement real-time notifications"
-
-4. 🧪 Quality & Testing
-   Examples:
-   • "add unit tests"
-   • "implement E2E testing"
-   • "add error tracking"
-   • "improve code coverage"
-
-5. 🐛 Bug Fixes & Refactoring
-   Examples:
-   • "refactor authentication flow"
-   • "fix memory leaks"
-   • "clean up deprecated code"
-   • "improve error handling"
-
-6. 📚 Documentation & DevX
-   Examples:
-   • "add API documentation"
-   • "create onboarding guide"
-   • "improve developer setup"
-   • "add code examples"
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💬 HOW TO USE:
-
-Choose a number (1-6) or just describe what you want:
-  "I want to add authentication"
-  "Need to optimize performance"
-  "3" (shows feature examples)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-What feature do you want to add?
-```
-
-### Template Category Deep Dive
-
-If user selects a category number (1-6):
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-{CATEGORY_ICON} {CATEGORY_NAME}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Common features in this category:
-
-{template_options_with_descriptions}
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Choose one or describe your own:
-```
-
-**Example for Performance (Category 2):**
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-⚡ PERFORMANCE OPTIMIZATION
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Common features in this category:
-
-1. "Optimize page load time"
-   → Bundle analysis, lazy loading, CDN setup
-   Impact: HIGH | Effort: 6-8h
-
-2. "Reduce memory leaks"
-   → Profiling, cleanup, optimization
-   Impact: HIGH | Effort: 4-6h
-
-3. "Implement code splitting"
-   → Route-based, component-based splitting
-   Impact: MEDIUM | Effort: 3-4h
-
-4. "Improve API response time"
-   → Caching, query optimization, CDN
-   Impact: HIGH | Effort: 6-10h
-
-5. "Optimize rendering performance"
-   → React.memo, useMemo, virtualization
-   Impact: MEDIUM | Effort: 4-6h
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Choose a number or describe your specific need:
-```
+User can: choose category number OR describe freely
 
 ## Flow
 
@@ -158,22 +47,26 @@ Choose a number or describe your specific need:
 
 Append to `planning/sessions/{YYYY-MM}/{YYYY-MM-DD}.jsonl`:
 
+**Use GetTimestamp() and GetDate() tools to get real system time:**
+
 ```jsonl
-{"ts":"2025-10-04T14:30:00Z","type":"feature_add","name":"{feature}","tasks":{N},"impact":"{high/med/low}","effort":"{Xh}","status":"queued"}
+{"ts":"{GetTimestamp()}","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):
 
+**Use GetDate() tool for current date:**
+
 ```markdown
 ## Queued
-- [ ] {feature_name} ({N} tasks, {Xh} estimated) - Added 2025-10-04
+- [ ] {feature_name} ({N} tasks, {Xh} estimated) - Added {GetDate()}
 ```
 
-If roadmap.md > 30 days old entries, archive them to `planning/archive/roadmap-{YYYY-MM}.md`
+If roadmap.md > 30 days old entries, archive to `planning/archive/roadmap-{YYYY-MM}.md`
 
-## Value Analysis
+## Value Analysis Format
 
 ```
 Feature: {description}
@@ -185,20 +78,6 @@ Value Analysis:
 • 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
 
 ```
@@ -213,27 +92,7 @@ Tasks:
 2. {task_2}
 ...
 
-¿Empezamos con tarea 1?
+Ready to start with task 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?"
-```