@pareto4/pp-core 1.8.2 → 1.9.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pp-core",
   "displayName": "PP Core",
-  "version": "1.8.2",
+  "version": "1.9.0",
   "description": "PP Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
   "author": {
     "name": "pareto4",

package/README.md

@@ -75,6 +75,9 @@ New here? Follow [Your first project](docs/tutorials/your-first-project.md) for
 - [The phase loop](docs/explanation/the-phase-loop.md)
 - [Architecture](docs/ARCHITECTURE.md)
 
+**No lock-in** — pp-core never ships inside the app it helps you build:
+- [Escape hatch](docs/ESCAPE-HATCH.md)
+
 Full index: [docs/README.md](docs/README.md).
 
 ---

package/bin/install.js

@@ -7055,7 +7055,15 @@ function _removeGsdEntries(destDir, kind) {
     return;
   }
   for (const entry of fs.readdirSync(destDir, { withFileTypes: true })) {
-    if (!entry.name.startsWith(kind.prefix)) continue;
+    // Match both the current kind.prefix (now always 'pp-') AND the legacy
+    // 'gsd-' prefix, so a reinstall also prunes stale pre-1.8.0 gsd-<stem>
+    // directories left over from before the pp- rename (#3810/D-13/D-14).
+    // `kind.prefix &&` guards against the empty-string prefix, which is
+    // handled by the whole-namespace early-return above and never reaches
+    // this loop today — defensive only.
+    const matchesCurrentPrefix = kind.prefix && entry.name.startsWith(kind.prefix);
+    const matchesLegacyPrefix = entry.name.startsWith('gsd-');
+    if (!matchesCurrentPrefix && !matchesLegacyPrefix) continue;
     fs.rmSync(path.join(destDir, entry.name), { recursive: true, force: true });
   }
 }

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "pp-core",
-  "version": "1.8.2",
+  "version": "1.9.0",
   "description": "PP Core — a meta-prompting, context engineering, and spec-driven development system for AI coding agents. Loads pp-core's operating context into every Gemini CLI session.",
   "contextFileName": "GEMINI.md"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pareto4/pp-core",
-  "version": "1.8.2",
+  "version": "1.9.0",
   "description": "Pareto pp-core — The Pareto Project's AI-assisted engineering framework: meta-prompting, context engineering, and spec-driven development for AI coding agents.",
   "bin": {
     "pp-core": "bin/install.js",
@@ -52,7 +52,7 @@
     "npm": ">=10.0.0"
   },
   "dependencies": {
-    "@anthropic-ai/claude-agent-sdk": "^0.2.84",
+    "@anthropic-ai/claude-agent-sdk": "^0.3.218",
     "ws": "^8.21.0"
   },
   "devDependencies": {
@@ -70,7 +70,8 @@
     "typescript-eslint": "^8.60.0"
   },
   "overrides": {
-    "qs": ">=6.15.2"
+    "qs": ">=6.15.2",
+    "@hono/node-server": ">=2.0.5"
   },
   "optionalDependencies": {
     "fallow": "^2.70.0"
@@ -107,6 +108,8 @@
     "lint:changeset": "node scripts/changeset/lint.cjs",
     "lint:docs": "node scripts/lint-docs-required.cjs",
     "lint:legacy-name": "node scripts/lint-legacy-dir-name.cjs",
+    "rename-guard": "node scripts/verify-rename-guard.cjs",
+    "rename-guard:baseline": "node scripts/verify-rename-guard.cjs --update-baseline",
     "ci:test-scope": "node scripts/ci-test-scope.cjs",
     "size:baseline": "node scripts/update-size-baseline.cjs",
     "changeset": "node scripts/changeset/new.cjs",

package/pareto-skills/pp-project-setup/SKILL.md

@@ -6,29 +6,29 @@ description: >
   "new project", "start a project", "create a repo", "set up a client project",
   "new engagement", or "initialise a project". This skill runs a wizard
   that collects project and client context, then automates: GitHub repo creation (via gh CLI),
-  Discovery Sprint framework (13 interactive session templates + methodology guide),
-  Obsidian vault configuration, requirements templates, GitHub project board setup,
-  and an initial commit pushed to GitHub — leaving the team ready to start Discovery immediately.
+  Obsidian vault configuration, requirements templates, project definition template,
+  GitHub project board setup, and an initial commit pushed to GitHub — leaving the team
+  ready to start the Discovery Sprint (via `/pp-discovery 1`) immediately.
   Trigger even for vague requests like "let's start a new project" or "new client, new repo".
 ---
 
 # Pareto Project Setup Skill
 ## From Zero to Discovery — Fully Automated
 
-This skill bootstraps a new Pareto project with a complete Discovery Sprint framework.
+This skill bootstraps a new Pareto project and hands it off to `/pp-discovery` to run the Discovery Sprint.
 
 **What it delivers:**
 - GitHub repository created and configured
-- Discovery Sprint framework (13 interactive session templates + methodology guide)
 - Prototype folder structure (interactive HTML prototype, created during Discovery after Session 4)
 - Obsidian vault configured for project documentation
 - Requirements templates (functional requirements, user stories, test cases)
 - Project Definition template
 - GitHub project board with labels, milestone, and custom fields
 - Initial commit pushed to GitHub
-- Team ready to start Discovery Sprint immediately
+- Team ready to run `/pp-discovery 1` and start the Discovery Sprint immediately
 
 **What it does NOT do:**
+- Discovery Sprint facilitation — `/pp-discovery` is the sole, self-sufficient session source (it bootstraps its own `.planning/discovery/_progress.md` and `_context.md`); this skill does not scaffold a `Discovery/` tree or a Sessions Guide
 - Application scaffolding (backend/frontend code) — do this after Discovery, when the stack is confirmed
 - CI/CD pipeline setup — use `pareto-cicd-setup` after the application is scaffolded
 - Deployment setup — use `pareto-deploy-setup` when ready for staging/production
@@ -120,12 +120,13 @@ Summarise everything before running any commands:
 >
 > I'll:
 > 1. Create the GitHub repo
-> 2. Scaffold the project structure (Discovery + requirements + docs)
-> 3. Set up Discovery Sprint framework (13 session templates + methodology guide)
+> 2. Scaffold the project structure (requirements + docs + prototype)
+> 3. Set up the Project Definition and requirements templates
 > 4. Configure Obsidian vault for project documentation
-> 5. Set up requirements templates
-> 6. Configure GitHub project board, labels, and milestone
-> 7. Push the initial commit to GitHub
+> 5. Configure GitHub project board, labels, and milestone
+> 6. Push the initial commit to GitHub
+>
+> You'll then run `/pp-discovery 1` to start the Discovery Sprint.
 >
 > Ready to go?"
 
@@ -152,7 +153,6 @@ cd [PROJECT_NAME]
 
 ```bash
 mkdir -p \
-  Discovery \
   prototype/src/components \
   prototype/src/pages \
   prototype/src/styles \
@@ -164,417 +164,15 @@ mkdir -p \
   .obsidian
 ```
 
-#### 4c. Scaffold Discovery Framework
-
-Generate all discovery, requirements, and project definition files. These are **interactive facilitation templates** — by working through all 13 sessions via guided Q&A, the team produces a comprehensive project definition, prioritized backlog, architecture decisions, and go/no-go assessment.
-
-**Generation order:** Guide first → tracking files → session files → Project Definition → requirements.
-
-##### 4c.1 Discovery Sessions Guide
-
-Generate `[PROJECT_NAME]-Discovery-Sessions-Guide.md` in the project root.
-
-This is the **complete Discovery Sprint methodology guide** containing all 13 session definitions. Generate the full guide with this structure:
-
-- **Title:** `# [PROJECT_NAME] Discovery Sprint Sessions Guide`
-- **Version:** 1.0, **Date:** current month and year
-- **Overview:** What is the Discovery Sprint, what it focuses on, expected outcome
-- **Session Schedule:** Overview table (all 13 sessions) + example 2-week schedule
-- **4 Parts with full session definitions:**
-
-| Part | Sessions | Category |
-|------|----------|----------|
-| Part 1: Introduction & Closure | 1, 13 | Kick-off and Wrap-up |
-| Part 2: Business Functional | 2, 3, 4 | As-Is, To-Be, UX |
-| Part 3: Technical | 5, 6, 7, 8, 9, 10 | Architecture, Security, Identity, Integration, QA, Infrastructure |
-| Part 4: Governance & Costs | 11, 12 | Roadmap, Team & Delivery |
-
-Each session section **must** include:
-1. **Goal** — what this session achieves
-2. **What We Cover** — numbered topic list with guiding questions (these drive the Q&A dialog)
-3. **Pre-requisites** — checklist of what's needed before starting
-4. **Outcomes / Deliverables** — checklist of what the session produces
-5. **Agenda Template** — time-boxed topic table
-6. **Notes Template** — structured tables for capturing session outputs (these are the key interactive elements — each table becomes a worksheet to fill in)
-
-End with:
-- **Deliverables Checklist** (Project Definition Document + Supporting Artifacts + Prioritized Product Backlog)
-- **How to Use This Guide** section
-
-**Reference the complete session definitions from the Pareto Discovery Sprint methodology (see 21Assets Discovery Sessions Guide for the canonical structure).**
-
-##### 4c.2 Cross-Session Context File
-
-Generate `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
-<!-- FR, NFR, BR counts -->
-
----
-
-## Session 4: UX Design Outputs
-_Populated after Session 4 completion_
-
-### Design Principles
-<!-- Numbered design principles -->
-
-### UX Standards
-<!-- Platform, navigation, language, accessibility -->
-
-### Key Personas (Refined)
-<!-- Persona categories and interaction patterns -->
-
-### Key Screen Decisions
-<!-- Screen layout decisions -->
-
----
-
-## 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 -->
-
----
-
-## 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_
+Discovery Sprint artifacts are not scaffolded here — `/pp-discovery` creates `.planning/discovery/` itself on first run (session files, `_progress.md`, `_context.md`).
 
-### 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 -->
-```
-
-##### 4c.3 Progress Tracker
-
-Generate `Discovery/_progress.md`:
-
-```markdown
-# Discovery Sprint Progress — [PROJECT_NAME]
-
-**Project:** [PROJECT_NAME]
-**Client:** [CLIENT_NAME]
-**Created:** [today's date]
-**Last Updated:** [today's date]
-**Overall Status:** Not Started
-
----
-
-## Session Progress
-
-| # | Session | Category | Status | Started | Completed | Score | Notes |
-|---|---------|----------|--------|---------|-----------|-------|-------|
-| 1 | Discovery Sprint Kick-off | Introduction & Closure | Not Started | | | | |
-| 2 | Business Process Mapping (As-Is) | Business Functional | Not Started | | | | |
-| 3 | Business Requirements (To-Be) | Business Functional | Not Started | | | | |
-| 4 | UX Design Principles | Business Functional | Not Started | | | | |
-| 5 | Application & Integration Architecture | Technical | Not Started | | | | |
-| 6 | Security & Compliance | Technical | Not Started | | | | |
-| 7 | User & Identity Management | Technical | Not Started | | | | |
-| 8 | Integration & Interface Design | Technical | Not Started | | | | |
-| 9 | QA & Testing Strategy | Technical | Not Started | | | | |
-| 10 | Infrastructure & Deployment | Technical | Not Started | | | | |
-| 11 | Roadmap & Release Planning | Governance & Costs | Not Started | | | | |
-| 12 | Team & Delivery Model | Governance & Costs | Not Started | | | | |
-| 13 | Discovery Sprint Wrap-up | Introduction & Closure | Not Started | | | | |
-
----
-
-## Summary
-
-- **Completed:** 0/13
-- **In Progress:** 0/13
-- **Not Started:** 13/13
-
----
-
-## Open Action Items
-
-| Action | From Session | Owner | Due Date | Status |
-|--------|-------------|-------|----------|--------|
-| | | | | |
-```
-
-##### 4c.4 Session Files (13 files)
-
-Generate one file per session in the `Discovery/` folder. Use this **session registry** for metadata:
-
-| # | Filename | Session Name | Category | Duration | Dependencies |
-|---|----------|-------------|----------|----------|-------------|
-| 1 | `01-discovery-sprint-kickoff.md` | Discovery Sprint Kick-off | Introduction & Closure | 2 hours | — |
-| 2 | `02-business-process-mapping-as-is.md` | Business Process Mapping (As-Is) | Business Functional | 2-3 hours | 1 |
-| 3 | `03-business-requirements-to-be.md` | Business Requirements & Future State (To-Be) | Business Functional | 2-3 hours | 1, 2 |
-| 4 | `04-ux-design-principles.md` | UX Design & User Experience Principles | Business Functional | 2-3 hours | 2, 3 |
-| 5 | `05-application-integration-architecture.md` | Application & Integration Architecture | Technical | 1.5-2 hours | 1, 2, 3, 4 |
-| 6 | `06-security-compliance-setup.md` | Security & Compliance Setup | Technical | 1.5-2 hours | 5 |
-| 7 | `07-user-identity-management.md` | User & Identity Management | Technical | 1.5-2 hours | 5, 6 |
-| 8 | `08-integration-interface-design.md` | Integration & Interface Design | Technical | 1.5-2 hours | 5 |
-| 9 | `09-quality-assurance-testing.md` | Quality Assurance & Testing Strategy | Technical | 1.5-2 hours | 3, 5 |
-| 10 | `10-infrastructure-deployment-readiness.md` | Infrastructure & Deployment Readiness | Technical | 1.5-2 hours | 5 |
-| 11 | `11-project-roadmap-release-planning.md` | Project Roadmap & Release Planning | Governance & Costs | 1-2 hours | 3, 5, 9 |
-| 12 | `12-team-delivery-model.md` | Team & Delivery Model Definition | Governance & Costs | 1-2 hours | 11 |
-| 13 | `13-discovery-sprint-wrapup.md` | Discovery Sprint Wrap-up & Next Steps | Introduction & Closure | 2 hours | 1-12 |
-
-**Each session file must contain:**
-
-1. **YAML frontmatter:**
-```yaml
----
-session_number: [N]
-session_name: "[Session Name]"
-category: "[Category]"
-duration: "[Duration]"
-dependencies: [list]
-status: "Not Started"
-project_name: "[PROJECT_NAME]"
-started_date: ""
-completed_date: ""
-completeness_score: 0
----
-```
-
-2. **Title:** `# Session [N] — [Session Name] — [PROJECT_NAME]`
-
-3. **Goal section:** The session's purpose — what it achieves and why it matters. This should describe the business value of completing this session.
-
-4. **What We Cover section:** Numbered topic list with **guiding questions** under each topic. These are the facilitation prompts that drive the Q&A dialog. For example, Session 1 covers: Project Context (What is happening? What problems?), Business Vision (Desired future state, KPIs), Stakeholders (Who decides? Who provides input?), Discovery Sprint Approach.
-
-5. **Pre-requisites:** Checklist of what must be ready before the session starts.
-
-6. **Outcomes / Deliverables:** Checklist of concrete outputs this session produces.
-
-7. **Notes Template:** The **structured tables** matching the Notes Template from the Discovery Sessions Guide for this specific session. These tables are the key interactive element — they get populated through the Q&A process. Include all relevant tables for the session (e.g., Session 2 has: Core Processes table, User Personas table, Pain Points table, Data Flow table, Current Systems table).
-
-8. **Key Decisions table:**
-```markdown
-| Decision | Rationale | Owner |
-|----------|-----------|-------|
-|          |           |       |
-```
-
-9. **Action Items table:**
-```markdown
-| Action | Owner | Deadline | Status |
-|--------|-------|----------|--------|
-|        |       |          |        |
-```
+#### 4c. Scaffold Project Definition & Requirements Templates
 
-10. **Footer:** Session date, Duration, Facilitator placeholders.
+Generate the requirements and project definition files. Discovery Sprint facilitation itself — the 13 guided sessions, the `_progress.md`/`_context.md` bootstrap files, and the Notes Template tables — is no longer scaffolded here. `/pp-discovery` is the sole, self-sufficient source for that: it bootstraps `.planning/discovery/_progress.md` and `.planning/discovery/_context.md` itself on first run (see `pp-core/workflows/discovery-sprint.md`'s Bootstrap Templates section). After STEP 4's scaffolding completes, the handoff (STEP 5) tells the team to run `/pp-discovery 1` to begin.
 
-**Reference the Discovery Sessions Guide for the exact content of each session's Goal, What We Cover, and Notes Template sections.**
+**Generation order:** Project Definition → requirements.
 
-##### 4c.5 Project Definition Template
+##### 4c.1 Project Definition Template
 
 Generate `[PROJECT_NAME]-Project-Definition.md`:
 
@@ -776,10 +374,10 @@ See [requirements/functional-requirements.md](requirements/functional-requiremen
 
 ## 12. Appendices
 
-- [Discovery Sessions Guide]([PROJECT_NAME]-Discovery-Sessions-Guide.md)
 - [Functional Requirements](requirements/functional-requirements.md)
 - [User Story Definition Guide](requirements/user-story-definition.md)
 - [Test Cases](requirements/test-cases.md)
+- Discovery Sprint sessions: `.planning/discovery/session-01.md` … `session-13.md` (run `/pp-discovery 1` to begin)
 
 ---
 
@@ -787,7 +385,7 @@ See [requirements/functional-requirements.md](requirements/functional-requiremen
 **Generated by:** pareto-project-setup skill
 ```
 
-##### 4c.6 Requirements Files
+##### 4c.2 Requirements Files
 
 Generate `requirements/functional-requirements.md`:
 
@@ -888,7 +486,7 @@ _Test cases are added here as user stories are defined during the Discovery Spri
 | | | | | | |
 ```
 
-##### 4c.7 Prototype README
+##### 4c.3 Prototype README
 
 Generate `prototype/README.md`:
 
@@ -940,7 +538,7 @@ Open `index.html` in any browser. No build tools or dependencies required.
 5. **Branded** — uses the customer's brand tokens (colors, typography, logo)
 ```
 
-##### 4c.8 Input Documents
+##### 4c.4 Input Documents
 
 Create `Inputs/docs/.gitkeep` (empty file — placeholder for input documents, architecture notes, and reference materials gathered during discovery).
 
@@ -1117,30 +715,27 @@ Create the following files in the project root:
 
 ## Discovery Sprint
 
-This project includes a complete Discovery Sprint framework. Open this folder in **Obsidian** to start.
+Run `/pp-discovery 1` to begin. `/pp-discovery` facilitates all 13 Discovery Sprint sessions, topic by topic, and writes progress and outputs to `.planning/discovery/` as you go — no separate methodology guide or Obsidian vault navigation is required to run it (Obsidian is still useful for browsing the project's other documentation).
 
 **How it works:**
-1. Open the project folder as an Obsidian vault
-2. Navigate to `Discovery/` and begin with Session 1 (Kick-off)
-3. Work through all 13 sessions via guided Q&A
-4. Use `[PROJECT_NAME]-Discovery-Sessions-Guide.md` for facilitation guidance
-5. Track progress in `Discovery/_progress.md`
+1. Run `/pp-discovery 1` to start Session 1 (Kick-off)
+2. Work through all 13 sessions via guided Q&A — resume any time with `/pp-discovery <N>`, or run `/pp-discovery` with no argument to see progress
+3. Track progress at `.planning/discovery/_progress.md`
 
 **Outcome:** A validated project definition, prioritized backlog, architecture decisions, and go/no-go assessment.
 
 | Document | Purpose |
 |----------|---------|
-| [Discovery Sessions Guide]([PROJECT_NAME]-Discovery-Sessions-Guide.md) | Full methodology — 13 session definitions |
 | [Project Definition]([PROJECT_NAME]-Project-Definition.md) | Consolidated output document |
-| [Discovery/_progress.md](Discovery/_progress.md) | Session progress tracker |
-| [Discovery/_context.md](Discovery/_context.md) | Cross-session context accumulator |
+| `.planning/discovery/_progress.md` | Session progress tracker (created by `/pp-discovery`) |
+| `.planning/discovery/_context.md` | Cross-session context accumulator (created by `/pp-discovery`) |
 | [prototype/](prototype/) | Interactive HTML prototype (created after Session 4) |
 
 ## Project Structure
 ```
 [PROJECT_NAME]/
   .obsidian/              Obsidian vault configuration
-  Discovery/              Discovery Sprint — 13 session worksheets
+  .planning/discovery/    Discovery Sprint outputs (created by /pp-discovery)
   prototype/              Interactive HTML prototype (built during Discovery)
   requirements/           Functional requirements, user stories, test cases
   Inputs/docs/            Input documents and reference materials
@@ -1297,7 +892,6 @@ web UI (click "New view" → "Board").
 git add .
 git commit -m "chore: initial project scaffold
 
-- Discovery Sprint framework (13 session templates + methodology guide)
 - Prototype folder structure (populated after Discovery Session 4)
 - Obsidian vault configured
 - Requirements templates (functional requirements, user stories, test cases)
@@ -1323,12 +917,10 @@ After successful push, give the developer a clean summary:
 > **Repo**: https://github.com/[GITHUB_ORG]/[PROJECT_NAME]
 >
 > **Next steps — Discovery Sprint (start here):**
-> 1. Open the project folder in **Obsidian** as a vault
-> 2. README.md loads as the landing page
-> 3. Navigate to `Discovery/` and begin **Session 1 (Kick-off)**
-> 4. Use `[PROJECT_NAME]-Discovery-Sessions-Guide.md` for facilitation guidance
-> 5. Track progress in `Discovery/_progress.md`
-> 6. Complete all 13 sessions to produce a validated project definition
+> 1. Run `/pp-discovery 1` to begin **Session 1 (Kick-off)**
+> 2. Work through all 13 sessions via guided Q&A — resume any time with `/pp-discovery <N>`
+> 3. Track progress at `.planning/discovery/_progress.md` (created automatically)
+> 4. Complete all 13 sessions to produce a validated project definition
 >
 > **Project Board:**
 > Open at: https://github.com/users/[GITHUB_ORG]/projects/ (or https://github.com/orgs/[GITHUB_ORG]/projects/)