@windagency/valora 2.0.1

package/data/templates/GUIDED_COMPLETION.md

@@ -0,0 +1,38 @@
+═══════════════════════════════════════════════════════════════════════════
+🎯 CURSOR GUIDED COMPLETION MODE (Zero Config!)
+═══════════════════════════════════════════════════════════════════════════
+
+✨ Good news! You can use your Cursor subscription - no API keys required!
+
+VALORA has prepared structured prompts below. Cursor MCP sampling
+is not yet supported, so please process these prompts using Cursor AI and
+generate the expected output as if it were called directly via API.
+
+This is the intended workflow - everything is working as designed! 🚀
+
+═══════════════════════════════════════════════════════════════════════════
+📋 SYSTEM INSTRUCTIONS
+═══════════════════════════════════════════════════════════════════════════
+
+{{systemPrompt}}
+
+═══════════════════════════════════════════════════════════════════════════
+💬 USER PROMPT
+═══════════════════════════════════════════════════════════════════════════
+
+{{userPrompt}}
+
+═══════════════════════════════════════════════════════════════════════════
+⚙️ GENERATION PARAMETERS
+═══════════════════════════════════════════════════════════════════════════
+
+Model: {{model}}
+Max Tokens: {{maxTokens}}
+Temperature: {{temperature}}
+
+═══════════════════════════════════════════════════════════════════════════
+📝 YOUR RESPONSE BELOW
+═══════════════════════════════════════════════════════════════════════════
+
+Following the system instructions above, please generate your response to
+address the user prompt. Provide a complete, well-structured answer:

package/data/templates/INFRASTRUCTURE_DOC.md

@@ -0,0 +1,138 @@
+# [Document Title]
+
+| Attribute        | Value                       |
+| ---------------- | --------------------------- |
+| **Purpose**      | [Brief purpose description] |
+| **Version**      | 1.0.0                       |
+| **Author**       | AI Documentation Generator  |
+| **Created**      | [YYYY-MM-DD]                |
+| **Last Updated** | [YYYY-MM-DD]                |
+| **Status**       | Draft                       |
+
+---
+
+## Overview
+
+[High-level overview of the document scope and content. Use British English for prose.]
+
+---
+
+## [Main Section 1]
+
+[Content for main section. Include relevant diagrams using Mermaid syntax.]
+
+```mermaid
+flowchart TB
+    A[Component A] --> B[Component B]
+    B --> C[Component C]
+```
+
+### [Subsection 1.1]
+
+[Detailed content]
+
+### [Subsection 1.2]
+
+[Detailed content]
+
+---
+
+## [Main Section 2]
+
+[Content for section 2]
+
+| Column 1 | Column 2 | Column 3 |
+| -------- | -------- | -------- |
+| Value 1  | Value 2  | Value 3  |
+
+---
+
+## Configuration
+
+[Configuration details with code examples using American English]
+
+```yaml
+# Example configuration
+service:
+  name: example-service
+  port: 3000
+  environment: production
+```
+
+---
+
+## Troubleshooting
+
+### Common Issues
+
+| Issue     | Symptoms              | Resolution                |
+| --------- | --------------------- | ------------------------- |
+| [Issue 1] | [Observable symptoms] | [Step-by-step resolution] |
+| [Issue 2] | [Observable symptoms] | [Step-by-step resolution] |
+| [Issue 3] | [Observable symptoms] | [Step-by-step resolution] |
+
+### Diagnostic Commands
+
+```bash
+# Check service status
+systemctl status [service-name]
+
+# View logs
+journalctl -u [service-name] -f
+
+# Test connectivity
+curl -v http://localhost:3000/health
+```
+
+### Escalation Path
+
+1. Check application logs for errors
+2. Verify configuration settings
+3. Check network connectivity
+4. Contact platform team if issue persists
+
+---
+
+## Best Practices
+
+### Do
+
+- Follow infrastructure-as-code principles
+- Implement proper monitoring and alerting
+- Use environment-specific configurations
+- Document all manual interventions
+- Maintain disaster recovery procedures
+
+### Don't
+
+- Store secrets in plain text or version control
+- Make undocumented changes to production
+- Skip testing in staging environments
+- Ignore security advisories
+- Neglect backup verification
+
+### Checklist
+
+- [ ] Infrastructure changes reviewed and approved
+- [ ] Monitoring configured for new components
+- [ ] Documentation updated
+- [ ] Rollback procedure documented
+- [ ] Security scan completed
+
+---
+
+## Related Documentation
+
+| Document                              | Relationship | Description         |
+| ------------------------------------- | ------------ | ------------------- |
+| [Document A](./DOCUMENT_A.md)         | Related      | [Brief description] |
+| [Document B](../domain/DOCUMENT_B.md) | See Also     | [Brief description] |
+| [Document C](./DOCUMENT_C.md)         | Depends On   | [Brief description] |
+
+---
+
+## Changelog
+
+| Version | Date         | Author                     | Changes               |
+| ------- | ------------ | -------------------------- | --------------------- |
+| 1.0.0   | [YYYY-MM-DD] | AI Documentation Generator | Initial documentation |

package/data/templates/PLAN_ARCHITECTURE.md

@@ -0,0 +1,190 @@
+# Architecture Plan: [TASK-ID] - [Task Title]
+
+## Overview
+
+**Task**: [Brief description of the task]
+**Date**: [YYYY-MM-DD]
+**Author**: [Agent/Human]
+
+---
+
+## 1. Technology Choices
+
+### Selected Technologies
+
+| Component         | Technology         | Version      | Rationale         |
+| ----------------- | ------------------ | ------------ | ----------------- |
+| [e.g., Runtime]   | [e.g., Node.js]    | [e.g., 20.x] | [Why this choice] |
+| [e.g., Database]  | [e.g., PostgreSQL] | [e.g., 15]   | [Why this choice] |
+| [e.g., Framework] | [e.g., Express]    | [e.g., 4.x]  | [Why this choice] |
+
+### Alternatives Considered
+
+| Alternative    | Pros       | Cons        | Rejection Reason   |
+| -------------- | ---------- | ----------- | ------------------ |
+| [Technology A] | [Benefits] | [Drawbacks] | [Why not selected] |
+| [Technology B] | [Benefits] | [Drawbacks] | [Why not selected] |
+
+---
+
+## 2. Component Boundaries
+
+### Components Overview
+
+```
+[High-level diagram or ASCII representation]
+
+e.g.:
++----------------+     +----------------+     +----------------+
+|   Frontend     | --> |    API Layer   | --> |   Database     |
+|   (React)      |     |   (Express)    |     |  (PostgreSQL)  |
++----------------+     +----------------+     +----------------+
+                              |
+                              v
+                       +----------------+
+                       | External APIs  |
+                       +----------------+
+```
+
+### Component Responsibilities
+
+| Component     | Responsibility | Boundaries            |
+| ------------- | -------------- | --------------------- |
+| [Component A] | [What it does] | [What it does NOT do] |
+| [Component B] | [What it does] | [What it does NOT do] |
+| [Component C] | [What it does] | [What it does NOT do] |
+
+### Interface Contracts
+
+| Interface     | From        | To          | Contract Type          |
+| ------------- | ----------- | ----------- | ---------------------- |
+| [Interface A] | [Component] | [Component] | [REST/gRPC/Event/etc.] |
+| [Interface B] | [Component] | [Component] | [REST/gRPC/Event/etc.] |
+
+---
+
+## 3. Integration Points
+
+### Internal Integrations
+
+| Integration               | Type         | Protocol           | Data Format     |
+| ------------------------- | ------------ | ------------------ | --------------- |
+| [Service A <-> Service B] | [Sync/Async] | [HTTP/gRPC/Events] | [JSON/Protobuf] |
+
+### External Integrations
+
+| External System    | Purpose              | Authentication  | Rate Limits    |
+| ------------------ | -------------------- | --------------- | -------------- |
+| [e.g., Stripe API] | [Payment processing] | [API Key/OAuth] | [100 req/min]  |
+| [e.g., SendGrid]   | [Email delivery]     | [API Key]       | [1000 req/min] |
+
+### Data Flow
+
+```
+[Data flow diagram or description]
+
+e.g.:
+User Request --> API Gateway --> Auth Middleware --> Route Handler
+    --> Service Layer --> Repository --> Database
+    --> Response Serialisation --> User Response
+```
+
+---
+
+## 4. Key Constraints
+
+### Technical Constraints
+
+| Constraint                            | Impact                               | Mitigation                       |
+| ------------------------------------- | ------------------------------------ | -------------------------------- |
+| [e.g., Must use existing auth system] | [Limits custom auth]                 | [Extend existing, don't replace] |
+| [e.g., Max 200ms response time]       | [No complex queries in request path] | [Use caching, async processing]  |
+
+### Business Constraints
+
+| Constraint                                   | Impact                                 | Mitigation                        |
+| -------------------------------------------- | -------------------------------------- | --------------------------------- |
+| [e.g., Must maintain backward compatibility] | [Cannot change existing API contracts] | [Version API, deprecation period] |
+| [e.g., GDPR compliance required]             | [Data handling restrictions]           | [Implement data anonymisation]    |
+
+### Resource Constraints
+
+| Constraint                    | Impact                        | Mitigation                     |
+| ----------------------------- | ----------------------------- | ------------------------------ |
+| [e.g., Limited team capacity] | [Cannot parallelise work]     | [Sequential implementation]    |
+| [e.g., Budget limits]         | [Cannot use premium services] | [Use open-source alternatives] |
+
+---
+
+## 5. Trade-offs
+
+### Key Trade-off Decisions
+
+| Decision             | Option A                | Option B                   | Chosen | Rationale                           |
+| -------------------- | ----------------------- | -------------------------- | ------ | ----------------------------------- |
+| [e.g., Data storage] | [SQL - ACID guarantees] | [NoSQL - horizontal scale] | [SQL]  | [Data consistency critical]         |
+| [e.g., API style]    | [REST - simplicity]     | [GraphQL - flexibility]    | [REST] | [Team familiarity, simpler caching] |
+
+### Implications of Choices
+
+**Chosen approach enables:**
+
+- [Benefit 1]
+- [Benefit 2]
+
+**Chosen approach limits:**
+
+- [Limitation 1]
+- [Limitation 2]
+
+---
+
+## 6. Go/No-Go Criteria
+
+### Prerequisites (Must be true to proceed)
+
+| #   | Criterion                             | Status        | Evidence         |
+| --- | ------------------------------------- | ------------- | ---------------- |
+| 1   | [Required dependency available]       | [ ] Y / [ ] N | [Link/reference] |
+| 2   | [Required access/permissions granted] | [ ] Y / [ ] N | [Link/reference] |
+| 3   | [Required infrastructure in place]    | [ ] Y / [ ] N | [Link/reference] |
+| 4   | [No blocking technical issues]        | [ ] Y / [ ] N | [Link/reference] |
+
+### Validation Checks
+
+| #   | Check                                      | Status        | Notes |
+| --- | ------------------------------------------ | ------------- | ----- |
+| 1   | Architecture aligns with existing patterns | [ ] Y / [ ] N |       |
+| 2   | No security concerns identified            | [ ] Y / [ ] N |       |
+| 3   | Performance requirements achievable        | [ ] Y / [ ] N |       |
+| 4   | Team has required expertise                | [ ] Y / [ ] N |       |
+
+### Go/No-Go Decision
+
+- [ ] **GO** - Proceed to detailed implementation planning
+- [ ] **NO-GO** - Address blocking issues first
+
+**Blocking issues (if No-Go):**
+
+1. [Issue description and resolution path]
+
+---
+
+## 7. Open Questions
+
+| #   | Question                           | Impact            | Owner    | Due Date |
+| --- | ---------------------------------- | ----------------- | -------- | -------- |
+| 1   | [Question requiring clarification] | [High/Medium/Low] | [Person] | [Date]   |
+| 2   | [Question requiring clarification] | [High/Medium/Low] | [Person] | [Date]   |
+
+---
+
+## Approval
+
+| Role          | Name | Status                      | Date |
+| ------------- | ---- | --------------------------- | ---- |
+| Tech Lead     |      | [ ] Approved / [ ] Rejected |      |
+| Architect     |      | [ ] Approved / [ ] Rejected |      |
+| Product Owner |      | [ ] Approved / [ ] Rejected |      |
+
+**Next Step**: If approved, proceed to `/plan-implementation` for detailed breakdown.

package/data/templates/PLAN_IMPLEMENTATION.md

@@ -0,0 +1,302 @@
+# Implementation Plan: [TASK-ID] - [Task Title]
+
+## Overview
+
+**Task**: [Brief description of the task]
+**Architecture Plan**: [Link to PLAN-ARCH-[TASK-ID].md]
+**Date**: [YYYY-MM-DD]
+**Author**: [Agent/Human]
+**Estimated Effort**: [X story points / hours]
+**Confidence Level**: [High/Medium/Low]
+
+---
+
+## 1. Implementation Steps
+
+### Step 1: [Step Title]
+
+**Objective**: [What this step achieves]
+
+**Files to modify/create**:
+| File Path | Action | Description |
+|-----------|--------|-------------|
+| `src/path/to/file.ts` | Create/Modify/Delete | [What changes] |
+| `src/path/to/file.test.ts` | Create/Modify | [Test coverage] |
+
+**Implementation details**:
+
+```typescript
+// Key code snippets or pseudocode
+```
+
+**Validation criteria**:
+
+- [ ] [Specific outcome to verify]
+- [ ] [Another outcome to verify]
+
+**Rollback procedure**:
+
+```bash
+# Commands to revert this step
+git revert <commit-hash>
+```
+
+---
+
+### Step 2: [Step Title]
+
+**Objective**: [What this step achieves]
+
+**Depends on**: Step 1
+
+**Files to modify/create**:
+| File Path | Action | Description |
+|-----------|--------|-------------|
+| `src/path/to/file.ts` | Create/Modify/Delete | [What changes] |
+
+**Implementation details**:
+
+```typescript
+// Key code snippets or pseudocode
+```
+
+**Validation criteria**:
+
+- [ ] [Specific outcome to verify]
+- [ ] [Another outcome to verify]
+
+**Rollback procedure**:
+
+```bash
+# Commands to revert this step
+```
+
+---
+
+### Step 3: [Step Title]
+
+**Objective**: [What this step achieves]
+
+**Depends on**: Step 1, Step 2
+
+**Files to modify/create**:
+| File Path | Action | Description |
+|-----------|--------|-------------|
+| `src/path/to/file.ts` | Create/Modify/Delete | [What changes] |
+
+**Implementation details**:
+
+```typescript
+// Key code snippets or pseudocode
+```
+
+**Validation criteria**:
+
+- [ ] [Specific outcome to verify]
+- [ ] [Another outcome to verify]
+
+**Rollback procedure**:
+
+```bash
+# Commands to revert this step
+```
+
+---
+
+## 2. Dependency Map
+
+### Execution Order
+
+```
+Step 1 ─────────────────────────────────┐
+                                        │
+Step 2 ─────────────────────────────────┼──▶ Step 4
+                                        │
+Step 3 ─────────────────────────────────┘
+```
+
+### Dependency Matrix
+
+| Step | Depends On | Blocks  | Can Parallelise With |
+| ---- | ---------- | ------- | -------------------- |
+| 1    | -          | 2, 3, 4 | -                    |
+| 2    | 1          | 4       | 3                    |
+| 3    | 1          | 4       | 2                    |
+| 4    | 2, 3       | -       | -                    |
+
+### External Dependencies
+
+| Dependency           | Type           | Source       | Status        |
+| -------------------- | -------------- | ------------ | ------------- |
+| [Package X v2.0]     | npm package    | npm registry | [ ] Available |
+| [API endpoint Y]     | External API   | [Service]    | [ ] Ready     |
+| [Database migration] | Infrastructure | DevOps       | [ ] Complete  |
+
+---
+
+## 3. Risk Mitigations
+
+### Per-Step Risks
+
+| Step | Risk               | Likelihood     | Impact         | Mitigation       |
+| ---- | ------------------ | -------------- | -------------- | ---------------- |
+| 1    | [Risk description] | [High/Med/Low] | [High/Med/Low] | [How to address] |
+| 2    | [Risk description] | [High/Med/Low] | [High/Med/Low] | [How to address] |
+| 3    | [Risk description] | [High/Med/Low] | [High/Med/Low] | [How to address] |
+
+### Fallback Strategies
+
+| Scenario                         | Trigger                     | Fallback Action                     |
+| -------------------------------- | --------------------------- | ----------------------------------- |
+| [e.g., External API unavailable] | [API timeout > 30s]         | [Use cached data / queue for retry] |
+| [e.g., Migration fails]          | [Error in migration script] | [Restore from backup]               |
+| [e.g., Performance regression]   | [Response time > 500ms]     | [Revert and profile]                |
+
+---
+
+## 4. Testing Strategy
+
+### Unit Tests
+
+| Component     | Test File             | Coverage Target | Key Scenarios             |
+| ------------- | --------------------- | --------------- | ------------------------- |
+| [Component A] | `component-a.test.ts` | 80%             | [Happy path, error cases] |
+| [Component B] | `component-b.test.ts` | 80%             | [Edge cases, validation]  |
+
+### Integration Tests
+
+| Integration     | Test File                     | Setup Required       | Key Scenarios           |
+| --------------- | ----------------------------- | -------------------- | ----------------------- |
+| [API endpoints] | `api.integration.test.ts`     | [Testcontainers DB]  | [CRUD operations, auth] |
+| [Service layer] | `service.integration.test.ts` | [Mock external APIs] | [Business workflows]    |
+
+### E2E Tests (if applicable)
+
+| Flow          | Test File        | Setup Required          | Key Scenarios           |
+| ------------- | ---------------- | ----------------------- | ----------------------- |
+| [User flow A] | `flow-a.spec.ts` | [Playwright, seeded DB] | [Complete user journey] |
+
+### Test Commands
+
+```bash
+# Unit tests
+pnpm test:suite:unit
+
+# Integration tests
+pnpm test:suite:integration
+
+# E2E tests
+pnpm test:suite:e2e
+
+# All tests with coverage
+pnpm test:coverage
+```
+
+---
+
+## 5. Rollback Procedures
+
+### Quick Rollback (< 5 minutes)
+
+```bash
+# Revert last commit
+git revert HEAD --no-edit
+
+# Or reset to previous state
+git reset --hard <last-known-good-commit>
+
+# Redeploy
+pnpm deploy:rollback
+```
+
+### Database Rollback (if applicable)
+
+```bash
+# Revert migration
+pnpm db:migrate:down
+
+# Or restore from backup
+pnpm db:restore --backup=<backup-id>
+```
+
+### Feature Flag Rollback (if applicable)
+
+```bash
+# Disable feature flag
+pnpm feature-flag:disable <flag-name>
+```
+
+### Rollback Verification
+
+| Check          | Command                | Expected Result          |
+| -------------- | ---------------------- | ------------------------ |
+| Service health | `curl /health`         | `200 OK`                 |
+| Database state | `pnpm db:check`        | `All migrations applied` |
+| Error rate     | [Monitoring dashboard] | `< 0.1%`                 |
+
+---
+
+## 6. Effort Breakdown
+
+### Per-Step Estimates
+
+| Step      | Effort (Points) | Confidence         | Notes             |
+| --------- | --------------- | ------------------ | ----------------- |
+| 1         | [X]             | [High/Med/Low]     | [Any assumptions] |
+| 2         | [X]             | [High/Med/Low]     | [Any assumptions] |
+| 3         | [X]             | [High/Med/Low]     | [Any assumptions] |
+| **Total** | **[Sum]**       | **[Weighted avg]** |                   |
+
+### Effort Distribution
+
+| Activity         | Percentage | Points |
+| ---------------- | ---------- | ------ |
+| Implementation   | 50%        | [X]    |
+| Testing          | 30%        | [X]    |
+| Documentation    | 10%        | [X]    |
+| Review/Iteration | 10%        | [X]    |
+
+### Confidence Factors
+
+| Factor                       | Status         | Impact on Confidence |
+| ---------------------------- | -------------- | -------------------- |
+| Team familiarity with tech   | [High/Med/Low] | [+/-/=]              |
+| Requirement clarity          | [High/Med/Low] | [+/-/=]              |
+| Dependency availability      | [High/Med/Low] | [+/-/=]              |
+| Similar past implementations | [Yes/No]       | [+/-]                |
+
+---
+
+## 7. Implementation Checklist
+
+### Pre-Implementation
+
+- [ ] Architecture plan approved
+- [ ] Dependencies available
+- [ ] Development environment ready
+- [ ] Test data prepared
+
+### Per-Step Validation
+
+- [ ] Step 1 complete and validated
+- [ ] Step 2 complete and validated
+- [ ] Step 3 complete and validated
+- [ ] All tests passing
+
+### Post-Implementation
+
+- [ ] All acceptance criteria met
+- [ ] Code review completed
+- [ ] Documentation updated
+- [ ] Ready for deployment
+
+---
+
+## Approval
+
+| Role      | Name | Status                      | Date |
+| --------- | ---- | --------------------------- | ---- |
+| Tech Lead |      | [ ] Approved / [ ] Rejected |      |
+| QA Lead   |      | [ ] Approved / [ ] Rejected |      |
+
+**Next Step**: If approved, proceed to `/implement --plan=PLAN-IMPL-[TASK-ID].md`