@zigrivers/scaffold 2.38.1 → 2.44.2

package/pipeline/vision/innovate-vision.md

@@ -7,7 +7,7 @@ order: 030
 dependencies: [review-vision]
 outputs: [docs/vision.md]
 conditional: "if-needed"
-knowledge-base: [vision-craft]
+knowledge-base: [vision-craft, prd-innovation]
 ---
 
 ## Purpose
@@ -29,24 +29,27 @@ not here.
 - docs/vision.md — updated with approved strategic innovations
 
 ## Quality Criteria
-- Innovations are strategic-level, not feature-level
+- (mvp) Innovations are strategic-level, not feature-level
 - (mvp) Each innovation categorized: market opportunity, positioning, AI-native, ecosystem, or contrarian
 - (mvp) Each innovation includes: what to change, why, impact (high/medium/low), cost estimate
 - (mvp) Each suggestion has an implementation cost estimate (trivial/moderate/significant)
 - (mvp) Recommended disposition stated for each: must-have, backlog, or reject with rationale
 - (deep) Impact assessments compared to existing document content
 - (deep) Each approved innovation is integrated with the same subsection headings and detail level as existing vision sections
-- Vision scope is respected — no uncontrolled strategic drift
-- User approval is obtained before modifying the vision document
+- (mvp) Each innovation marked with approval status: approved, deferred, or rejected, with user decision timestamp
+- (mvp) Vision scope is respected — no uncontrolled strategic drift
+- (mvp) User approval is obtained before modifying the vision document
 
 ## Methodology Scaling
 - **deep**: Full innovation pass across all 5 dimensions. Competitive research
   via web search. Detailed integration of approved innovations into vision.
 - **mvp**: Not applicable — this step is conditional and skipped in MVP.
-- **custom:depth(1-5)**: Depth 1-2: Quick scan only — identify 1-2 high-impact
-  strategic angles with brief rationale. Depth 3: quick scan for positioning
-  gaps and obvious market opportunities. Depth 4-5: full innovation pass
-  across all 5 dimensions.
+- **custom:depth(1-5)**:
+  - Depth 1: Skip (not enough context for meaningful innovation at this depth).
+  - Depth 2: Quick scan only — identify 1-2 high-impact strategic angles with brief rationale.
+  - Depth 3: Quick scan for positioning gaps and obvious market opportunities across dimensions 1-2.
+  - Depth 4: Full innovation pass across all 5 dimensions with competitive research.
+  - Depth 5: Full innovation pass across all 5 dimensions with competitive research and contrarian stress-test.
 
 ## Conditional Evaluation
 Enable when: project has competitive landscape content in vision.md, user

package/pipeline/vision/review-vision.md

@@ -26,21 +26,24 @@ strategically sound, and ready for the PRD to consume.
 
 ## Quality Criteria
 - (mvp) Passes 1 and 5 executed with findings documented
-- All 5 review passes executed with findings documented
-- Every finding categorized by severity (P0-P3)
-- Fix plan created for P0 and P1 findings
-- Fixes applied and re-validated
+- (deep) All 5 review passes executed with findings documented
+- (mvp) Every finding categorized by severity: P0 = Breaks downstream work. P1 = Prevents quality milestone. P2 = Known tech debt. P3 = Polish.
+- (mvp) Fix plan created for P0 and P1 findings
+- (mvp) Fixes applied and re-validated
 - (mvp) Every vision section has content specific enough to derive a PRD without asking strategic clarification questions
-- (depth 4+) Multi-model review findings synthesized with consensus/disagreement analysis
+- (depth 4+) Multi-model review findings synthesized: Consensus (all models agree), Majority (2+ models agree), or Divergent (models disagree — present to user for decision)
 
 ## Methodology Scaling
 - **deep**: All 5 review passes. Full findings report with severity
   categorization. Fixes applied and re-validated.
 - **mvp**: Passes 1 and 5 only (Vision Clarity and Downstream Readiness).
   Focus on blocking gaps — is the vision clear enough to write a PRD from?
-- **custom:depth(1-5)**: Depth 1-2: passes 1 and 5 only. Depth 3: passes 1,
-  2, 5 (add Audience Precision). Depth 4: passes 1-3, 5 (add Competitive
-  Rigor). Depth 5: all 5 passes.
+- **custom:depth(1-5)**:
+  - Depth 1: Pass 1 only (Vision Clarity). Single review pass.
+  - Depth 2: Passes 1 and 5 (Vision Clarity, Downstream Readiness). Two review passes.
+  - Depth 3: Passes 1, 2, 5 (add Audience Precision). Three review passes.
+  - Depth 4: Passes 1-3, 5 (add Competitive Rigor) + one external model review (if CLI available). Four review passes.
+  - Depth 5: All 5 passes + multi-model review with reconciliation. Five review passes.
 
 ## Mode Detection
 If docs/reviews/vision-review-vision.md exists, this is a re-review. Read
@@ -115,10 +118,10 @@ Evaluate whether the PRD can be written from this vision:
 ### Review Process
 
 1. Execute each pass, documenting findings with severity (P0-P3):
-   - P0: Vision is fundamentally unclear or contradictory — blocks all downstream work
-   - P1: Significant gap that would cause PRD to make wrong assumptions
-   - P2: Minor gap or vagueness that could be improved
-   - P3: Nitpick or style suggestion
+   - P0: Breaks downstream work — vision is fundamentally unclear or contradictory
+   - P1: Prevents quality milestone — significant gap that would cause PRD to make wrong assumptions
+   - P2: Known tech debt — minor gap or vagueness that could be improved
+   - P3: Polish — nitpick or style suggestion
 2. Create a fix plan for all P0 and P1 findings
 3. Present the fix plan to the user for approval
 4. Apply approved fixes to docs/vision.md

package/skills/multi-model-dispatch/SKILL.md

@@ -141,12 +141,13 @@ When dispatching a review, bundle all relevant context into the prompt. Each CLI
 ### Template for Artifact Review
 
 ```
-You are reviewing a project artifact for quality issues. Focus on P0 (critical) and P1 (high) issues only.
+You are reviewing a project artifact for quality issues. Report P0 (critical), P1 (high), and P2 (medium) issues.
 
 ## Severity Definitions
 - P0: Will cause implementation failure, data loss, security vulnerability, or fundamental architectural flaw
 - P1: Will cause bugs in normal usage, inconsistency across documents, or blocks downstream work
-- Do NOT report P2/P3 issues (suggestions, style, minor improvements)
+- P2: Improvement opportunity — style, naming, documentation, minor optimization
+- Do NOT report P3 issues (personal preference, trivial nits)
 
 ## Review Standards
 [paste contents of docs/review-standards.md if it exists, otherwise use severity definitions above]
@@ -163,7 +164,7 @@ Respond with a JSON object:
   "approved": true/false,
   "findings": [
     {
-      "severity": "P0" or "P1",
+      "severity": "P0" or "P1" or "P2",
       "location": "section or line reference",
       "description": "what's wrong",
       "suggestion": "specific fix"
@@ -172,13 +173,13 @@ Respond with a JSON object:
   "summary": "one-line assessment"
 }
 
-If no P0/P1 issues found, respond with: { "approved": true, "findings": [], "summary": "No P0/P1 issues found." }
+If no P0/P1/P2 issues found, respond with: { "approved": true, "findings": [], "summary": "No issues found." }
 ```
 
 ### Template for PR Diff Review
 
 ```
-You are reviewing a pull request diff. Focus on P0 and P1 issues only.
+You are reviewing a pull request diff. Report P0, P1, and P2 issues.
 
 ## Review Standards
 [paste docs/review-standards.md]

package/skills/scaffold-runner/SKILL.md

@@ -148,7 +148,7 @@ If no prior activity is detected, suggest `single-agent-start` or `multi-agent-s
 
 ## Tool Execution
 
-Tools (version-bump, release, version, update, dashboard, prompt-pipeline, session-analyzer) are utility commands orthogonal to the pipeline.
+Tools (version-bump, release, version, update, dashboard, prompt-pipeline, session-analyzer, review-pr, post-implementation-review) are utility commands orthogonal to the pipeline.
 
 ### Differences from Pipeline Steps
 
@@ -167,7 +167,50 @@ Tools (version-bump, release, version, update, dashboard, prompt-pipeline, sessi
 ### Accessing Tools
 
 - `scaffold run <tool-name>` — run a specific tool
-- `scaffold list --tools` — show available tools (when implemented)
+- `scaffold list --section tools` — show available tools (compact)
+- `scaffold list --section tools --verbose` — show with argument hints
+- `scaffold list --section tools --format json` — machine-readable output
+
+## Tool Listing
+
+When the user asks "what tools are available?", "what can I build?", or "show me the tools":
+
+1. Run `scaffold list --section tools --format json`
+2. Parse the JSON: `data.tools.build` (build phase steps) and `data.tools.utility` (utility tools)
+3. Render as two grouped sections:
+
+**Build Phase (Phase 15)**
+> These are stateless pipeline steps — they appear in `scaffold next` once Phase 14 is complete and can be run repeatedly.
+
+| Command | When to Use |
+|---------|-------------|
+| `scaffold run single-agent-start` | Start the autonomous TDD implementation loop — Claude picks up tasks and builds |
+| `scaffold run single-agent-resume` | Resume where you left off after closing Claude Code |
+| `scaffold run multi-agent-start` | Start parallel implementation with multiple agents in worktrees |
+| `scaffold run multi-agent-resume` | Resume parallel agent work after a break |
+| `scaffold run quick-task` | Create a focused task for a bug fix, refactor, or small improvement |
+| `scaffold run new-enhancement` | Add a new feature to an already-scaffolded project |
+
+**Utility Tools**
+> These are orthogonal to the pipeline — usable at any time, not tied to pipeline state.
+
+| Command | When to Use |
+|---------|-------------|
+| `scaffold run version-bump` | Mark a milestone with a version number without the full release ceremony |
+| `scaffold run release` | Ship a new version — changelog, Git tag, and GitHub release. Supports `--dry-run`, `current`, and `rollback` |
+| `scaffold run version` | Show the current scaffold version |
+| `scaffold run update` | Update scaffold to the latest version |
+| `scaffold run dashboard` | Open a visual progress dashboard in your browser |
+| `scaffold run prompt-pipeline` | Print the full pipeline reference table |
+| `scaffold run review-pr` | Run all 3 code review channels (Codex CLI, Gemini CLI, Superpowers) on a PR |
+| `scaffold run post-implementation-review` | Full 3-channel codebase review after an AI agent completes all tasks |
+| `scaffold run session-analyzer` | Analyze Claude Code session logs for patterns and insights |
+
+**Display rules:**
+- The tool list comes from CLI output (always complete and up-to-date)
+- The "When to Use" column comes from the table above (stable prose)
+- If the CLI returns a tool not in the table above, display it using its `description` field from the CLI output — graceful degradation
+- For verbose detail (`--verbose`), call `scaffold list --section tools --verbose --format json` and add an Arguments column using the `argumentHint` values
 
 ## Session Preferences
 
@@ -217,8 +260,9 @@ Respond to these natural language requests:
 | "New feature" / "Add enhancement" | `scaffold run new-enhancement <description>` |
 | "Bump version" / "Version bump" | `scaffold run version-bump` |
 | "Create release" / "Release" | `scaffold run release` |
-| "What tools are available?" | `scaffold list --tools` |
+| "What tools are available?" | Run `scaffold list --section tools --format json`, render as two-section grouped display — see [Tool Listing](#tool-listing) |
 | "Show version" | `scaffold run version` |
+| "Review PR" / "Run code review" | `scaffold run review-pr` |
 
 ### Re-running Steps
 

package/tools/dashboard.md

@@ -0,0 +1,53 @@
+---
+name: dashboard
+description: Open visual pipeline dashboard in browser
+phase: null
+order: null
+dependencies: []
+outputs: []
+conditional: null
+stateless: true
+category: tool
+knowledge-base: []
+---
+
+## Purpose
+
+Open a visual pipeline dashboard in the browser showing progress, phase grouping,
+step details, and what's next.
+
+## Instructions
+
+Run the `scaffold dashboard` CLI command:
+
+```bash
+scaffold dashboard
+```
+
+### Flags
+
+- `--no-open` — Generate HTML but don't open in browser
+- `--json-only` — Output JSON data to stdout (for scripting)
+- `--output FILE` — Write HTML to a specific file path
+
+### What It Shows
+
+- **Progress bar** with color-coded segments (completed, skipped, pending)
+- **Summary cards** with counts for completed, skipped, pending, and total steps
+- **Phase-grouped steps** in collapsible sections, organized by the 16 pipeline phases
+- **Step detail modals** with descriptions, dependencies, outputs, and full prompt content
+- **"What's Next" banner** highlighting the recommended next step
+- **Decision log** showing recorded project decisions
+- **Dark/light theme** (automatic, follows system preference)
+
+### Modes
+
+- **With `.scaffold/` directory**: Shows actual progress — completed/skipped/pending status from state
+- **Without `.scaffold/` directory**: Shows full pipeline overview as a reference guide (all steps pending)
+
+## Process Rules
+
+1. This is a standalone command — use it anytime during the pipeline to check progress.
+2. No files in the project are modified (the dashboard HTML is written to a temp directory).
+
+**Pipeline reference:** `/scaffold:prompt-pipeline`