prjct-cli 0.4.0

package/templates/workflows/task.md

@@ -0,0 +1,109 @@
+---
+title: prjct task
+invocable_name: p:task
+description: Break down and execute complex tasks systematically using global prjct architecture
+---
+
+# Steps
+
+1. Read project config from `.prjct/prjct.config.json`
+2. Extract `projectId` and `author` from config
+3. Parse task description from arguments
+4. Analyze task complexity and requirements
+5. Break down into subtasks with dependencies
+6. Create task breakdown in `~/.prjct-cli/projects/{projectId}/planning/tasks/{task-id}.md`
+7. Add subtasks to `~/.prjct-cli/projects/{projectId}/core/next.md` with priority
+8. Set first subtask to `~/.prjct-cli/projects/{projectId}/core/now.md`
+9. Log task creation to memory
+10. Display execution plan
+
+# Response Format
+
+```
+📋 Task Breakdown: {task description}
+
+🔍 Analysis:
+- Complexity: {High/Medium/Low}
+- Estimated Time: {timeframe}
+- Dependencies: {list or "None"}
+
+📦 Subtasks Created:
+
+1. 🎯 {subtask 1} (Starting now)
+   - Why: {reason}
+   - Deliverable: {outcome}
+   - Estimate: {time}
+
+2. ⏳ {subtask 2}
+   - Why: {reason}
+   - Deliverable: {outcome}
+   - Estimate: {time}
+   - Depends on: #1
+
+3. ⏳ {subtask 3}
+   - Why: {reason}
+   - Deliverable: {outcome}
+   - Estimate: {time}
+   - Depends on: #2
+
+Total Estimate: {total time}
+
+✅ Actions Taken:
+- Created task breakdown file
+- Added subtasks to priority queue
+- Set first subtask as current focus
+
+🎯 Let's start! Current task:
+{subtask 1 description}
+
+Use /p:done when complete to move to next subtask.
+```
+
+# Task Breakdown Strategy
+
+1. **Understand Requirements**: Analyze what needs to be done
+2. **Identify Dependencies**: What must happen first?
+3. **Define Milestones**: Key deliverables within the task
+4. **Chunk into Subtasks**: Each subtask should be ~1-4 hours
+5. **Sequence Execution**: Order by dependencies and logic
+6. **Estimate Effort**: Realistic time estimates per subtask
+
+# Subtask Characteristics
+
+Good subtasks are:
+- **Atomic**: Can be completed in one session
+- **Testable**: Clear success criteria
+- **Valuable**: Produces tangible progress
+- **Independent**: Minimal blocking dependencies
+- **Sized Right**: 1-4 hours of focused work
+
+# Task Tracking
+
+Task breakdown file created at:
+`~/.prjct-cli/projects/{id}/planning/tasks/{task-id}.md`
+
+Contains:
+- Original task description
+- Analysis and breakdown
+- Subtask list with status
+- Dependencies map
+- Progress tracking
+- Completion notes
+
+# Progress Workflow
+
+1. `/p:task "Complex feature"` - Break down
+2. `/p:now` shows first subtask (auto-set)
+3. `/p:done` when complete → auto-advances to next subtask
+4. Repeat until all subtasks complete
+5. Final `/p:done` marks entire task complete
+6. `/p:ship` to celebrate the feature
+
+# Global Architecture Notes
+
+- **Task Files**: `~/.prjct-cli/projects/{id}/planning/tasks/*.md`
+- **Queue Integration**: `~/.prjct-cli/projects/{id}/core/next.md`
+- **Current Task**: `~/.prjct-cli/projects/{id}/core/now.md`
+- **Memory Logging**: `~/.prjct-cli/projects/{id}/memory/context.jsonl`
+- **Config Location**: `{project}/.prjct/prjct.config.json`
+- **Use Case**: Complex features, refactoring, large implementations

package/templates/workflows/test.md

@@ -0,0 +1,243 @@
+---
+title: prjct test
+invocable_name: p:test
+description: Execute tests with reporting and coverage tracking using global prjct architecture
+---
+
+# Steps
+
+1. Read project config from `.prjct/prjct.config.json`
+2. Extract `projectId` and `author` from config
+3. Parse test type and arguments (unit, integration, e2e, all)
+4. Detect test framework from project analysis
+5. Execute appropriate test suite
+6. Collect test results:
+   - Pass/fail counts
+   - Coverage metrics
+   - Failed test details
+   - Performance metrics
+7. Update test metrics in `~/.prjct-cli/projects/{projectId}/progress/metrics.md`
+8. Log test execution to memory
+9. Display formatted results
+10. Provide actionable suggestions
+
+# Response Format
+
+```
+🧪 Test Execution: {test-type}
+
+Framework: {jest/vitest/pytest/etc}
+Environment: {node-version/python-version}
+
+📊 Results:
+✅ Passed: X tests
+❌ Failed: Y tests
+⏭️  Skipped: Z tests
+⏱️  Duration: A.Bs
+
+📈 Coverage:
+- Statements: {X}%
+- Branches: {Y}%
+- Functions: {Z}%
+- Lines: {A}%
+
+{if-coverage-change}
+Coverage Change: {+/-}% from last run
+{endif}
+
+{if-failures}
+❌ Failed Tests:
+
+1. {test-name}
+   File: {file-path}:{line}
+   Error: {error-message}
+
+2. {test-name}
+   File: {file-path}:{line}
+   Error: {error-message}
+
+🔧 Quick Fixes:
+- Review failing test: {file-path}
+- Check recent changes: git diff
+- Debug: npm test -- --watch
+- Get help: /p:stuck "Test failing: {test-name}"
+{endif}
+
+{if-all-passed}
+✅ All Tests Passed!
+
+🎉 Great work! Test suite is green.
+
+{if-coverage-improved}
+📈 Coverage improved by {X}%!
+{endif}
+
+Next Steps:
+- Ship this: /p:ship "{feature-name}"
+- Mark done: /p:done
+- Continue work: /p:now
+{endif}
+
+💡 Suggestions:
+{coverage-suggestions}
+{performance-suggestions}
+```
+
+# Test Types
+
+## unit (default)
+```
+npm test
+# or
+pytest tests/unit
+# or
+go test ./...
+```
+
+## integration
+```
+npm test -- tests/integration
+# or
+pytest tests/integration
+```
+
+## e2e
+```
+npm run test:e2e
+# or
+playwright test
+# or
+cypress run
+```
+
+## all
+```
+npm run test:all
+# or run all test suites sequentially
+```
+
+## watch
+```
+npm test -- --watch
+# Interactive test watcher
+```
+
+## coverage
+```
+npm test -- --coverage
+# Detailed coverage report
+```
+
+# Framework Detection
+
+Auto-detect test framework:
+- **JavaScript/TypeScript**: Jest, Vitest, Mocha, Jasmine
+- **Python**: Pytest, Unittest, Nose
+- **Go**: Go test
+- **Rust**: Cargo test
+- **Ruby**: RSpec, Minitest
+
+Auto-detect commands from:
+- package.json scripts
+- Makefile
+- Test configuration files
+
+# Coverage Analysis
+
+**Good Coverage**:
+- Statements: >80%
+- Branches: >75%
+- Functions: >80%
+- Lines: >80%
+
+**Suggestions Based on Coverage**:
+- <50%: "Critical: Add basic tests for core functionality"
+- 50-70%: "Add tests for edge cases and error paths"
+- 70-85%: "Good coverage! Focus on complex branches"
+- >85%: "Excellent! Maintain this level"
+
+# Performance Metrics
+
+Track:
+- Total test duration
+- Slowest tests (top 5)
+- Flaky tests (inconsistent results)
+- Test suite trends over time
+
+Suggestions:
+- Tests >5s: "Consider splitting or optimizing"
+- Flaky tests: "Investigate timing or async issues"
+- Growing duration: "Review test efficiency"
+
+# Test Failure Analysis
+
+For each failure:
+1. **Extract Error**: Parse error message and stack trace
+2. **Locate Code**: Find relevant source code
+3. **Check Recent Changes**: Review related commits
+4. **Suggest Fix**: Provide debugging guidance
+
+Common Failure Types:
+- **Assertion Failed**: Expected vs. actual mismatch
+- **Timeout**: Async operation took too long
+- **Exception**: Unhandled error in test
+- **Setup Failed**: Test environment issue
+
+# Continuous Integration
+
+If in CI environment:
+- Adjust output format for CI
+- Generate CI-specific reports
+- Set appropriate exit codes
+- Provide machine-readable output
+
+# Integration with Workflow
+
+## Before Ship
+```
+/p:test all
+# Ensure all tests pass before shipping
+```
+
+## During Development
+```
+/p:test watch
+# Run tests continuously during development
+```
+
+## After Refactoring
+```
+/p:test coverage
+# Ensure coverage didn't drop
+```
+
+## Debug Failures
+```
+/p:test unit
+# Failed? Use /p:stuck "Test failing: {name}"
+```
+
+# Metrics Tracking
+
+Update `~/.prjct-cli/projects/{id}/progress/metrics.md`:
+```markdown
+## Test Metrics
+
+Last Run: {timestamp}
+- Pass Rate: {X}%
+- Coverage: {Y}%
+- Duration: {Z}s
+
+Historical:
+- {date}: {pass-rate}% pass, {coverage}% coverage
+- {date}: {pass-rate}% pass, {coverage}% coverage
+```
+
+# Global Architecture Notes
+
+- **Metrics Location**: `~/.prjct-cli/projects/{id}/progress/metrics.md`
+- **Memory Logging**: `~/.prjct-cli/projects/{id}/memory/context.jsonl`
+- **Config Source**: `{project}/.prjct/prjct.config.json`
+- **Integration**: Part of quality gates before shipping
+- **Trend Analysis**: Track test health over time
+- **Use Case**: Quality assurance, regression prevention, coverage tracking