@pareto4/pp-core 1.11.1 → 1.12.1

package/pp-core/workflows/discovery-sprint/sessions/13-wrap-up.md

@@ -0,0 +1,205 @@
+# Session 13 — Discovery Sprint Wrap-up & Next Steps
+
+> **Lazy-loaded.** Read from `workflows/discovery-sprint.md` Flow 2 Step 1 when facilitating this session.
+> Holds the session's Goal, vault areas, topics and Notes Template, plus its special protocol.
+
+### Session 13: Discovery Sprint Wrap-up & Next Steps
+
+**Goal:** Present consolidated Discovery Sprint findings, deliver the Go / No-Go recommendation, review open items, agree on the transition plan to the build phase, and formally close the Discovery Sprint.
+
+**Vault areas:** (none) — this session reads nothing from the client vault.
+
+**Special Protocol — Cross-Reference (required for Session 13):**
+Before facilitating any topics, execute the **Session 13: Cross-Reference Protocol** (Step 0) at the end of this file. Analyze Sessions 1–12 for inconsistencies, present findings, resolve critical and high issues, and capture results in the notes. This ensures the wrap-up discussion starts from a consistent, verified baseline. The cross-reference must complete before proceeding to the topic-by-topic facilitation of the topics above.
+
+**What We Cover:**
+
+1. **Discovery Sprint summary**
+   *Why it matters: this synthesis is what gets handed to the build team as the single source of truth. Skip when: never — always required to close the sprint.*
+   - What are the key findings across business, technical, and governance dimensions?
+   - Were there any significant surprises or pivots during discovery?
+   - Which assumptions were validated and which were invalidated?
+   - What issues were identified and resolved by the cross-reference analysis?
+
+2. **Project Definition Document (PDD) review**
+   *Why it matters: this is the client's last chance to catch a scoping or architecture error before build starts. Skip when: never — always required before go/no-go.*
+   - Walk through the PDD structure and key sections
+   - Are there sections requiring further refinement?
+   - Does the client agree with documented scope, architecture, and approach?
+
+3. **Go / No-Go assessment**
+   *Why it matters: this is the literal decision gate that authorizes spend on the build phase. Skip when: never — always required.*
+   - Are the business requirements sufficiently clear to begin building?
+   - Is the technical architecture validated and feasible?
+   - Are there blocking risks or unresolved dependencies?
+   - What is the confidence level for the proposed timeline and budget? [needs-business-input]
+
+4. **Open items and parking lot**
+   *Why it matters: unresolved items surfaced here become explicit known-gaps in the handoff, not silent omissions. Skip when: never — always required, even an empty parking lot is worth stating explicitly.*
+   - What items remain unresolved from discovery sessions?
+   - Which items can be deferred to the build phase without risk?
+   - Which items must be resolved before the build phase begins?
+
+5. **Transition plan and next steps**
+   *Why it matters: this is the literal onboarding checklist the build team executes on day one. Skip when: no build phase follows immediately (e.g. discovery was standalone).*
+   - What is the proposed start date for the build phase?
+   - What team onboarding or environment setup is needed?
+   - How will the product backlog be handed over to the development team?
+
+6. **Feedback and lessons learned**
+   *Why it matters: captured lessons improve the next engagement's Discovery Sprint facilitation. Skip when: this was the client's first and only Pareto engagement with no future comparison point.*
+   - What worked well during the Discovery Sprint?
+   - What could be improved for future engagements?
+
+**Notes Template:**
+
+**Go / No-Go Assessment**
+
+| Criterion | Status (Green / Amber / Red) | Notes |
+|-----------|------------------------------|-------|
+| Business requirements clarity | | |
+| Technical architecture feasibility | | |
+| Security and compliance readiness | | |
+| Integration dependencies resolved | | |
+| Team and budget availability | | |
+| Timeline confidence | | |
+| Stakeholder alignment | | |
+| **Overall Recommendation** | | |
+
+**Open Items Register**
+
+| ID | Item | Source Session | Priority (H/M/L) | Must Resolve Before Build? | Owner | Target Date | Status |
+|----|------|---------------|-------------------|---------------------------|-------|-------------|--------|
+| OI-1 | | | | | | | |
+
+**Cross-Reference Analysis Results**
+
+| Metric | Count | Notes |
+|--------|-------|-------|
+| Total findings | | |
+| Critical | | |
+| High | | |
+| Medium | | |
+| Low | | |
+| Fixes applied | | |
+| Findings deferred | | |
+
+**Transition Plan**
+
+| Activity | Description | Owner | Target Date | Status |
+|----------|-------------|-------|-------------|--------|
+| Build phase kick-off | | | | |
+| Team onboarding | | | | |
+| Environment provisioning | | | | |
+| Backlog handover | | | | |
+| First sprint planning | | | | |
+
+**Lessons Learned**
+
+| Category | What Went Well | What Could Improve | Action for Next Time |
+|----------|----------------|--------------------|----------------------|
+| Facilitation | | | |
+| Stakeholder engagement | | | |
+| Documentation | | | |
+| Logistics | | | |
+
+**Key Decisions**
+
+| # | Decision | Rationale | Owner | Date |
+|---|----------|-----------|-------|------|
+| | | | | |
+
+**Action Items**
+
+| # | Action | Owner | Due Date | Status |
+|---|--------|-------|----------|--------|
+| | | | | |
+
+---
+
+## Session 13: Cross-Reference Protocol
+
+**Run this protocol (Step 0) before facilitating Session 13 topics.**
+This ensures all inconsistencies across Sessions 1–12 are identified and resolved before the wrap-up discussion begins.
+
+### Step 0: Cross-Reference Analysis
+
+**Engine gates (D-07/D-19/D-42/D-52) — run before 0a:** Read `${PP_TOOLS%/bin/pp-tools.cjs}/workflows/discovery-sprint/session-13-gates.md` and run every gate it defines, in order. Each must exit 0 — or take its own documented absent-artifact arm — before the cross-reference analysis begins.
+
+#### 0a. Launch Parallel Cross-Reference Analysis
+
+Analyze all prior sessions in three groups. Use Explore agents if available, or perform the analysis sequentially:
+
+| Group | Sessions | Focus |
+|-------|----------|-------|
+| Business Functional | 1–4 (Kick-off, As-Is, To-Be, UX) | Scope alignment, requirement consistency, persona/role naming, process definitions |
+| Technical | 5–8 (Architecture, Security, Identity, Integration) | Technology stack consistency, role/RBAC alignment, integration point definitions, API contracts |
+| Governance & Costs | 9–12 (QA, Infrastructure, Roadmap, Team) | Timeline feasibility, resource allocation, test strategy alignment, sprint capacity |
+
+For each group: read all session files AND `.planning/discovery/_context.md`. Cross-reference factual claims, role names, technology choices, integration points, and requirement IDs. Check for contradictions between sessions.
+
+#### 0b. Issue Severity Categories
+
+| Severity | Description |
+|----------|-------------|
+| Critical | Contradictions causing build failures or incorrect implementation |
+| High | Significant inconsistencies affecting multiple sessions |
+| Medium | Naming/terminology inconsistencies |
+| Low | Minor administrative issues |
+
+#### 0c. Cross-Reference Checklist
+
+- [ ] **Roles & RBAC:** Same role names, count, and permissions across all sessions (especially S5 vs S7)
+- [ ] **Technology stack:** Consistent tools/frameworks referenced (especially S5, S8, S10)
+- [ ] **Integration points:** Same systems, directions, and protocols across S5, S8, S10
+- [ ] **Requirements traceability:** Every S3 requirement addressable in S5 architecture
+- [ ] **Requirements roll-up:** `discovery rollup --check` exits 0 (totals block matches table)
+- [ ] **Pre-fill/confidential gate:** `discovery input-check` exits 0 (no unconfirmed markers, no tracked confidential files)
+- [ ] **Research-track gate:** `discovery research-check` exits 0 (no structural faults, no stale ⚠️ markers)
+- [ ] **Screen-traceability gate:** `discovery screen-check` exits 0 (no structural faults, every MVP requirement placed on a screen or in the no-screen bucket, no discovery instrumentation in the build tree)
+- [ ] **Scope boundaries:** In-scope/out-of-scope consistent between S1, S3, S11
+- [ ] **Stakeholder names:** Consistent across all sessions
+- [ ] **KPIs and metrics:** Consistent definitions between S1, S3, S11
+- [ ] **Security constraints:** S6 constraints reflected in S5 and S10
+- [ ] **Test strategy:** S9 covers all S3 requirements and S5 components
+- [ ] **Timeline and capacity:** S11 roadmap feasible given S12 team and S9 test needs
+- [ ] **Action items:** No duplicates or contradictions in `_progress.md`
+
+#### 0d. Present Findings
+
+After analysis, consolidate findings into a single report grouped by severity:
+
+```
+Cross-Reference Analysis Complete
+
+Found: X findings (C critical, H high, M medium, L low)
+
+Critical/High Issues:
+1. [C1] Description — Sessions affected — Recommended fix
+
+Medium Issues:
+1. [M1] Description — Sessions affected — Recommended fix
+
+Low Issues:
+1. [L1] Description — Sessions affected — Recommended fix
+```
+
+#### 0e. Resolve Issues
+
+Ask the user how to proceed (AskUserQuestion or text-mode numbered list):
+
+1. Fix all + discuss planning (Recommended)
+2. Fix critical/high only — note the rest
+3. Review each finding one by one
+4. Skip cross-reference (not recommended)
+
+Apply fixes using Edit tool across affected session files. Update `.planning/discovery/_context.md` if key facts change.
+
+#### 0f. Record Cross-Reference Results
+
+Capture in `.planning/discovery/session-13.md` notes:
+- Total findings count and severity breakdown
+- List of all fixes applied (file, what changed, why)
+- Any findings deferred or noted but not fixed
+
+Then proceed to Step 5 (Facilitate Session 13 topics).

package/pp-core/workflows/discovery-sprint/templates/context-template.md

@@ -0,0 +1,266 @@
+# Bootstrap Template — .planning/discovery/_context.md
+
+> **Lazy-loaded.** Read this file from `workflows/discovery-sprint.md` — from
+> Flow 2 Step 1, or from the Bootstrap Templates section — when
+> `.planning/discovery/_context.md` is absent (first-ever session on this
+> project). Create that file verbatim from the fenced schema below. The path is
+> fixed under `.planning/discovery/` (T-04-03): never a root-level directory,
+> never an absolute path, never a path containing `..`.
+
+**`.planning/discovery/_context.md`:**
+
+```markdown
+# Cross-Session Context — [PROJECT_NAME]
+
+This file accumulates key outputs from each completed session to provide context for subsequent sessions. It is automatically maintained as sessions are completed.
+
+---
+
+## Session 1: Kick-off Outputs
+_Populated after Session 1 completion_
+
+### Project Context
+<!-- Notes about the rationale and context -->
+
+### Business Vision
+<!-- Business vision summary, KPIs -->
+
+### Stakeholders
+<!-- Key stakeholder list with roles -->
+
+### Discovery Sprint Scope
+**In Scope:**
+-
+
+**Out of Scope:**
+-
+
+---
+
+## Session 2: As-Is Outputs
+_Populated after Session 2 completion_
+
+### Core Processes
+<!-- Current business processes -->
+
+### Pain Points
+<!-- Prioritized pain points -->
+
+### User Personas
+<!-- Key personas and their journeys -->
+
+### Current Systems
+<!-- Systems landscape -->
+
+### Data Flows
+<!-- How information moves today -->
+
+---
+
+## Session 3: To-Be Outputs
+_Populated after Session 3 completion_
+
+### Business Objectives
+<!-- Measurable outcomes and KPIs -->
+
+### MVP Scope
+<!-- What's in/out for MVP -->
+
+### EPICs Summary
+<!-- EPIC registry table -->
+
+### User Stories Summary
+<!-- Story count and distribution -->
+
+### Requirements Summary
+<!-- Copy the rollup:auto totals table verbatim from .planning/discovery/_requirements.md — never hand-count -->
+
+---
+
+## Session 4: UX Design Outputs
+_Populated after Session 4 completion_
+
+### Design Principles
+<!-- Numbered design principles -->
+
+### UX Standards
+<!-- Standards Applied: platform, navigation, language, accessibility — with the frontend/standards/ citation when the client vault carries one, and every D-04 deviation -->
+
+### Key Personas (Refined)
+<!-- Persona categories and interaction patterns -->
+
+### Key Screen Decisions
+<!-- Screen layout decisions -->
+
+### Prototype
+<!-- Session 4 Closing Step answer; per /pp-discovery prototype round: flows validated, open feedback count -->
+
+---
+
+## Session 5: Architecture Outputs
+_Populated after Session 5 completion_
+
+### Target Architecture
+<!-- Platform, architecture style, ownership -->
+
+### Technology Stack
+<!-- Full stack listing -->
+
+### Key Components
+<!-- Module/component list -->
+
+### Integration Points
+<!-- External system integrations -->
+
+### ADRs
+<!-- Architecture Decision Records -->
+
+### Domain Model / Entity Register
+<!-- Entity, key attributes, relationships, owner module -->
+
+---
+
+## Session 6: Security Outputs
+_Populated after Session 6 completion_
+
+### Data Classification
+<!-- Data sensitivity levels -->
+
+### Compliance Framework
+<!-- Standards and regulations -->
+
+### Encryption
+<!-- In-transit, at-rest, key management -->
+
+### Network & Access
+<!-- Network security approach -->
+
+### Audit Logging
+<!-- Logging strategy and retention -->
+
+### Availability
+<!-- SLA targets -->
+
+---
+
+## Session 7: Identity Management Outputs
+_Populated after Session 7 completion_
+
+### RBAC Model
+<!-- Roles and permissions summary -->
+
+### IdP Integration
+<!-- Identity provider details -->
+
+### User Lifecycle
+<!-- Provisioning approach -->
+
+---
+
+## Session 8: Integration Outputs
+_Populated after Session 8 completion_
+
+### External Systems
+<!-- Systems and their interfaces -->
+
+### Interface Patterns
+<!-- Chosen patterns and protocols -->
+
+### Data Exchange
+<!-- Key data flows and formats -->
+
+---
+
+## Session 9: QA Outputs
+_Populated after Session 9 completion_
+
+### Test Strategy
+<!-- Testing approach -->
+
+### Tooling
+<!-- Test management and automation tools -->
+
+### Test Environments
+<!-- Environment list and purposes -->
+
+### Quality Gates
+<!-- Gate definitions -->
+
+### UAT
+<!-- UAT participants, period, criteria -->
+
+---
+
+## Session 10: Infrastructure Outputs
+_Populated after Session 10 completion_
+
+### Infrastructure
+<!-- Cloud/hosting setup -->
+
+### Deployment
+<!-- Deployment strategy -->
+
+### Monitoring
+<!-- Monitoring and alerting approach -->
+
+### Backup & DR
+<!-- Backup and disaster recovery -->
+
+### Go-Live Readiness
+<!-- Readiness checklist status -->
+
+---
+
+## Session 11: Roadmap Outputs
+_Populated after Session 11 completion_
+
+### Project Phases
+<!-- Phase breakdown -->
+
+### Timeline
+<!-- Sprint cadence and key dates -->
+
+### MVP Scope (Confirmed)
+<!-- Must-have vs nice-to-have -->
+
+### Build Order
+<!-- Sprint-by-sprint plan -->
+
+### Key Milestones
+<!-- Milestone dates -->
+
+### Risks
+<!-- Top risks and mitigations -->
+
+---
+
+## Session 12: Delivery Model Outputs
+_Populated after Session 12 completion_
+
+### Team Structure
+<!-- Key roles and people -->
+
+### Governance
+<!-- Governance framework summary -->
+
+### Ceremonies
+<!-- Sprint cadence and meetings -->
+
+### Support Model
+<!-- Post-go-live support approach -->
+
+---
+
+## Session 13: Wrap-up Outputs
+_Populated after Session 13 completion_
+
+### Decision Readiness
+<!-- Go / Conditional Go / No-Go assessment -->
+
+### Open Items
+<!-- Items carried forward -->
+
+### Next Steps
+<!-- Transition plan to execution -->
+```
+