@cluesmith/codev 2.0.0-rc.9 → 2.0.1

package/skeleton/protocols/spider/prompts/implement.md

@@ -1,149 +0,0 @@
-# IMPLEMENT Phase Prompt
-
-You are executing the **IMPLEMENT** phase of the SPIDER protocol.
-
-## Your Goal
-
-Write clean, well-structured code that implements the current plan phase.
-
-## Context
-
-- **Project ID**: {{project_id}}
-- **Project Title**: {{title}}
-- **Current State**: {{current_state}}
-- **Plan Phase**: {{plan_phase}} (if applicable)
-- **Spec File**: `codev/specs/{{project_id}}-{{title}}.md`
-- **Plan File**: `codev/plans/{{project_id}}-{{title}}.md`
-
-## Consultation Context
-
-**Implementation does NOT require consultation checkpoints** - that happens after Defend.
-
-However, you should be aware:
-- Spec and Plan have already been reviewed by GPT-5 Codex and Gemini Pro
-- After you complete Implement + Defend, your work will be reviewed
-- Implementation must strictly follow the approved spec and plan
-
-## Prerequisites
-
-Before implementing, verify:
-1. Previous phase (if any) is committed to git
-2. You've read the plan phase you're implementing
-3. You understand the success criteria for this phase
-4. Dependencies from earlier phases are available
-
-## Process
-
-### 1. Review the Plan Phase
-
-Read the current phase in the plan:
-- What is the objective?
-- What files need to be created/modified?
-- What are the success criteria?
-- What dependencies exist?
-
-### 2. Set Up
-
-- Verify you're on the correct branch
-- Check that previous phase is committed: `git log --oneline -5`
-- Ensure build passes before starting: `npm run build` (or equivalent)
-
-### 3. Implement
-
-Write the code following these principles:
-
-**Code Quality Standards**:
-- Self-documenting code (clear names, obvious structure)
-- No commented-out code
-- No debug prints in final code
-- Explicit error handling
-- Follow project style guide
-
-**Implementation Approach**:
-- Work on one file at a time
-- Make small, incremental changes
-- Test as you go (manual verification is fine here)
-- Document complex logic with comments
-
-### 4. Self-Review
-
-Before signaling completion:
-- Read through all changes
-- Check for obvious bugs
-- Verify code matches the spec requirements
-- Ensure no accidental debug code
-
-### 5. Build Verification
-
-Run build checks using **project-specific commands**:
-
-```bash
-# Check package.json scripts or Makefile for actual commands
-# Common patterns:
-npm run build      # Node.js/TypeScript projects
-npm run typecheck  # TypeScript type checking
-npm run lint       # Linting (ESLint, etc.)
-cargo build        # Rust projects
-go build ./...     # Go projects
-make build         # Projects using Makefiles
-```
-
-**Important**: Don't assume `npm run build` exists. Check `package.json` or equivalent first.
-
-Fix any errors before proceeding.
-
-## Output
-
-- Modified/created source files as specified in the plan phase
-- All build checks passing
-- Code ready for the Defend (testing) phase
-
-## Signals
-
-Emit appropriate signals based on your progress:
-
-- After implementation is complete and builds pass:
-  ```
-  <signal>PHASE_IMPLEMENTED</signal>
-  ```
-
-- If you encounter a blocker:
-  ```
-  <signal>BLOCKED:reason goes here</signal>
-  ```
-
-- If you need spec/plan clarification:
-  ```
-  <signal>NEEDS_CLARIFICATION:specific question</signal>
-  ```
-
-## Important Notes
-
-1. **Follow the plan** - Implement what's specified, not more
-2. **Don't over-engineer** - Simplest solution that works
-3. **Don't skip error handling** - But don't go overboard either
-4. **Keep changes focused** - Only touch files in this phase
-5. **Build must pass** - Don't proceed if build fails
-
-## What NOT to Do
-
-- Don't write tests yet (that's Defend phase)
-- Don't modify files outside this phase's scope
-- Don't add features not in the spec
-- Don't leave TODO comments for later (fix now or note as blocker)
-- Don't commit yet (that happens after Defend + Evaluate)
-- Don't use `git add .` or `git add -A` when you do commit (security risk)
-
-## Handling Problems
-
-**If the plan is unclear**:
-Signal `NEEDS_CLARIFICATION` with your specific question.
-
-**If you discover the spec is wrong**:
-Signal `BLOCKED` and explain the issue. The Architect may need to update the spec.
-
-**If a dependency is missing**:
-Signal `BLOCKED` with details about what's missing.
-
-**If build fails and you can't fix it**:
-Signal `BLOCKED` with the error message.

package/skeleton/protocols/spider/templates/review.md

@@ -1,207 +0,0 @@
-# Review: [Feature/Project Name]
-
-## Metadata
-- **Date**: [YYYY-MM-DD]
-- **Specification**: [Link to codev/specs/spec-file.md]
-- **Plan**: [Link to codev/plans/plan-file.md]
-
-## Executive Summary
-[Brief overview of what was built, how it went, and key outcomes]
-
-## Specification Compliance
-
-### Success Criteria Assessment
-| Criterion | Status | Evidence | Notes |
-|-----------|--------|----------|-------|
-| [Criterion 1] | ✅/❌/⚠️ | [Link/description] | [Any context] |
-| [Criterion 2] | ✅/❌/⚠️ | [Link/description] | [Any context] |
-| [All tests pass >90% coverage] | ✅/❌/⚠️ | [Coverage report] | [Details] |
-| [Performance benchmarks met] | ✅/❌/⚠️ | [Metrics] | [Details] |
-
-### Deviations from Specification
-| Original Requirement | What Was Built | Reason for Deviation |
-|---------------------|----------------|---------------------|
-| [If any] | [Actual] | [Justification] |
-
-## Plan Execution Review
-
-### Phase Completion
-| Phase | Status | Notes |
-|-------|--------|-------|
-| Phase 1 | Complete | [Context] |
-| Phase 2 | Complete | [Context] |
-
-### Deliverables Checklist
-- [x] All planned features implemented
-- [x] Test coverage achieved
-- [x] Documentation updated
-- [x] Performance requirements met
-- [ ] [Any incomplete items]
-
-## Code Quality Assessment
-
-### Architecture Impact
-- **Positive Changes**: [Improvements made to architecture]
-- **Technical Debt Incurred**: [Any shortcuts taken]
-- **Future Considerations**: [What should be refactored later]
-
-### Code Metrics
-- **Lines of Code**: [Added/Modified/Removed]
-- **Test Coverage**: [Percentage and areas covered]
-- **Code Complexity**: [Cyclomatic complexity if measured]
-- **Documentation Coverage**: [Public APIs documented?]
-
-### Security Review
-- **Vulnerabilities Found**: [None/List]
-- **Security Best Practices**: [Followed/Exceptions]
-- **Sensitive Data Handling**: [Properly secured?]
-
-## Performance Analysis
-
-### Benchmarks
-| Metric | Target | Achieved | Status |
-|--------|--------|----------|---------|
-| Response Time (p95) | <200ms | [Actual] | ✅/❌ |
-| Throughput | 1000 rps | [Actual] | ✅/❌ |
-| Memory Usage | <500MB | [Actual] | ✅/❌ |
-
-### Load Testing Results
-[Summary of load testing outcomes, if performed]
-
-## Testing Summary
-
-### Test Execution
-- **Unit Tests**: [X passed, Y failed]
-- **Integration Tests**: [X passed, Y failed]
-- **E2E Tests**: [X passed, Y failed]
-- **Manual Testing**: [Scenarios tested]
-
-### Issues Found During Testing
-| Issue | Severity | Resolution |
-|-------|----------|------------|
-| [Bug 1] | Critical/High/Medium/Low | [Fixed/Deferred] |
-
-## Lessons Learned
-
-### What Went Well
-1. [Success point 1 - be specific]
-2. [Success point 2 - include why it worked]
-3. [Success point 3 - note for future replication]
-
-### What Was Challenging
-1. [Challenge 1 - describe the issue]
-   - **Root Cause**: [Why it happened]
-   - **Resolution**: [How it was addressed]
-   - **Prevention**: [How to avoid in future]
-
-2. [Challenge 2]
-   - **Root Cause**:
-   - **Resolution**:
-   - **Prevention**:
-
-### What Would You Do Differently
-1. [Improvement 1 - be actionable]
-2. [Improvement 2 - be specific]
-3. [Improvement 3 - be realistic]
-
-## Methodology Feedback
-
-### SP(IDE)R Protocol Effectiveness
-- **Specification Phase**: [Was it thorough enough? Too detailed?]
-- **Planning Phase**: [Were estimates accurate? Phases well-sized?]
-- **Implementation Loop**: [Did IDE cycle work well?]
-- **Review Process**: [Is this review capturing the right information?]
-
-### Suggested Improvements
-1. **Template Updates**: [Any template improvements needed?]
-2. **Process Changes**: [Any step modifications recommended?]
-3. **Tool Needs**: [Any automation opportunities?]
-
-## Resource Analysis
-
-### Time Investment
-- **Planned**: [X person-days]
-- **Actual**: [Y person-days]
-- **Variance Explanation**: [Why different?]
-
-### Team Feedback
-- [Feedback from team members]
-- [Collaboration insights]
-- [Communication effectiveness]
-
-## Follow-Up Actions
-
-### Immediate (This Week)
-- [ ] [Action 1 - owner]
-- [ ] [Action 2 - owner]
-
-### Short-term (This Month)
-- [ ] [Action 1 - owner]
-- [ ] [Action 2 - owner]
-
-### Long-term (Future Consideration)
-- [ ] [Improvement opportunity 1]
-- [ ] [Technical debt to address]
-
-## Risk Retrospective
-
-### Identified Risks That Materialized
-| Risk | Impact | How Handled | Prevention for Future |
-|------|--------|-------------|----------------------|
-| [Risk] | [What happened] | [Resolution] | [Learning] |
-
-### Unforeseen Issues
-| Issue | Impact | How Handled | How to Predict |
-|-------|--------|-------------|----------------|
-| [Issue] | [Impact] | [Resolution] | [Detection method] |
-
-## Documentation Updates
-
-### Completed
-- [x] API documentation updated
-- [x] README updated
-- [x] Architecture diagrams revised
-- [ ] [Pending items]
-
-### Knowledge Transfer
-- **Wiki/Confluence Updates**: [Links]
-- **Team Presentations**: [Scheduled/Completed]
-- **Runbooks Created**: [Links]
-
-## Stakeholder Feedback
-- **Product Owner**: [Feedback]
-- **End Users**: [Feedback if available]
-- **Support Team**: [Readiness assessment]
-
-## Final Recommendations
-
-### For Future Similar Projects
-1. [Recommendation 1]
-2. [Recommendation 2]
-
-### For Methodology Evolution
-1. [Suggestion 1]
-2. [Suggestion 2]
-
-## Conclusion
-[Summary statement about the project success, key achievements, and main learnings]
-
-## Appendix
-
-### Links
-- **Code**: [Repository links, PRs]
-- **Documentation**: [All related docs]
-- **Metrics Dashboards**: [Monitoring links]
-- **Test Reports**: [CI/CD links]
-
-### Expert Consultation Summary
-[If expert AI review was performed post-implementation]
-- **Model**: [Which model]
-- **Feedback**: [Key points]
-- **Incorporated Changes**: [What was acted upon]
-
-## Sign-off
-- [ ] Technical Lead Review
-- [ ] Team Retrospective Completed
-- [ ] Lessons Documented
-- [ ] Methodology Updates Proposed