feat(M2): Documentation flow, accuracy, consistency cleanup, and cross-platform shell portability

pi-package/skills/create-plan/templates/continuation-runbook.md

@@ -65,15 +65,19 @@ Work from this folder (`ai_plan/YYYY-MM-DD-<short-title>/`) and always follow th
 ## Full Context Reproduction
 
 ### Project Overview
+
 [What this project/feature is about]
 
 ### User Requirements
+
 [All gathered requirements]
 
 ### Scope
+
 [In scope / out of scope]
 
 ### Dependencies
+
 [External dependencies, prerequisites, related systems]
 
 ---
@@ -81,16 +85,19 @@ Work from this folder (`ai_plan/YYYY-MM-DD-<short-title>/`) and always follow th
 ## Key Specifications
 
 ### Type Definitions
+
 ```typescript
 // Copy-paste ready type definitions
 ```
 
 ### Enums & Constants
+
 ```typescript
 // All enums/constants needed
 ```
 
 ### API Endpoints
+
 ```typescript
 // Request/response shapes
 ```
@@ -108,16 +115,19 @@ Work from this folder (`ai_plan/YYYY-MM-DD-<short-title>/`) and always follow th
 ## Verification Commands
 
 ### Lint (changed files first)
+
 ```bash
 # example: pnpm eslint <changed-file-1> <changed-file-2>
 ```
 
 ### Typecheck
+
 ```bash
 # example: pnpm tsc --noEmit
 ```
 
 ### Tests (target changed scope first)
+
 ```bash
 # example: pnpm test -- <related spec/file>
 ```

pi-package/skills/create-plan/templates/milestone-plan.md

@@ -1,6 +1,7 @@
 # [Plan Title]
 
 ## Overview
+
 - **Goal:** [One sentence describing the end state]
 - **Created:** YYYY-MM-DD
 - **Status:** In Progress | Complete
@@ -8,37 +9,46 @@
 ## Context
 
 ### Requirements
+
 [Gathered requirements from user questions]
 
 ### Constraints
+
 [Technical, business, or timeline constraints]
 
 ### Success Criteria
+
 [How we know this is complete]
 
 ## Architecture
 
 ### Design Decisions
+
 [Key architectural choices and rationale]
 
 ### Component Relationships
+
 [How pieces fit together]
 
 ### Data Flow
+
 [How data moves through the system]
 
 ## Milestones
 
 ### M1: [Name]
+
 **Description:** [What this milestone achieves]
 
 **Acceptance Criteria:**
+
 - [ ] [Criterion 1]
 - [ ] [Criterion 2]
 
 **Stories:** S-101, S-102, S-103...
 
 **Milestone Completion Rule (MANDATORY):**
+
 - Run lint/typecheck/tests for changed files.
 - Commit locally (DO NOT push).
 - Stop and ask user for feedback.
@@ -48,15 +58,18 @@
 ---
 
 ### M2: [Name]
+
 **Description:** [What this milestone achieves]
 
 **Acceptance Criteria:**
+
 - [ ] [Criterion 1]
 - [ ] [Criterion 2]
 
 **Stories:** S-201, S-202, S-203...
 
 **Milestone Completion Rule (MANDATORY):**
+
 - Run lint/typecheck/tests for changed files.
 - Commit locally (DO NOT push).
 - Stop and ask user for feedback.
@@ -68,16 +81,19 @@
 ## Technical Specifications
 
 ### Types & Interfaces
+
 ```typescript
 // Key type definitions
 ```
 
 ### API Contracts
+
 ```typescript
 // Endpoint signatures, request/response shapes
 ```
 
 ### Constants & Enums
+
 ```typescript
 // Shared constants
 ```
@@ -94,6 +110,7 @@
 ## Related Plan Files
 
 This file is part of the plan folder under `ai_plan/`:
+
 - `original-plan.md` - Original approved plan (reference for original intent)
 - `final-transcript.md` - Final planning transcript (reference for rationale/context)
 - `milestone-plan.md` - This file (full specification)

pi-package/skills/create-plan/templates/story-tracker.md

@@ -1,6 +1,7 @@
 # Story Tracker: [Plan Title]
 
 ## Progress Summary
+
 - **Current Milestone:** M1
 - **Stories Complete:** 0/N
 - **Milestones Approved:** 0/M
@@ -46,15 +47,18 @@
 ## Update Instructions (MANDATORY)
 
 Before starting any story:
+
 1. Mark story as `in-dev`
 2. Update "Last Updated"
 
 After completing any story:
+
 1. Mark story as `completed`
 2. Add local commit hash to Notes
 3. Update "Stories Complete" and "Last Updated"
 
 At milestone boundary:
+
 1. Run lint/typecheck/tests for changed files
 2. Commit (no push)
 3. Request feedback
@@ -63,4 +67,5 @@ At milestone boundary:
 6. Continue only after approval
 
 After all milestones approved:
+
 - Ask permission to push and then mark plan completed.