prjct-cli 0.8.6 → 0.8.8

package/templates/commands/init.md

@@ -31,7 +31,7 @@ description: 'Initialize prjct project (with architect mode for blank projects)'
 6. Create: directory structure + base files
 7. Generate: initial roadmap
 8. Generate: agents
-9. Ask: "¿Empezamos con la primera feature?"
+9. Ask: "Ready to start with the first feature?"
 
 ## Directory Structure
 
@@ -74,97 +74,23 @@ description: 'Initialize prjct project (with architect mode for blank projects)'
 🎯 WHAT DO YOU WANT TO DO FIRST?
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Choose your path:
+5 clear paths:
+1. 🚀 Add feature → /p:feature "{desc}"
+2. 🐛 Fix bug → /p:bug "{desc}"
+3. 🔍 Analyze deeper → /p:analyze
+4. 📊 See status → /p:status or /p:recap
+5. 💡 Not sure? → /p:suggest or /p:help
 
-1. 🚀 Add a new feature
-   Tell me what you want to build!
-
-   Examples:
-   • "add user authentication"
-   • "implement dark mode"
-   • "optimize performance"
-
-   → /p:feature "{description}"
-
-2. 🐛 Fix a bug
-   Describe what's broken
-
-   Example:
-   • "login button not working"
-
-   → /p:bug "{description}"
-
-3. 🔍 Analyze deeper
-   Discover TODOs and improvements
-
-   → /p:analyze
-
-4. 📊 See current status
-   View what's in your project
-
-   → /p:status (visual dashboard)
-   → /p:recap (detailed overview)
-
-5. 💡 Not sure yet?
-   Get personalized suggestions
-
-   → /p:suggest
-   → /p:help
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💬 OR JUST TELL ME:
-
-You can talk naturally:
-  "I want to add authentication"
-  "Help me fix this performance issue"
-  "What should I do?"
-
-I understand! No need to memorize commands.
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
+💬 OR JUST TELL ME: "I want to add authentication" / "What should I do?"
 
 Let's ship something! 🚀
 ```
 
 ## Response: Blank Project
 
-```
-✅ prjct initialized!
-
-📐 ARCHITECT MODE ACTIVATED
-
-Your idea: "{idea}"
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🎨 TECH STACK RECOMMENDATIONS:
-
-Based on your idea, I recommend:
-
-  ⭐ Option 1: Next.js + TypeScript + Tailwind
-     → Best for: Full-stack apps, SEO, modern UI
-     → Why: Fast, scalable, great DX
-
-  Option 2: React + Vite + shadcn/ui
-     → Best for: SPAs, rapid prototyping
-     → Why: Lightweight, flexible
-
-  Option 3: Vue 3 + Nuxt
-     → Best for: Progressive apps, content sites
-     → Why: Easy learning curve, performant
-
-  Custom: Tell me your preference
-     → Any stack works with prjct!
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Which option works for you? (1, 2, 3, or describe your choice)
-
-[After user confirms:]
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
+After ARCHITECT MODE activates and user confirms stack:
 
+```
 ✅ Structure created!
 
 📁 Project: {path}
@@ -176,35 +102,12 @@ Which option works for you? (1, 2, 3, or describe your choice)
 🎯 WHAT'S NEXT?
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Your roadmap is ready! You can:
-
-1. 🚀 Start with first feature (RECOMMENDED)
-   → /p:feature "{first_feature}"
-   I'll break it down and we'll start building
-
-2. 📊 See your roadmap
-   → /p:roadmap
-   View all planned features
-
-3. 🔍 Review project structure
-   → /p:recap
-   See what was created
-
-4. 💡 Modify the plan
-   Just tell me:
-   "I also want to add {feature}"
-   "Let's do {different_feature} first"
+1. 🚀 Start first feature (RECOMMENDED) → /p:feature "{first_feature}"
+2. 📊 See roadmap → /p:roadmap
+3. 🔍 Review structure → /p:recap
+4. 💡 Modify plan → Just tell me
 
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-💬 REMEMBER:
-
-You can talk naturally! Just tell me what you want:
-  "Start with authentication"
-  "Show me the roadmap"
-  "I want to add another feature"
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━
+💬 REMEMBER: Talk naturally! "Start with auth" / "Show roadmap" / "Add another feature"
 
 Ready to start building? 🚀
 ```

package/templates/commands/migrate-all.md

@@ -1,6 +1,9 @@
-# /p:migrate-all - Migrate All Legacy Projects
+---
+allowed-tools: [Read, Write, Bash]
+description: 'Migrate all legacy projects to global storage architecture'
+---
 
-Migrates all legacy prjct projects to the new global storage architecture.
+# /p:migrate-all
 
 ## Usage
 
@@ -8,113 +11,51 @@ Migrates all legacy prjct projects to the new global storage architecture.
 /p:migrate-all [--deep-scan] [--remove-legacy] [--dry-run]
 ```
 
-## What This Command Does
+## What It Does
 
-1. **Scans Global Storage**
-   - Reads all project IDs from `~/.prjct-cli/projects/`
-   - Retrieves project paths from `project.json` files
-
-2. **Detects Legacy Structure**
-   - Checks each project for old `.prjct/` directory structure
-   - Identifies projects that need migration
-
-3. **Migrates Each Project**
-   - Moves data from local `.prjct/` to global `~/.prjct-cli/projects/{id}/`
-   - Creates new minimal local config (`.prjct/prjct.config.json`)
-   - Preserves all project data and history
-
-4. **Cleanup (Optional)**
-   - Removes legacy `.prjct/` directories (with `--remove-legacy`)
-   - Keeps only the new minimal config file
-
-5. **Reports Summary**
-   - Shows migrated, skipped, and failed projects
-   - Lists detailed errors for any failures
+1. **Scans global storage** → Reads all project IDs from `~/.prjct-cli/projects/`
+2. **Detects legacy structure** → Checks each project for old `.prjct/` directory
+3. **Migrates each project** → Moves data from local `.prjct/` to global storage
+4. **Cleanup (optional)** → Removes legacy `.prjct/` directories (with `--remove-legacy`)
+5. **Reports summary** → Shows migrated, skipped, failed counts
 
 ## Options
 
 - `--deep-scan`: Scan entire file system (slow but thorough)
-- `--remove-legacy`: Delete old `.prjct/` directories after successful migration
+- `--remove-legacy`: Delete old `.prjct/` after successful migration
 - `--dry-run`: Show what would be migrated without making changes
 
 ## When to Use
 
-- **After major version updates**: When architecture changes
-- **Upgrading from v0.7.x to v0.8.x**: New global storage system
-- **Consolidating projects**: Moving all projects to global storage
-- **Troubleshooting**: If projects aren't working after update
+- After major version updates (architecture changes)
+- Upgrading from v0.7.x to v0.8.x (new global storage)
+- Troubleshooting projects not working after update
 
-## Migration Process
+## Migration: Before → After
 
-### Before (Legacy Structure)
+**Before (Legacy)**:
 ```
-your-project/
-  .prjct/
-    core/
-    planning/
-    progress/
-    memory/
-    analysis/
-    prjct.config.json  # Full config
+your-project/.prjct/     # All data locally
+  core/, planning/, progress/, memory/, analysis/
 ```
 
-### After (Global Storage)
+**After (Global)**:
 ```
-your-project/
-  .prjct/
-    prjct.config.json  # Minimal (projectId + dataPath only)
-
-~/.prjct-cli/projects/3a5667a5dedb/
-  core/
-  planning/
-  progress/
-  memory/
-  analysis/
-  agents/
-  project.json  # System config (authors, version, etc.)
-```
-
-## Output Example
+your-project/.prjct/
+  prjct.config.json      # Minimal (projectId + dataPath only)
 
+~/.prjct-cli/projects/{id}/
+  core/, planning/, progress/, memory/, analysis/, agents/
 ```
-🔄 Scanning for legacy prjct projects...
-
-📁 Found 3 projects in global storage
-
-🔄 Migrating: /Users/jj/Apps/my-app
-   ✅ Migrated successfully
-
-🔄 Migrating: /Users/jj/Apps/other-project
-   ⏭️  Already migrated
-
-📊 Migration Summary:
-   ✅ Migrated: 1
-   ⏭️  Skipped: 1
-   ❌ Failed: 0
-```
-
-## Error Handling
-
-- **No global storage**: Creates directory structure
-- **Missing project paths**: Skips projects with invalid paths
-- **Permission errors**: Reports which projects couldn't be migrated
-- **Already migrated**: Safely skips without changes
 
 ## Safety
 
 - **Idempotent**: Safe to run multiple times
 - **Non-destructive**: Original files only removed with `--remove-legacy`
-- **Dry run available**: Test migration with `--dry-run` first
+- **Dry run**: Test with `--dry-run` first
 - **Automatic backup**: Legacy data preserved until explicitly removed
 
 ## Requirements
 
 - Write permissions to `~/.prjct-cli/` and project directories
 - Projects must have valid global config in `project.json`
-
-## Notes
-
-- This command does NOT require an initialized prjct project
-- Migration is automatic on install (but manual execution is safer)
-- Always test with `--dry-run` first for large migrations
-- Can be safely interrupted and resumed

package/templates/commands/now.md

@@ -1,6 +1,7 @@
 ---
-allowed-tools: [Read, Write]
+allowed-tools: [Read, Write, GetTimestamp, GetDate]
 description: 'Manage current focus task'
+timestamp-rule: 'CRITICAL - ALWAYS use GetTimestamp() tool for ALL timestamps. NEVER generate timestamps manually. LLM does not know current date/time.'
 ---
 
 # /p:now
@@ -18,9 +19,9 @@ description: 'Manage current focus task'
 
 **Set**:
 
-1. Write: `core/now.md` with task + timestamp
+1. Write: `core/now.md` with task + timestamp (use GetTimestamp() tool)
 2. Update: `core/context.md`, `progress/metrics.md`
-3. Log: `memory/context.jsonl`
+3. Log: `memory/context.jsonl` (use GetTimestamp() tool)
 
 ## Response
 

package/templates/commands/ship.md

@@ -1,6 +1,7 @@
 ---
-allowed-tools: [Read, Write, Bash]
+allowed-tools: [Read, Write, Bash, GetTimestamp, GetDate]
 description: 'Ship feature with complete automated workflow'
+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:ship
@@ -14,94 +15,28 @@ description: 'Ship feature with complete automated workflow'
 
 ## Complete Workflow (Automated)
 
-1. ✅ **Lint checks** → Run project linters
-2. ✅ **Run tests** → Execute test suite (does NOT block if fail)
-3. ✅ **Update docs** → Update relevant documentation
+1. ✅ **Lint checks** → Run linters (non-blocking if fail)
+2. ✅ **Run tests** → Execute test suite (non-blocking if fail)
+3. ✅ **Update docs** → README, API docs, component docs if needed
 4. ✅ **Update version** → Bump version (patch/minor based on changes)
-5. ✅ **Update CHANGELOG** → Add entry with changes
-6. ✅ **Git commit** → Create commit with metadata
+5. ✅ **Update CHANGELOG** → Add entry with metadata
+6. ✅ **Git commit** → With prjct footer format
 7. ✅ **Git push** → Push to remote
-8. ✅ **Recommend compact** → Suggest conversation compacting
+8. ✅ **Log to session** → Append to `progress/sessions/{YYYY-MM}/{YYYY-MM-DD}.jsonl`
+9. ✅ **Update index** → Prepend to `progress/shipped.md` (last 30 days only)
+10. ✅ **Update roadmap** → Mark as complete in `planning/roadmap.md`
+11. ✅ **Recommend compact** → Suggest conversation compacting
 
-## Workflow Steps Detail
-
-### Step 1: Lint Checks
-
-```bash
-npm run lint || yarn lint || pnpm lint
-# If fails: Show errors but continue
-```
-
-### Step 2: Run Tests
-
-```bash
-npm test || yarn test || pnpm test
-# If fails: Show results but DO NOT block (no infinite loop)
-# User decides if acceptable to ship
-```
-
-### Step 3: Update Docs
-
-- Update README if needed
-- Update API docs if endpoints changed
-- Update component docs if UI changed
-
-### Step 4: Update Version
-
-```json
-// package.json
-"version": "X.Y.Z" → "X.Y.(Z+1)"  // patch for fixes
-"version": "X.Y.Z" → "X.(Y+1).0"  // minor for features
-```
-
-### Step 5: Update CHANGELOG
-
-```markdown
-## [X.Y.Z] - YYYY-MM-DD
-
-### Added / Changed / Fixed
-
-- {feature_description}
-- Agent: {agent}
-- Time: {actual_time}
-```
-
-### Step 6-7: Git Commit + Push
-
-Auto-commit with metadata and push
-
-### Step 8: Log to Session
+## Session Log Format
 
 Append to `progress/sessions/{YYYY-MM}/{YYYY-MM-DD}.jsonl`:
 
-```jsonl
-{"ts":"2025-10-04T18:00:00Z","type":"feature_ship","name":"{feature}","tasks_done":{N},"duration":"{Xh}","agent":"{agent}","version":"{X.Y.Z}"}
-```
-
-### Step 9: Update Index
+**Use GetTimestamp() tool for real system time:**
 
-Prepend to `progress/shipped.md` (keep only last 30 days):
-
-```markdown
-## 2025-10-04
-- ✅ {feature_name} ({Xh}, {N} tasks, v{X.Y.Z})
-```
-
-If shipped.md has entries > 30 days old, archive to `progress/archive/shipped-{YYYY-MM}.md`
-
-### Step 10: Update Roadmap
-
-Mark feature as complete in `planning/roadmap.md`:
-
-```markdown
-## Completed
-- [x] {feature_name} - Shipped 2025-10-04
+```jsonl
+{"ts":"{GetTimestamp()}","type":"feature_ship","name":"{feature}","tasks_done":{N},"duration":"{Xh}","agent":"{agent}","version":"{X.Y.Z}"}
 ```
 
-### Step 11: Recommend Compact
-
-Suggest compacting conversation after ship
-
 ## Commit Message Format
 
 ```
@@ -116,7 +51,7 @@ Time: {actual_time}
 Designed for [Claude](https://www.anthropic.com/claude)
 ```
 
-**IMPORTANT**: This footer format MUST be used in ALL commits made by prjct.
+**CRITICAL**: This footer format MUST be used in ALL commits made by prjct.
 
 ## Response
 
@@ -141,8 +76,7 @@ Workflow completed:
 
 ## Important Notes
 
-- **Tests/Lint failures DO NOT block shipping**
-- User sees results and decides
-- Prevents infinite loop of "fix → test → fail → fix"
-- ALWAYS updates version and CHANGELOG
-- ALWAYS commits and pushes if workflow completes
+- **Tests/Lint failures DO NOT block shipping** → User sees results and decides
+- **ALWAYS** updates version and CHANGELOG
+- **ALWAYS** commits and pushes if workflow completes
+- Archive `shipped.md` entries > 30 days to `progress/archive/shipped-{YYYY-MM}.md`