@zigrivers/scaffold 2.1.1 → 2.28.1

package/pipeline/modeling/domain-modeling.md

@@ -2,9 +2,10 @@
 name: domain-modeling
 description: Deep domain modeling across all identified project domains
 phase: "modeling"
-order: 7
+order: 510
 dependencies: [review-user-stories]
 outputs: [docs/domain-models/]
+reads: [coding-standards]
 conditional: null
 knowledge-base: [domain-modeling]
 ---
@@ -17,7 +18,7 @@ Use user stories and their acceptance criteria to discover entities, events,
 and aggregate boundaries. User actions reveal the domain model.
 
 ## Inputs
-- docs/prd.md (required) — requirements defining the problem space
+- docs/plan.md (required) — requirements defining the problem space
 - docs/reviews/pre-review-prd.md (optional) — review findings for context
 - docs/prd-innovation.md (optional) — innovation findings and approved enhancements
 - docs/user-stories.md (required) — user stories with acceptance criteria for domain discovery
@@ -55,3 +56,14 @@ and aggregate boundaries. User actions reveal the domain model.
 If docs/domain-models/ exists, operate in update mode: read existing models,
 identify changes needed based on updated PRD or new understanding. Preserve
 existing decisions unless explicitly revisiting them.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/domain-models/ directory exists with model files
+- **Preserve**: existing entity definitions, aggregate boundaries, domain events,
+  invariants, ubiquitous language terms, bounded context interfaces
+- **Triggers for update**: PRD features added or changed, user stories revealed
+  new domain concepts, innovation suggestions accepted new capabilities,
+  implementation revealed modeling gaps
+- **Conflict resolution**: if a new feature introduces an entity name that
+  conflicts with existing ubiquitous language, resolve by renaming the new
+  entity and documenting the distinction; never silently merge aggregates

package/pipeline/modeling/review-domain-modeling.md

@@ -2,9 +2,9 @@
 name: review-domain-modeling
 description: Review domain models for completeness, consistency, and downstream readiness
 phase: "modeling"
-order: 8
+order: 520
 dependencies: [domain-modeling]
-outputs: [docs/reviews/review-domain-modeling.md]
+outputs: [docs/reviews/review-domain-modeling.md, docs/reviews/domain-modeling/review-summary.md, docs/reviews/domain-modeling/codex-review.json, docs/reviews/domain-modeling/gemini-review.json]
 conditional: null
 knowledge-base: [review-methodology, review-domain-modeling]
 ---
@@ -14,13 +14,19 @@ Deep multi-pass review of the domain models, targeting the specific failure mode
 of domain modeling artifacts. Identify issues, create a fix plan, execute fixes,
 and re-validate.
 
+At depth 4+, dispatches to external AI models (Codex, Gemini) for
+independent review validation.
+
 ## Inputs
 - docs/domain-models/ (required) — domain models to review
-- docs/prd.md (required) — source requirements for coverage checking
+- docs/plan.md (required) — source requirements for coverage checking
 
 ## Expected Outputs
 - docs/reviews/review-domain-modeling.md — review findings, fix plan, and resolution log
 - docs/domain-models/ — updated with fixes
+- docs/reviews/domain-modeling/review-summary.md (depth 4+) — multi-model review synthesis
+- docs/reviews/domain-modeling/codex-review.json (depth 4+, if available) — raw Codex findings
+- docs/reviews/domain-modeling/gemini-review.json (depth 4+, if available) — raw Gemini findings
 
 ## Quality Criteria
 - All review passes executed with findings documented
@@ -28,14 +34,21 @@ and re-validate.
 - Fix plan created for P0 and P1 findings
 - Fixes applied and re-validated
 - Downstream readiness confirmed (decisions phase can proceed)
+- (depth 4+) Multi-model findings synthesized with consensus/disagreement analysis
 
 ## Methodology Scaling
 - **deep**: All review passes from the knowledge base. Full findings report
-  with severity categorization. Fixes applied and re-validated.
+  with severity categorization. Fixes applied and re-validated. Multi-model
+  review dispatched to Codex and Gemini if available, with graceful fallback
+  to Claude-only enhanced review.
 - **mvp**: Quick consistency check. Focus on blocking issues only.
 - **custom:depth(1-5)**: Depth 1-2: blocking issues only. Depth 3: add coverage
-  and consistency passes. Depth 4-5: full multi-pass review.
+  and consistency passes. Depth 4: full multi-pass review + one external model
+  (if CLI available). Depth 5: full multi-pass review + multi-model with
+  reconciliation.
 
 ## Mode Detection
 If docs/reviews/review-domain-modeling.md exists, this is a re-review. Read previous
 findings, check which were addressed, run review passes again on updated models.
+If multi-model review artifacts exist under docs/reviews/domain-modeling/,
+preserve prior findings still valid.

package/pipeline/parity/platform-parity-review.md

@@ -0,0 +1,70 @@
+---
+name: platform-parity-review
+description: Audit all documentation for platform-specific gaps across target platforms
+phase: "parity"
+order: 1010
+dependencies: [review-architecture, review-database, review-api, review-ux]
+outputs: [docs/reviews/platform-parity-review.md, docs/reviews/platform-parity/review-summary.md, docs/reviews/platform-parity/codex-review.json, docs/reviews/platform-parity/gemini-review.json]
+reads: [user-stories, coding-standards, tech-stack, project-structure, tdd]
+conditional: "if-needed"
+knowledge-base: [cross-phase-consistency]
+---
+
+## Purpose
+When the project targets multiple platforms (web, iOS, Android, desktop), audit
+all documentation to ensure every target platform is thoroughly addressed.
+Identify gaps where one platform was assumed but another was not considered,
+verify feature parity across targets, and ensure platform-specific testing,
+input patterns, and UX considerations are documented.
+
+At depth 4+, dispatches to external AI models (Codex, Gemini) for
+independent platform gap analysis.
+
+## Inputs
+- docs/plan.md (required) — target platforms and version requirements
+- docs/tech-stack.md (required) — cross-platform framework and build approach
+- docs/user-stories.md (required) — stories to check for platform coverage
+- docs/coding-standards.md (required) — platform-specific conventions
+- docs/project-structure.md (optional) — platform-specific file organization
+- docs/tdd-standards.md (optional) — platform-specific testing approach
+- docs/design-system.md (optional) — responsive breakpoints and platform patterns
+- docs/implementation-plan.md (optional) — tasks covering each platform
+- CLAUDE.md (required) — platform-specific workflow notes
+
+## Expected Outputs
+- docs/reviews/platform-parity-review.md — platform gap analysis report with
+  findings per document, feature parity matrix, and recommended fixes
+- docs/reviews/platform-parity/review-summary.md (depth 4+) — multi-model review synthesis
+- docs/reviews/platform-parity/codex-review.json (depth 4+, if available) — raw Codex findings
+- docs/reviews/platform-parity/gemini-review.json (depth 4+, if available) — raw Gemini findings
+
+## Quality Criteria
+- All target platforms identified from PRD and tech-stack.md
+- Every user story checked for platform-specific acceptance criteria
+- Feature parity matrix shows which features work on which platforms
+- Input pattern differences documented (touch vs. mouse, keyboard shortcuts, gestures)
+- Platform-specific testing documented (Playwright for web, Maestro for mobile)
+- Navigation patterns appropriate per platform (sidebar vs. tab bar, etc.)
+- Offline/connectivity handling addressed per platform (if applicable)
+- Web version is treated as first-class (not afterthought) if PRD specifies it
+- (depth 4+) Multi-model findings synthesized with consensus/disagreement analysis
+
+## Methodology Scaling
+- **deep**: Comprehensive platform audit across all documents, feature parity
+  matrix, input pattern analysis, navigation pattern review, offline handling,
+  accessibility per platform, and detailed fix recommendations. Multi-model
+  review dispatched to Codex and Gemini if available, with graceful fallback
+  to Claude-only enhanced review.
+- **mvp**: Quick check of user stories and tech-stack for platform coverage.
+  Identify top 3 platform gaps. Skip detailed feature parity matrix.
+- **custom:depth(1-5)**: Depth 1-2: user stories platform check. Depth 3: add
+  tech-stack and coding-standards. Depth 4: add feature parity matrix + one
+  external model (if CLI available). Depth 5: full suite across all documents
+  + multi-model with reconciliation.
+
+## Mode Detection
+Update mode if docs/reviews/platform-parity-review.md exists. In update mode:
+re-run audit against current documents, preserve prior findings still valid,
+note which gaps have been addressed since last review. If multi-model review
+artifacts exist under docs/reviews/platform-parity/, preserve prior findings
+still valid.

package/pipeline/planning/implementation-plan-review.md

@@ -0,0 +1,56 @@
+---
+name: implementation-plan-review
+description: Review implementation tasks for coverage, feasibility, and multi-model validation
+phase: "planning"
+order: 1220
+dependencies: [implementation-plan]
+outputs: [docs/reviews/review-tasks.md, docs/reviews/implementation-plan/task-coverage.json, docs/reviews/implementation-plan/review-summary.md]
+conditional: null
+knowledge-base: [review-methodology, review-implementation-tasks, task-decomposition]
+---
+
+## Purpose
+Review implementation tasks targeting task-specific failure modes: architecture
+coverage gaps, missing dependencies, tasks too large or too vague for agents,
+critical path inaccuracy, and invalid parallelization assumptions. At depth 4+,
+dispatch to independent AI models (Codex/Gemini CLIs) for multi-model validation
+and produce a structured coverage matrix and review summary.
+
+## Inputs
+- docs/implementation-plan.md (required) — tasks to review
+- docs/system-architecture.md (required) — for coverage checking
+- docs/domain-models/ (required) — for completeness
+- docs/user-stories.md (required) — for AC coverage mapping
+- docs/plan.md (required) — for traceability
+- docs/project-structure.md (required) — for file contention analysis
+- docs/tdd-standards.md (required) — for test requirement verification
+
+## Expected Outputs
+- docs/reviews/review-tasks.md — findings and resolution log
+- docs/implementation-plan.md — updated with fixes
+- docs/reviews/implementation-plan/task-coverage.json — AC-to-task coverage matrix (depth 3+)
+- docs/reviews/implementation-plan/review-summary.md — multi-model review summary (depth 4+)
+- docs/reviews/implementation-plan/codex-review.json — raw Codex findings (depth 4+, if available)
+- docs/reviews/implementation-plan/gemini-review.json — raw Gemini findings (depth 4+, if available)
+
+## Quality Criteria
+- Architecture coverage verified (every component has tasks)
+- Dependency graph is valid DAG
+- No task is too large for a single agent session
+- Critical path is accurate
+- Parallelization assumptions are valid
+- Every acceptance criterion maps to at least one task (100% AC coverage)
+- Task descriptions are unambiguous enough for AI agents (agent-implementable)
+- At depth 4+: independent model reviews completed and reconciled
+
+## Methodology Scaling
+- **deep**: Full multi-pass review with multi-model validation. AC coverage
+  matrix. Independent Codex/Gemini dispatches. Detailed reconciliation report.
+- **mvp**: Coverage check only. No external model dispatch.
+- **custom:depth(1-5)**: Depth 1-2: coverage check. Depth 3: add dependency
+  analysis and AC coverage matrix. Depth 4: add one external model. Depth 5:
+  full multi-model with reconciliation.
+
+## Mode Detection
+Re-review mode if previous review exists. If multi-model review artifacts exist
+under docs/reviews/implementation-plan/, preserve prior findings still valid.

package/pipeline/planning/{implementation-tasks.md → implementation-plan.md}

@@ -1,10 +1,11 @@
 ---
-name: implementation-tasks
+name: implementation-plan
 description: Break architecture into implementable tasks with dependencies
 phase: "planning"
-order: 25
-dependencies: [testing-strategy, operations, security]
-outputs: [docs/implementation-tasks.md]
+order: 1210
+dependencies: [tdd, operations, security, review-architecture, create-evals]
+outputs: [docs/implementation-plan.md]
+reads: [create-prd]
 conditional: null
 knowledge-base: [task-decomposition]
 ---
@@ -19,9 +20,9 @@ The primary mapping is Story → Task(s), with PRD as the traceability root.
 - docs/system-architecture.md (required) — components to implement
 - docs/domain-models/ (required) — domain logic to implement
 - docs/adrs/ (required) — technology constraints
-- docs/prd.md (required) — features to trace tasks back to
+- docs/plan.md (required) — features to trace tasks back to
 - docs/user-stories.md (required) — stories to derive tasks from
-- docs/testing-strategy.md (required) — testing requirements to incorporate into tasks
+- docs/tdd-standards.md (required) — testing requirements to incorporate into tasks
 - docs/operations-runbook.md (optional) — ops requirements to incorporate into tasks
 - docs/security-review.md (optional) — security requirements to incorporate into tasks
 - docs/database-schema.md (optional) — data layer tasks
@@ -29,7 +30,7 @@ The primary mapping is Story → Task(s), with PRD as the traceability root.
 - docs/ux-spec.md (optional) — frontend tasks
 
 ## Expected Outputs
-- docs/implementation-tasks.md — task list with dependencies, sizing, and
+- docs/implementation-plan.md — task list with dependencies, sizing, and
   assignment recommendations
 
 ## Quality Criteria
@@ -41,8 +42,10 @@ The primary mapping is Story → Task(s), with PRD as the traceability root.
 - Tasks incorporate security controls from the security review where applicable
 - Tasks incorporate operational requirements (monitoring, deployment) where applicable
 - Critical path is identified
-- Parallelization opportunities are marked
+- Parallelization opportunities are marked with wave plan
 - Every user story maps to at least one task
+- High-risk tasks are flagged with risk type and mitigation
+- Wave summary produced with agent allocation recommendation
 
 ## Methodology Scaling
 - **deep**: Detailed task breakdown with story-to-task tracing. Dependency graph.
@@ -54,4 +57,21 @@ The primary mapping is Story → Task(s), with PRD as the traceability root.
   and sizing. Depth 4-5: full breakdown with parallelization.
 
 ## Mode Detection
-Update mode if tasks exist. Re-derive from updated architecture.
+Check for docs/implementation-plan.md. If it exists, operate in update mode:
+read existing task list and diff against current architecture, user stories,
+and specification documents. Preserve completed task statuses and existing
+dependency relationships. Add new tasks for new stories or architecture
+components. Re-derive wave plan if dependencies changed. Never remove tasks
+that are in-progress or completed.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/implementation-plan.md exists
+- **Preserve**: completed and in-progress task statuses, existing task IDs,
+  dependency relationships for stable tasks, wave assignments for tasks
+  already started, agent allocation history
+- **Triggers for update**: architecture changed (new components need tasks),
+  user stories added or changed, security review identified new requirements,
+  operations runbook added deployment tasks, specification docs changed
+- **Conflict resolution**: if architecture restructured a component that has
+  in-progress tasks, flag for user review rather than silently reassigning;
+  re-derive critical path only for unstarted tasks

package/pipeline/pre/create-prd.md

@@ -2,9 +2,9 @@
 name: create-prd
 description: Create a product requirements document from a project idea
 phase: "pre"
-order: 1
+order: 110
 dependencies: []
-outputs: [docs/prd.md]
+outputs: [docs/plan.md]
 conditional: null
 knowledge-base: [prd-craft]
 ---
@@ -19,7 +19,7 @@ This is the foundation document that all subsequent phases reference.
 - Existing project files (if brownfield — any README, docs, or code)
 
 ## Expected Outputs
-- docs/prd.md — Product requirements document
+- docs/plan.md — Product requirements document
 
 ## Quality Criteria
 - Problem statement is specific and testable (not vague aspirations)
@@ -40,6 +40,15 @@ This is the foundation document that all subsequent phases reference.
   phased delivery.
 
 ## Mode Detection
-If docs/prd.md exists, operate in update mode: read existing content, identify
+If docs/plan.md exists, operate in update mode: read existing content, identify
 what has changed or been learned since it was written, propose targeted updates.
 Preserve existing decisions unless explicitly revisiting them.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/plan.md exists
+- **Preserve**: problem statement, existing feature definitions, success criteria,
+  user personas, and scope boundaries unless user explicitly requests changes
+- **Triggers for update**: user provides new requirements, scope adjustment
+  requested, constraints changed (timeline, budget, team), new user research
+- **Conflict resolution**: new features are appended to the feature list with
+  clear versioning; changed constraints are documented with rationale for change

package/pipeline/pre/innovate-prd.md

@@ -2,9 +2,9 @@
 name: innovate-prd
 description: Discover feature-level innovation opportunities in the PRD
 phase: "pre"
-order: 3
+order: 130
 dependencies: [review-prd]
-outputs: [docs/prd-innovation.md]
+outputs: [docs/prd-innovation.md, docs/reviews/prd-innovation/review-summary.md, docs/reviews/prd-innovation/codex-review.json, docs/reviews/prd-innovation/gemini-review.json]
 conditional: "if-needed"
 knowledge-base: [prd-innovation, prd-craft]
 ---
@@ -15,14 +15,21 @@ new capabilities, competitive positioning, and defensive product gaps. It is
 NOT UX-level enhancement (that belongs in user story innovation) — it focuses
 on whether the right features are in the PRD at all.
 
+At depth 4+, dispatches to external AI models (Codex, Gemini) for
+independent innovation brainstorming — different models surface different
+creative opportunities and competitive insights.
+
 ## Inputs
-- docs/prd.md (required) — PRD to analyze for innovation opportunities
+- docs/plan.md (required) — PRD to analyze for innovation opportunities
 - docs/reviews/pre-review-prd.md (optional) — review findings for context
 
 ## Expected Outputs
 - docs/prd-innovation.md — innovation findings, suggestions with cost/impact
   assessment, and disposition (accepted/rejected/deferred)
-- docs/prd.md — updated with approved innovations
+- docs/plan.md — updated with approved innovations
+- docs/reviews/prd-innovation/review-summary.md (depth 4+) — multi-model innovation synthesis
+- docs/reviews/prd-innovation/codex-review.json (depth 4+, if available) — raw Codex suggestions
+- docs/reviews/prd-innovation/gemini-review.json (depth 4+, if available) — raw Gemini suggestions
 
 ## Quality Criteria
 - Enhancements are feature-level, not UX-level polish
@@ -31,17 +38,39 @@ on whether the right features are in the PRD at all.
 - Approved innovations are documented to the same standard as existing features
 - PRD scope boundaries are respected — no uncontrolled scope creep
 - User approval is obtained before modifying the PRD
+- (depth 4+) Multi-model suggestions deduplicated and synthesized with unique ideas from each model highlighted
 
 ## Methodology Scaling
 - **deep**: Full innovation pass across all categories (competitive research,
   UX gaps, AI-native opportunities, defensive product thinking). Cost/impact
-  matrix. Detailed integration of approved innovations into PRD.
+  matrix. Detailed integration of approved innovations into PRD. Multi-model
+  innovation dispatched to Codex and Gemini if available, with graceful
+  fallback to Claude-only enhanced brainstorming.
 - **mvp**: Not applicable — this step is conditional and skipped in MVP.
 - **custom:depth(1-5)**: Depth 1-2: not typically enabled. Depth 3: quick scan
-  for obvious gaps and missing expected features. Depth 4-5: full innovation
-  pass with evaluation framework.
+  for obvious gaps and missing expected features. Depth 4: full innovation
+  pass + one external model (if CLI available). Depth 5: full innovation pass
+  + multi-model with deduplication and synthesis.
+
+## Conditional Evaluation
+Enable when: project has a competitive landscape section in plan.md, user explicitly
+requests an innovation pass, or the PRD review (review-prd) identifies feature gaps
+or missing capabilities. Skip when: PRD is minimal/exploratory, depth < 3, or user
+explicitly declines innovation.
 
 ## Mode Detection
 If docs/prd-innovation.md exists, this is a re-innovation pass. Read previous
 suggestions and their disposition (accepted/rejected/deferred), focus on new
-opportunities from PRD changes since last run.
+opportunities from PRD changes since last run. If multi-model artifacts exist
+under docs/reviews/prd-innovation/, preserve prior suggestion dispositions.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/prd-innovation.md exists with suggestion
+  dispositions
+- **Preserve**: accepted/rejected/deferred dispositions from prior runs,
+  cost/impact assessments already reviewed by user, multi-model review artifacts
+- **Triggers for update**: PRD scope changed (new features added or removed),
+  user requests re-evaluation of deferred suggestions, new external model
+  available for additional perspectives
+- **Conflict resolution**: if a previously rejected suggestion is now relevant
+  due to PRD changes, re-propose with updated rationale referencing the change

package/pipeline/pre/innovate-user-stories.md

@@ -2,9 +2,9 @@
 name: innovate-user-stories
 description: Discover UX-level enhancements and innovation opportunities in user stories
 phase: "pre"
-order: 6
+order: 160
 dependencies: [review-user-stories]
-outputs: [docs/user-stories-innovation.md]
+outputs: [docs/user-stories-innovation.md, docs/reviews/user-stories-innovation/review-summary.md, docs/reviews/user-stories-innovation/codex-review.json, docs/reviews/user-stories-innovation/gemini-review.json]
 conditional: "if-needed"
 knowledge-base: [user-stories, user-story-innovation]
 ---
@@ -16,14 +16,21 @@ innovation — `innovate-prd`) — it focuses on making existing features better
 through smart defaults,
 progressive disclosure, accessibility improvements, and AI-native capabilities.
 
+At depth 4+, dispatches to external AI models (Codex, Gemini) for
+independent UX innovation brainstorming — different models surface different
+enhancement opportunities.
+
 ## Inputs
 - docs/user-stories.md (required) — stories to enhance
-- docs/prd.md (required) — PRD boundaries (innovation must not exceed scope)
+- docs/plan.md (required) — PRD boundaries (innovation must not exceed scope)
 
 ## Expected Outputs
 - docs/user-stories-innovation.md — innovation findings, suggestions with
   cost/impact assessment, and disposition (accepted/rejected/deferred)
 - docs/user-stories.md — updated with approved enhancements
+- docs/reviews/user-stories-innovation/review-summary.md (depth 4+) — multi-model innovation synthesis
+- docs/reviews/user-stories-innovation/codex-review.json (depth 4+, if available) — raw Codex suggestions
+- docs/reviews/user-stories-innovation/gemini-review.json (depth 4+, if available) — raw Gemini suggestions
 
 ## Quality Criteria
 - Enhancements are UX-level, not new features
@@ -31,17 +38,41 @@ progressive disclosure, accessibility improvements, and AI-native capabilities.
 - Each suggestion has a clear user benefit
 - Approved enhancements are integrated into existing stories (not new stories)
 - PRD scope boundaries are respected — no scope creep
+- (depth 4+) Multi-model suggestions deduplicated and synthesized with unique ideas from each model highlighted
 
 ## Methodology Scaling
 - **deep**: Full innovation pass across all three categories (high-value
   low-effort, differentiators, defensive gaps). Cost/impact matrix.
-  Detailed integration of approved enhancements into stories.
+  Detailed integration of approved enhancements into stories. Multi-model
+  innovation dispatched to Codex and Gemini if available, with graceful
+  fallback to Claude-only enhanced brainstorming.
 - **mvp**: Not applicable — this step is conditional and skipped in MVP.
 - **custom:depth(1-5)**: Depth 1-2: not typically enabled. Depth 3: quick
-  scan for obvious improvements. Depth 4-5: full innovation pass with
-  evaluation framework.
+  scan for obvious improvements. Depth 4: full innovation pass + one external
+  model (if CLI available). Depth 5: full innovation pass + multi-model with
+  deduplication and synthesis.
+
+## Conditional Evaluation
+Enable when: user stories review identifies UX gaps, project targets a consumer-facing
+audience, or progressive disclosure patterns would benefit users. Skip when: stories
+are backend-only with no user-facing UI, depth < 3, or user explicitly declines
+innovation.
 
 ## Mode Detection
 If docs/user-stories-innovation.md exists, this is a re-innovation pass. Read
 previous suggestions and their disposition (accepted/rejected), focus on new
-opportunities from story changes since last run.
+opportunities from story changes since last run. If multi-model artifacts
+exist under docs/reviews/user-stories-innovation/, preserve prior suggestion
+dispositions.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/user-stories-innovation.md exists with
+  suggestion dispositions
+- **Preserve**: accepted/rejected dispositions from prior runs, cost/impact
+  assessments already reviewed, multi-model review artifacts
+- **Triggers for update**: user stories changed (new stories added, existing
+  stories rewritten), PRD innovation accepted new features that need UX
+  enhancement analysis
+- **Conflict resolution**: if a previously rejected UX enhancement is now
+  relevant due to story changes, re-propose with updated rationale; never
+  re-suggest rejected enhancements without a material change in context

package/pipeline/pre/review-prd.md

@@ -2,9 +2,9 @@
 name: review-prd
 description: Multi-pass review of the PRD for completeness, clarity, and downstream readiness
 phase: "pre"
-order: 2
+order: 120
 dependencies: [create-prd]
-outputs: [docs/reviews/pre-review-prd.md]
+outputs: [docs/reviews/pre-review-prd.md, docs/reviews/prd/review-summary.md, docs/reviews/prd/codex-review.json, docs/reviews/prd/gemini-review.json]
 conditional: null
 knowledge-base: [review-methodology, review-prd, prd-craft, gap-analysis]
 ---
@@ -15,13 +15,19 @@ product requirements artifacts. Identify issues, create a fix plan, execute
 fixes, and re-validate. Ensures the PRD is complete, clear, consistent, and
 ready for User Stories to consume.
 
+At depth 4+, dispatches to external AI models (Codex, Gemini) for
+independent review validation.
+
 ## Inputs
-- docs/prd.md (required) — PRD to review
+- docs/plan.md (required) — PRD to review
 - Project idea or brief (context from user, if available)
 
 ## Expected Outputs
 - docs/reviews/pre-review-prd.md — review findings, fix plan, and resolution log
-- docs/prd.md — updated with fixes
+- docs/plan.md — updated with fixes
+- docs/reviews/prd/review-summary.md (depth 4+) — multi-model review synthesis
+- docs/reviews/prd/codex-review.json (depth 4+, if available) — raw Codex findings
+- docs/reviews/prd/gemini-review.json (depth 4+, if available) — raw Gemini findings
 
 ## Quality Criteria
 - All review passes executed with findings documented
@@ -29,16 +35,22 @@ ready for User Stories to consume.
 - Fix plan created for P0 and P1 findings
 - Fixes applied and re-validated
 - Downstream readiness confirmed (User Stories can proceed)
+- (depth 4+) Multi-model findings synthesized with consensus/disagreement analysis
 
 ## Methodology Scaling
 - **deep**: All 8 review passes from the knowledge base. Full findings report
-  with severity categorization. Fixes applied and re-validated.
+  with severity categorization. Fixes applied and re-validated. Multi-model
+  review dispatched to Codex and Gemini if available, with graceful fallback
+  to Claude-only enhanced review.
 - **mvp**: Passes 1-2 only (Problem Statement Rigor, Persona Coverage). Focus
   on blocking gaps — requirements too vague to write stories from.
 - **custom:depth(1-5)**: Depth 1-2: passes 1-2 only (Problem Statement Rigor,
   Persona Coverage). Depth 3: passes 1-4 (add Feature Scoping, Success
-  Criteria). Depth 4-5: all 8 passes.
+  Criteria). Depth 4: all 8 passes + one external model review (if CLI
+  available). Depth 5: all 8 passes + multi-model review with reconciliation.
 
 ## Mode Detection
 If docs/reviews/pre-review-prd.md exists, this is a re-review. Read previous
 findings, check which were addressed, run review passes again on updated PRD.
+If multi-model review artifacts exist under docs/reviews/prd/, preserve prior
+findings still valid.

package/pipeline/pre/review-user-stories.md

@@ -2,9 +2,9 @@
 name: review-user-stories
 description: Multi-pass review of user stories for PRD coverage, quality, and downstream readiness
 phase: "pre"
-order: 5
+order: 150
 dependencies: [user-stories]
-outputs: [docs/reviews/pre-review-user-stories.md]
+outputs: [docs/reviews/pre-review-user-stories.md, docs/reviews/user-stories/requirements-index.md, docs/reviews/user-stories/coverage.json, docs/reviews/user-stories/review-summary.md]
 conditional: null
 knowledge-base: [review-methodology, review-user-stories]
 ---
@@ -14,13 +14,23 @@ Deep multi-pass review of user stories, targeting failure modes specific to
 story artifacts. Identify coverage gaps, quality issues, and downstream
 readiness problems. Create a fix plan, execute fixes, and re-validate.
 
+At higher depths, builds a formal requirements index with traceability matrix
+and optionally dispatches to external AI models (Codex, Gemini) for
+independent coverage validation.
+
 ## Inputs
 - docs/user-stories.md (required) — stories to review
-- docs/prd.md (required) — source requirements for coverage checking
+- docs/plan.md (required) — source requirements for coverage checking
+- docs/reviews/user-stories/ artifacts (optional) — prior review findings in update mode
 
 ## Expected Outputs
 - docs/reviews/pre-review-user-stories.md — review findings, fix plan, and resolution log
 - docs/user-stories.md — updated with fixes
+- docs/reviews/user-stories/requirements-index.md (depth 4+) — atomic requirements
+  extracted from PRD with REQ-xxx IDs
+- docs/reviews/user-stories/coverage.json (depth 4+) — requirement-to-story mapping
+- docs/reviews/user-stories/review-summary.md (depth 5) — multi-model review
+  synthesis with coverage verification
 
 ## Quality Criteria
 - All review passes executed with findings documented
@@ -28,16 +38,23 @@ readiness problems. Create a fix plan, execute fixes, and re-validate.
 - Fix plan created for P0 and P1 findings
 - Fixes applied and re-validated
 - Downstream readiness confirmed (modeling phase can proceed)
+- (depth 4+) Every atomic PRD requirement has a REQ-xxx ID in the requirements index
+- (depth 4+) Coverage matrix maps every REQ to at least one US (100% coverage target)
+- (depth 5) Multi-model findings synthesized with consensus/disagreement analysis
 
 ## Methodology Scaling
 - **deep**: All 6 review passes from the knowledge base. Full findings report
-  with severity categorization. Fixes applied and re-validated.
+  with severity categorization. Fixes applied and re-validated. Requirements
+  index and coverage matrix built. Multi-model review dispatched to Codex and
+  Gemini if available, with graceful fallback to Claude-only enhanced review.
 - **mvp**: Pass 1 only (PRD coverage). Focus on blocking gaps — PRD features
   with no corresponding story.
 - **custom:depth(1-5)**: Depth 1: pass 1 only. Depth 2: passes 1-2.
-  Depth 3: passes 1-4. Depth 4-5: all 6 passes.
+  Depth 3: passes 1-4. Depth 4: all 6 passes + requirements index + coverage
+  matrix. Depth 5: all of depth 4 + multi-model review (if CLIs available).
 
 ## Mode Detection
 If docs/reviews/pre-review-user-stories.md exists, this is a re-review. Read
 previous findings, check which were addressed, run review passes again on
-updated stories.
+updated stories. If docs/reviews/user-stories/requirements-index.md exists,
+preserve requirement IDs — never renumber REQ-xxx IDs.

package/pipeline/pre/user-stories.md

@@ -2,7 +2,7 @@
 name: user-stories
 description: Translate PRD features into user stories with acceptance criteria
 phase: "pre"
-order: 4
+order: 140
 dependencies: [review-prd]
 outputs: [docs/user-stories.md]
 conditional: null
@@ -16,7 +16,7 @@ that are testable and specific enough to drive domain modeling, UX design, and
 task decomposition downstream.
 
 ## Inputs
-- docs/prd.md (required) — features, personas, and requirements to translate
+- docs/plan.md (required) — features, personas, and requirements to translate
 - docs/reviews/pre-review-prd.md (optional) — review findings for context
 - docs/prd-innovation.md (optional) — innovation findings and approved enhancements
 
@@ -46,3 +46,13 @@ task decomposition downstream.
 If docs/user-stories.md exists, operate in update mode: read existing stories,
 identify changes needed based on updated PRD, categorize as ADD/RESTRUCTURE/
 PRESERVE, get approval before modifying. Preserve existing story IDs.
+
+## Update Mode Specifics
+- **Detect prior artifact**: docs/user-stories.md exists
+- **Preserve**: existing story IDs, epic groupings, acceptance criteria that
+  haven't been invalidated, story-to-PRD-feature traceability
+- **Triggers for update**: PRD features added or changed, innovation suggestions
+  accepted, user personas expanded, review findings require story adjustments
+- **Conflict resolution**: never reuse a retired story ID; if a story's scope
+  changed, update its acceptance criteria in-place rather than creating a
+  duplicate story