@windagency/valora 2.0.1

package/data/commands/plan-architecture.md

@@ -0,0 +1,269 @@
+---
+name: plan-architecture
+description: Create high-level architectural plan covering technology choices, component boundaries, and integration strategy (Phase 1 of tiered planning)
+experimental: true
+argument-hint: '[--task-id=<id>] [--backlog-file=<path>]'
+allowed-tools:
+  - codebase_search
+  - read_file
+  - grep
+  - list_dir
+  - glob_file_search
+  - run_terminal_cmd # Required for modern CLI tools (jq, yq, rg, fd)
+model: claude-opus-4.5
+agent: lead
+prompts:
+  pipeline:
+    - stage: load
+      prompt: context.load-task
+      required: true
+      inputs:
+        task_id: $ARG_task_id
+        backlog_file: $ARG_backlog_file
+      outputs:
+        - task_details
+        - current_acceptance_criteria
+        - linked_requirements
+    - stage: context
+      prompt: context.analyze-task-context
+      required: true
+      inputs:
+        task_description: $STAGE_load.task_details
+      outputs:
+        - task_scope
+        - affected_components
+        - relevant_files
+        - scope_boundaries
+    - stage: architecture
+      prompt: plan.define-architecture
+      required: true
+      inputs:
+        task_details: $STAGE_load.task_details
+        context_analysis: $STAGE_context.result
+        acceptance_criteria: $STAGE_load.current_acceptance_criteria
+      outputs:
+        - technology_choices
+        - component_boundaries
+        - integration_points
+        - constraints
+        - trade_offs
+        - go_no_go_criteria
+  merge_strategy: sequential
+  rollback_on_failure: context
+  cache_strategy: stage
+  retry_policy:
+    max_attempts: 2
+    backoff_ms: 1000
+    retry_on:
+      - error
+      - validation_failed
+---
+
+# Architecture Planning Command (Phase 1)
+
+## Role
+
+Use the [agent] profile
+
+## Goal
+
+**Create a high-level architectural plan** that establishes technology choices, component boundaries, and integration strategy. This is Phase 1 of the tiered planning approach, designed to validate architectural decisions before investing time in detailed implementation planning.
+
+**Primary Objectives**:
+
+1. **Select technologies** - Choose appropriate technologies with rationale
+2. **Define boundaries** - Establish clear component responsibilities
+3. **Map integrations** - Identify internal and external integration points
+4. **Document constraints** - Capture technical and business constraints
+5. **Evaluate trade-offs** - Make and document architectural trade-off decisions
+6. **Gate decision** - Determine if task is ready for detailed planning
+
+**Target duration**: ~5 minutes
+
+**This command answers**: "What is the right architecture for this task?"
+
+## Context
+
+### Input Arguments
+
+```plaintext
+$ARGUMENTS
+```
+
+### Configuration Parameters
+
+```structured
+<details>
+<summary>Architecture Planning Options</summary>
+
+**--task-id** (optional)
+- Explicit task ID to load from BACKLOG.md
+- If not provided, loads most recent task from TODO.md
+
+**--backlog-file** (optional, default: knowledge-base/BACKLOG.md)
+- Path to the backlog file to load task from
+
+</details>
+```
+
+### Available Context
+
+The architecture planning process leverages:
+
+- **Task from BACKLOG.md** - Loaded via task-id
+- **Codebase analysis** - Existing patterns, technologies, constraints
+- **Technical standards** - Required tools and frameworks (pnpm, Vitest, Playwright, etc.)
+
+## Rules
+
+### Technology Stack Requirements (TypeScript Projects)
+
+When planning for a **TypeScript project**, the following technology stack is **MANDATORY**:
+
+| Category                     | Required Tool  | Purpose                         |
+| ---------------------------- | -------------- | ------------------------------- |
+| **Package Manager**          | pnpm           | Dependency management           |
+| **Unit/Integration Testing** | Vitest         | Fast, modern test runner        |
+| **E2E Testing**              | Playwright     | Browser automation              |
+| **Test Containers**          | Testcontainers | Containerised test dependencies |
+
+### Architecture Plan Requirements
+
+Every architecture plan MUST include:
+
+1. **Technology Choices** - Selected technologies with rationale and alternatives considered
+2. **Component Boundaries** - Clear responsibilities and interfaces
+3. **Integration Points** - Internal and external integration mapping
+4. **Constraints** - Technical, business, and resource constraints
+5. **Trade-offs** - Key decisions with implications
+6. **Go/No-Go Criteria** - Prerequisites for proceeding to detailed planning
+
+## Process Steps
+
+### Pipeline Overview
+
+1. **Load Task** (`context.load-task`)
+   - Load task details from BACKLOG.md
+   - Extract acceptance criteria and requirements
+   - Output: Task details, acceptance criteria
+
+2. **Analyse Context** (`context.analyze-task-context`)
+   - Parse requirements and identify affected components
+   - Locate relevant files and patterns
+   - Output: Task scope, affected components, relevant files
+
+3. **Define Architecture** (`plan.define-architecture`)
+   - Select technologies with trade-off analysis
+   - Define component responsibilities and boundaries
+   - Map integration points
+   - Document constraints
+   - Establish go/no-go criteria
+   - Output: Architecture plan sections
+
+### Final Architecture Plan
+
+Compile outputs using the `PLAN_ARCHITECTURE.md` template:
+
+```markdown
+# Architecture Plan: [TASK-ID] - [Task Title]
+
+## Overview
+
+[Task summary and context]
+
+## 1. Technology Choices
+
+[Selected technologies with rationale]
+
+## 2. Component Boundaries
+
+[Component responsibilities and interfaces]
+
+## 3. Integration Points
+
+[Internal and external integrations]
+
+## 4. Key Constraints
+
+[Technical, business, resource constraints]
+
+## 5. Trade-offs
+
+[Key decisions with implications]
+
+## 6. Go/No-Go Criteria
+
+[Prerequisites and validation checks]
+
+## 7. Open Questions
+
+[Items requiring clarification]
+```
+
+## Output Requirements
+
+### Architecture Plan Quality Checklist
+
+- [ ] **Technology choices documented** - With rationale for each
+- [ ] **Alternatives considered** - With rejection reasons
+- [ ] **Component boundaries clear** - Single responsibility per component
+- [ ] **Integration points mapped** - Internal and external
+- [ ] **Constraints explicit** - Technical, business, resource
+- [ ] **Trade-offs documented** - With implications
+- [ ] **Go/No-Go criteria defined** - All prerequisites listed
+
+### Success Criteria
+
+A successful architecture plan enables:
+
+1. **Quick validation** - Stakeholders can assess approach in ~5 minutes
+2. **Go/No-Go decision** - Clear criteria for proceeding
+3. **Foundation for detail** - Sufficient context for implementation planning
+4. **Risk identification** - Major risks visible early
+
+## Document Generation
+
+**File**: `knowledge-base/PLAN-ARCH-[TASK-ID].md`
+
+**Ask user**: "Would you like me to create `knowledge-base/PLAN-ARCH-[TASK-ID].md` with the architecture plan?"
+
+## Command Output Summary
+
+Print the following summary at command completion:
+
+```markdown
+## Architecture Plan Created
+
+**Task**: [TASK-ID] - [Title]
+
+### Architecture Summary
+
+- **Technologies**: [Key technologies selected]
+- **Components**: [N] components defined
+- **Integrations**: [N] integration points
+- **Constraints**: [N] constraints identified
+
+### Go/No-Go Status
+
+- Prerequisites: [X/Y] met
+- Validation checks: [X/Y] passed
+- **Decision**: [GO / NO-GO / PENDING]
+
+### Document Generated
+
+-> `knowledge-base/PLAN-ARCH-[TASK-ID].md`
+
+### Next Step
+
+-> If GO: `/plan-implementation --arch-plan=PLAN-ARCH-[TASK-ID].md`
+-> If NO-GO: Address blocking issues listed above
+```
+
+### Handoff to Next Phase
+
+The architecture plan becomes input to:
+
+- **plan-implementation** - For detailed implementation breakdown (if GO)
+- **review-plan** - For architecture validation (optional)
+
+**Recommended Next Command**: `/plan-implementation` to create detailed implementation plan

package/data/commands/plan-implementation.md

@@ -0,0 +1,312 @@
+---
+name: plan-implementation
+description: Create detailed implementation plan with step-by-step tasks, dependencies, and rollback procedures (Phase 2 of tiered planning)
+experimental: true
+argument-hint: '[--arch-plan=<path>] [--task-id=<id>]'
+allowed-tools:
+  - codebase_search
+  - read_file
+  - grep
+  - list_dir
+  - glob_file_search
+  - run_terminal_cmd # Required for modern CLI tools (jq, yq, rg, fd)
+model: claude-opus-4.5
+agent: lead
+prompts:
+  pipeline:
+    - stage: load-arch
+      prompt: context.load-architecture-plan
+      required: true
+      inputs:
+        arch_plan: $ARG_arch_plan
+        task_id: $ARG_task_id
+      outputs:
+        - architecture_decisions
+        - technology_choices
+        - component_boundaries
+        - integration_points
+        - constraints
+    - stage: dependencies
+      prompt: plan.identify-dependencies
+      required: true
+      inputs:
+        architecture: $STAGE_load-arch.result
+      outputs:
+        - technical_dependencies
+        - data_dependencies
+        - integration_dependencies
+        - execution_order
+    - stage: risks
+      prompt: plan.assess-risks
+      required: true
+      inputs:
+        architecture: $STAGE_load-arch.result
+        dependencies: $STAGE_dependencies.result
+      outputs:
+        - technical_risks
+        - business_risks
+        - operational_risks
+        - mitigation_strategies
+        - risk_score
+    - stage: breakdown
+      prompt: plan.breakdown-implementation
+      required: true
+      inputs:
+        architecture: $STAGE_load-arch.result
+        dependencies: $STAGE_dependencies.result
+        risks: $STAGE_risks.result
+      outputs:
+        - implementation_steps
+        - testing_strategy
+        - rollback_strategy
+        - effort_estimate
+  merge_strategy: sequential
+  rollback_on_failure: load-arch
+  cache_strategy: stage
+  retry_policy:
+    max_attempts: 2
+    backoff_ms: 1000
+    retry_on:
+      - error
+      - validation_failed
+---
+
+# Implementation Planning Command (Phase 2)
+
+## Role
+
+Use the [agent] profile
+
+## Goal
+
+**Create a detailed implementation plan** with step-by-step tasks, explicit dependencies, risk mitigations, and rollback procedures. This is Phase 2 of the tiered planning approach, building on the approved architecture plan.
+
+**Primary Objectives**:
+
+1. **Break down work** - Create atomic, executable implementation steps
+2. **Map dependencies** - Explicit technical, data, and integration dependencies
+3. **Mitigate risks** - Per-step risk identification with mitigation strategies
+4. **Define testing** - Comprehensive testing strategy (unit/integration/E2E)
+5. **Plan rollback** - Quick rollback procedures for each step
+6. **Estimate effort** - Realistic effort estimates with confidence levels
+
+**Target duration**: ~10 minutes
+
+**This command answers**: "How exactly should we implement this task?"
+
+## Context
+
+### Input Arguments
+
+```plaintext
+$ARGUMENTS
+```
+
+### Configuration Parameters
+
+```structured
+<details>
+<summary>Implementation Planning Options</summary>
+
+**--arch-plan** (required if --task-id not provided)
+- Path to approved architecture plan
+- Example: `knowledge-base/PLAN-ARCH-TASK-001.md`
+
+**--task-id** (optional)
+- Task ID to derive architecture plan path
+- Will look for `knowledge-base/PLAN-ARCH-[TASK-ID].md`
+
+</details>
+```
+
+### Prerequisites
+
+This command requires an approved architecture plan:
+
+- Created via `/plan-architecture`
+- Go/No-Go decision: **GO**
+- All prerequisites met
+
+### Available Context
+
+The implementation planning process inherits:
+
+- **Architecture decisions** - From architecture plan
+- **Technology choices** - Selected technologies and rationale
+- **Component boundaries** - Defined responsibilities
+- **Integration points** - Internal and external integrations
+- **Constraints** - Technical, business, resource constraints
+
+## Rules
+
+### Technology Stack Requirements (TypeScript Projects)
+
+Inherit from architecture plan. Ensure all implementation steps use:
+
+| Category                     | Required Tool  |
+| ---------------------------- | -------------- |
+| **Package Manager**          | pnpm           |
+| **Unit/Integration Testing** | Vitest         |
+| **E2E Testing**              | Playwright     |
+| **Test Containers**          | Testcontainers |
+
+### Implementation Plan Requirements
+
+Every implementation plan MUST include:
+
+1. **Implementation Steps** - Atomic steps with file paths and validation criteria
+2. **Dependency Map** - Execution order with parallelisation opportunities
+3. **Risk Mitigations** - Per-step risks with mitigation strategies
+4. **Testing Strategy** - Unit, integration, E2E coverage per step
+5. **Rollback Procedures** - Quick rollback for each step
+6. **Effort Breakdown** - Per-step estimates with confidence levels
+
+### Step Quality Criteria
+
+Each implementation step MUST have:
+
+- **Single objective** - One clear goal per step
+- **File paths** - Specific files to create/modify/delete
+- **Implementation details** - Code snippets or pseudocode
+- **Validation criteria** - How to verify step completion
+- **Rollback procedure** - How to revert if needed
+
+## Process Steps
+
+### Pipeline Overview
+
+1. **Load Architecture Plan** (`context.load-architecture-plan`)
+   - Load approved architecture plan
+   - Extract key decisions and constraints
+   - Output: Architecture decisions, technology choices, boundaries
+
+2. **Identify Dependencies** (`plan.identify-dependencies`)
+   - Map technical, data, integration dependencies
+   - Determine execution order
+   - Identify parallelisation opportunities
+   - Output: Dependency graph, execution order, critical path
+
+3. **Assess Risks** (`plan.assess-risks`)
+   - Identify per-step risks
+   - Define mitigation strategies
+   - Establish fallback procedures
+   - Output: Risk registry, mitigations, risk score
+
+4. **Break Down Implementation** (`plan.breakdown-implementation`)
+   - Create atomic implementation steps
+   - Define testing strategy per step
+   - Document rollback procedures
+   - Estimate effort with confidence
+   - Output: Implementation steps, testing strategy, rollback plan, effort
+
+### Final Implementation Plan
+
+Compile outputs using the `PLAN_IMPLEMENTATION.md` template:
+
+```markdown
+# Implementation Plan: [TASK-ID] - [Task Title]
+
+## Overview
+
+[Task summary with link to architecture plan]
+
+## 1. Implementation Steps
+
+[Step-by-step breakdown with file paths]
+
+## 2. Dependency Map
+
+[Execution order and parallelisation]
+
+## 3. Risk Mitigations
+
+[Per-step risks with strategies]
+
+## 4. Testing Strategy
+
+[Unit/integration/E2E coverage]
+
+## 5. Rollback Procedures
+
+[Quick rollback for each step]
+
+## 6. Effort Breakdown
+
+[Per-step estimates with confidence]
+
+## 7. Implementation Checklist
+
+[Pre/post implementation validation]
+```
+
+## Output Requirements
+
+### Implementation Plan Quality Checklist
+
+- [ ] **All steps atomic** - Single objective per step
+- [ ] **File paths explicit** - Specific files for each step
+- [ ] **Dependencies mapped** - Execution order clear
+- [ ] **Risks mitigated** - Each risk has strategy
+- [ ] **Testing complete** - Unit + integration + E2E where applicable
+- [ ] **Rollback documented** - Quick procedure for each step
+- [ ] **Effort estimated** - With confidence level
+
+### Success Criteria
+
+A successful implementation plan enables:
+
+1. **Confident execution** - Engineer can implement without confusion
+2. **Progress tracking** - Can monitor completion by step
+3. **Risk management** - Known risks with mitigation plans
+4. **Quality assurance** - Clear testing approach per step
+5. **Safe rollback** - Can revert any step quickly
+
+## Document Generation
+
+**File**: `knowledge-base/PLAN-IMPL-[TASK-ID].md`
+
+**Ask user**: "Would you like me to create `knowledge-base/PLAN-IMPL-[TASK-ID].md` with the implementation plan?"
+
+## Command Output Summary
+
+Print the following summary at command completion:
+
+```markdown
+## Implementation Plan Created
+
+**Task**: [TASK-ID] - [Title]
+**Architecture Plan**: PLAN-ARCH-[TASK-ID].md
+
+### Plan Summary
+
+- **Steps**: [N] implementation steps
+- **Dependencies**: [N] mapped dependencies
+- **Risks**: [N] identified ([critical] critical)
+- **Risk Level**: [Low | Medium | High]
+
+### Effort Estimate
+
+- **Total**: [X] story points
+- **Confidence**: [High | Medium | Low]
+
+### Documents Generated
+
+-> `knowledge-base/PLAN-IMPL-[TASK-ID].md`
+
+### Quality Gate
+
+-> Run `/review-plan --checklist` to validate before implementation
+
+### Next Step
+
+-> `/implement --plan=PLAN-IMPL-[TASK-ID].md` to start implementation
+```
+
+### Handoff to Next Phase
+
+The implementation plan becomes input to:
+
+- **review-plan** - For validation before implementation
+- **implement** - For direct execution (if plan approved)
+
+**Recommended Next Command**: `/review-plan --checklist` to validate plan quality