@pennyfarthing/core 9.0.0 → 9.1.2

package/pennyfarthing-dist/workflows/interactive-debug/steps/step-04-commit.md

@@ -0,0 +1,122 @@
+# Step 4: Commit Changes
+
+<step-meta>
+number: 4
+name: commit
+gate: false
+</step-meta>
+
+<purpose>
+Roll up all fixes into a single chore commit using the `/chore` skill.
+</purpose>
+
+<instructions>
+1. REVIEW all changes before committing
+2. Present summary of all changes (issues fixed, files changed)
+3. Show git status output to verify no unintended changes
+4. Ask user to confirm ready to commit
+5. USE `/chore` skill to execute the commit
+6. VERIFY no unintended changes are staged
+7. Confirm commit succeeded with hash and message
+8. Offer options to push, debug more, or exit
+</instructions>
+
+<output>
+Provide:
+- Summary: Issues fixed count, files changed count
+- Changes table: File path and what was changed
+- Git status before commit
+- Commit hash
+- Commit message used
+- Post-commit status
+- Next steps offered to user
+</output>
+
+## Purpose
+
+Roll up all fixes into a single chore commit using the `/chore` skill.
+
+## Mandatory Execution Rules
+
+- REVIEW all changes before committing
+- USE `/chore` skill for the commit
+- VERIFY no unintended changes are staged
+
+## Pre-Commit Review
+
+Present summary of all changes:
+
+```
+## Debug Session Summary
+
+**Issues Fixed:** [count]
+**Files Changed:** [count]
+
+### Changes
+
+| File | Change |
+|------|--------|
+| `path/to/file.css` | Fixed overflow on main panel |
+| `path/to/file.tsx` | Added missing click handler |
+...
+
+### Git Status
+[show git status output]
+```
+
+Ask user to confirm:
+
+> Ready to commit these changes as a chore fix?
+>
+> - **[C] Commit** - Bundle into chore commit
+> - **[R] Review** - Show me the diffs first
+> - **[S] Split** - These should be separate commits
+> - **[X] Cancel** - Don't commit yet
+
+## Commit Execution
+
+**Use the `/chore` skill to create the commit.**
+
+The chore skill will:
+1. Stage the relevant files
+2. Create a commit with appropriate message format
+3. Handle the Co-Authored-By trailer
+
+Suggested commit message format:
+
+```
+fix(ui): resolve visual bugs from debug session
+
+- Fixed [issue 1 brief description]
+- Fixed [issue 2 brief description]
+...
+
+Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
+```
+
+## Post-Commit
+
+After successful commit:
+
+```
+## Debug Session Complete
+
+**Commit:** [hash]
+**Message:** [commit message]
+**Files:** [count] files changed
+
+The fixes have been committed. You can:
+- Push to remote when ready
+- Continue with another debug session
+- Exit the workflow
+```
+
+## Collaboration Menu
+
+- **[P] Push** - Push to remote branch
+- **[D] Debug more** - Start another debug session (back to step 1)
+- **[X] Exit** - End workflow
+
+## Workflow Complete
+
+This concludes the interactive-debug workflow.

package/pennyfarthing-dist/workflows/interactive-debug/workflow.yaml

@@ -0,0 +1,51 @@
+# Interactive Debug Workflow - BikeLane Stepped Workflow
+#
+# Connect to a running frontend (web server or Electron app), use Playwright MCP
+# for browser automation, hunt bugs collaboratively with UX Designer, fix them,
+# and roll up into a chore commit.
+#
+# Supports two connection modes:
+#   - Web Mode: Standard web servers (React, Vue, Next.js, Express, etc.)
+#   - Electron Mode: Desktop apps via Chrome DevTools Protocol (CDP)
+#
+# Prerequisites:
+#   - Playwright MCP configured in Claude settings
+#   - For web: A running dev server or command to start one
+#   - For Electron: App started with --remote-debugging-port=9222
+#
+# Purpose: Interactive visual debugging session that produces committed fixes
+# Role: UX Designer leads visual inspection, Dev fixes issues
+# Output: Chore commit with all bug fixes rolled up
+
+workflow:
+  name: interactive-debug
+  description: |
+    Interactive debugging workflow that connects to your frontend via Playwright MCP.
+    Supports both web servers and Electron apps (via CDP). Collaboratively identifies
+    bugs with UX Designer, fixes them, and commits as a chore.
+  version: "1.0.0"
+  type: stepped
+
+  # Step configuration
+  steps:
+    path: ./steps/
+    pattern: step-*.md
+
+  # Variables available in step files
+  variables:
+    project_root: .
+    dev_command: npm run dev
+    dev_port: 3000
+    dev_url: http://localhost:3000
+    # Electron/CDP configuration (for Electron apps)
+    cdp_port: 9222
+    cdp_url: http://localhost:9222
+    app_name: app  # Used in `just {app_name} cdp` suggestion
+
+  # Agent assignment - UX Designer leads visual debugging
+  agent: ux-designer
+
+  # Triggers - when to suggest this workflow
+  triggers:
+    types: [interactive-debug, debug-ui, visual-debug, bug-hunt]
+    tags: [debug, visual, playwright, ux, bug-fix]

package/pennyfarthing-dist/workflows/patch.yaml

@@ -18,9 +18,8 @@ workflow:
   description: Interrupt-driven bug fix during active story work
   version: "1.0.0"
 
-  # Patch mode is NOT a full workflow - it's an interrupt
-  # It doesn't have phases in the traditional sense
-  type: interrupt
+  # Patch mode is a simple single-phase workflow for interrupts
+  type: phased
 
   phases:
     - name: fix

package/pennyfarthing-dist/workflows/prd/steps-c/step-01-init.md

@@ -13,6 +13,12 @@ prdTemplate: '../templates/prd-template.md'
 
 # Step 1: Workflow Initialization
 
+<purpose>Initialize the PRD workflow by detecting continuation state, discovering input documents, and setting up the document structure for collaborative product requirement discovery.</purpose>
+
+<instructions>Check for existing workflow state; if continuing, hand off to step-01b. Otherwise, discover input documents, create initial document from template, track loaded files in frontmatter, and present initialization report with confirmation menu.</instructions>
+
+<output>Initialized PRD document with proper frontmatter structure (inputDocuments array, documentCounts, stepsCompleted), discovered input documents loaded and tracked, user confirmation to proceed to next step.</output>
+
 **Progress: Step 1 of 11** - Next: Project Discovery
 
 ## STEP GOAL:

package/pennyfarthing-dist/workflows/prd/steps-c/step-01b-continue.md

@@ -8,6 +8,12 @@ outputFile: '{planning_artifacts}/prd.md'
 
 # Step 1B: Workflow Continuation
 
+<purpose>Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration and accurate next-step determination.</purpose>
+
+<instructions>Analyze current workflow state from frontmatter; restore all previously loaded context documents; determine the correct next step from the last completed step's frontmatter; present progress summary with continuation option.</instructions>
+
+<output>Fully restored context with all previous input documents reloaded, accurate determination of next workflow step, user confirmation to proceed to the next step in the workflow.</output>
+
 ## STEP GOAL:
 
 Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration.

package/pennyfarthing-dist/workflows/prd/steps-c/step-02-discovery.md

@@ -17,6 +17,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 2: Project Discovery
 
+<purpose>Discover and classify the project through collaborative dialogue to understand product type, domain, complexity, and project context (greenfield vs brownfield).</purpose>
+
+<instructions>Check document state and loaded input documents; load classification data from CSV files; conduct discovery conversation to identify project type, domain, and complexity signals; confirm classification with user; optionally execute advanced elicitation or party mode workflows; save classification to frontmatter.</instructions>
+
+<output>Confirmed project classification with projectType, domain, complexity level, and projectContext saved to document frontmatter; stepsCompleted updated with this step; ready to proceed to product vision step.</output>
+
 **Progress: Step 2 of 13** - Next: Product Vision
 
 ## STEP GOAL:

package/pennyfarthing-dist/workflows/prd/steps-c/step-03-success.md

@@ -13,6 +13,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 3: Success Criteria Definition
 
+<purpose>Define comprehensive success criteria covering user, business, and technical success dimensions for the product.</purpose>
+
+<instructions>Collaborate with user to identify specific, measurable success criteria; cover user satisfaction, business metrics, and technical quality; capture acceptance thresholds for each criterion; optionally use advanced elicitation or party mode for deeper insight; save criteria to document.</instructions>
+
+<output>Comprehensive success criteria document with user success metrics, business success metrics, and technical success metrics, each with specific acceptance thresholds and measurability criteria.</output>
+
 **Progress: Step 3 of 11** - Next: User Journey Mapping
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-04-journeys.md

@@ -13,6 +13,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 4: User Journey Mapping
 
+<purpose>Map all user types that interact with the system with narrative story-based journeys that capture interactions, touchpoints, and emotional states.</purpose>
+
+<instructions>Identify all user personas and archetypes; for each user type, collaboratively craft narrative journey stories; capture decision points, pain points, and desired outcomes; ensure journey completeness from initial interaction through goal completion; save journeys to document.</instructions>
+
+<output>Comprehensive user journey narratives for all identified user types, each with clear story flow, decision points, pain points, and desired outcomes documented in the PRD.</output>
+
 **Progress: Step 4 of 11** - Next: Domain Requirements
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-05-domain.md

@@ -14,6 +14,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 5: Domain-Specific Requirements (Optional)
 
+<purpose>Explore domain-specific constraints, compliance requirements, and technical considerations for complex domains that shape product requirements.</purpose>
+
+<instructions>Check if domain is marked as high-complexity; if simple domain, skip this step; for complex domains, explore regulatory constraints, industry standards, and technical domain considerations through collaborative dialogue; document domain-specific requirements.</instructions>
+
+<output>Domain-specific requirements documentation including applicable regulatory constraints, industry standards, technical domain considerations, and compliance requirements relevant to the project domain.</output>
+
 **Progress: Step 5 of 13** - Next: Innovation Focus
 
 ## STEP GOAL:

package/pennyfarthing-dist/workflows/prd/steps-c/step-06-innovation.md

@@ -16,6 +16,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 6: Innovation Discovery
 
+<purpose>Detect and explore innovative aspects of the product including novel technology, unique approaches, or differentiated features.</purpose>
+
+<instructions>Analyze product classification for innovation signals; conduct collaborative dialogue to identify innovative elements; explore novel aspects, technical differentiation, and competitive advantages; document innovation aspects in the PRD.</instructions>
+
+<output>Innovation documentation capturing novel elements, unique technical approaches, competitive differentiation, and innovative features of the product.</output>
+
 **Progress: Step 6 of 11** - Next: Project Type Analysis
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-07-project-type.md

@@ -16,6 +16,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 7: Project-Type Deep Dive
 
+<purpose>Conduct project-type specific discovery using CSV-driven guidance to explore key considerations unique to the product type.</purpose>
+
+<instructions>Load project-type guidance from CSV file matching the detected project type; use guidance framework to conduct type-specific discovery dialogue; explore type-specific features, architecture patterns, and considerations; document project-type insights.</instructions>
+
+<output>Project-type specific discovery documentation capturing type-specific features, architectural considerations, and key discovery insights for the product type.</output>
+
 **Progress: Step 7 of 11** - Next: Scoping
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-08-scoping.md

@@ -13,6 +13,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 8: Scoping Exercise - MVP & Future Features
 
+<purpose>Define MVP boundaries and prioritize features across development phases to create a strategic delivery roadmap.</purpose>
+
+<instructions>Collaborate with user to identify core MVP features and future feature sets; establish clear phase-based feature prioritization; capture dependencies and sequencing logic; document MVP scope and phased roadmap.</instructions>
+
+<output>Documented MVP scope with prioritized core features, phased feature roadmap across development iterations, and feature dependency analysis.</output>
+
 **Progress: Step 8 of 11** - Next: Functional Requirements
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-09-functional.md

@@ -13,6 +13,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 9: Functional Requirements Synthesis
 
+<purpose>Synthesize all discovery insights into comprehensive functional requirements that define feature specifications and user-facing capabilities.</purpose>
+
+<instructions>Review all previous discovery documentation; synthesize insights into clear functional requirements; structure requirements with feature descriptions, acceptance criteria, and user story format; optionally use advanced elicitation; document comprehensive functional specification.</instructions>
+
+<output>Comprehensive functional requirements document with feature specifications, acceptance criteria, user story mappings, and traceability to success criteria and user journeys.</output>
+
 **Progress: Step 9 of 11** - Next: Non-Functional Requirements
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-10-nonfunctional.md

@@ -13,6 +13,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 10: Non-Functional Requirements
 
+<purpose>Define quality attributes including performance, security, scalability, reliability, and other non-functional requirements that matter for this product.</purpose>
+
+<instructions>Collaborate with user to identify critical quality attributes; establish measurable targets for performance, security, scalability, reliability, and accessibility; determine quality thresholds and trade-off priorities; document comprehensive non-functional specification.</instructions>
+
+<output>Comprehensive non-functional requirements documentation including performance targets, security requirements, scalability requirements, reliability targets, and quality attribute priorities.</output>
+
 **Progress: Step 10 of 12** - Next: Polish Document
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-11-polish.md

@@ -14,6 +14,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step 11: Document Polish
 
+<purpose>Optimize and polish the complete PRD document for flow, coherence, and readability while preserving all content and requirements.</purpose>
+
+<instructions>Load the entire PRD document; review structure and organization; improve cross-section flow and coherence; enhance readability and clarity; verify all requirements are traceable; polish without removing or modifying core content; optionally gather feedback.</instructions>
+
+<output>Polished PRD document with improved structure, enhanced flow and coherence, clearer writing, and verified completeness of all sections and requirements.</output>
+
 **Progress: Step 11 of 12** - Next: Complete PRD
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-c/step-12-complete.md

@@ -9,6 +9,12 @@ validationFlow: '../steps-v/step-v-01-discovery.md'
 
 # Step 12: Workflow Completion
 
+<purpose>Complete the PRD workflow, finalize document status, update completion metadata, and suggest next steps including validation and publication options.</purpose>
+
+<instructions>Verify all sections of PRD are complete; update frontmatter with workflow completion status; finalize stepsCompleted array; generate completion summary; present options for validation workflow, stakeholder review, or publication; confirm user satisfaction with completed PRD.</instructions>
+
+<output>Finalized PRD document with complete workflow metadata, completion confirmation, summary of deliverables, and options for next workflow steps.</output>
+
 **Final Step - Complete the PRD**
 
 ## MANDATORY EXECUTION RULES (READ FIRST):

package/pennyfarthing-dist/workflows/prd/steps-e/step-e-01-discovery.md

@@ -11,6 +11,12 @@ partyModeWorkflow: '{project_root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Step E-1: Discovery & Understanding
 
+<purpose>Understand what the user wants to edit in the PRD, detect PRD format/type, check for validation report guidance, and route to appropriate editing workflow.</purpose>
+
+<instructions>Discover which PRD document user wants to edit; detect format and structure; identify specific sections or requirements to edit; check if validation report exists; route to format-specific editing (current format edit or legacy conversion); understand edit scope and objectives.</instructions>
+
+<output>Clear understanding of edit objectives, detected PRD format, identified sections to edit, and routing to appropriate editing workflow step.</output>
+
 ## STEP GOAL:
 
 Understand what the user wants to edit in the PRD, detect PRD format/type, check for validation report guidance, and route appropriately.

package/pennyfarthing-dist/workflows/prd/steps-e/step-e-01b-legacy-conversion.md

@@ -10,6 +10,12 @@ prdPurpose: '{project_root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/
 
 # Step E-1B: Legacy PRD Conversion Assessment
 
+<purpose>Analyze legacy PRD against BMAD standards, identify gaps and improvement opportunities, propose conversion strategy, and let user choose conversion approach.</purpose>
+
+<instructions>Load and analyze legacy PRD structure; compare against BMAD standard sections and formatting; identify missing sections, gaps, and improvement opportunities; propose conversion strategy options; present user with conversion choices (full conversion, incremental editing, hybrid approach).</instructions>
+
+<output>Comprehensive legacy PRD analysis with gap assessment, conversion strategy proposal, and user-selected approach for proceeding with edits.</output>
+
 ## STEP GOAL:
 
 Analyze legacy PRD against BMAD standards, identify gaps, propose conversion strategy, and let user choose how to proceed.

package/pennyfarthing-dist/workflows/prd/steps-e/step-e-02-review.md

@@ -12,6 +12,12 @@ advancedElicitationTask: '{project_root}/_bmad/core/workflows/advanced-elicitati
 
 # Step E-2: Deep Review & Analysis
 
+<purpose>Thoroughly review the existing PRD, analyze validation report findings (if provided), and prepare a detailed change plan before editing.</purpose>
+
+<instructions>Load and deeply analyze the PRD structure and content; if validation report exists, extract key findings and recommendations; identify sections requiring changes; conduct dialogue to understand user's edit priorities; prepare structured change plan with prioritized edits.</instructions>
+
+<output>Detailed analysis of PRD strengths and gaps, prioritized change plan with specific sections and edit recommendations, validation findings summary (if applicable), and structured roadmap for editing steps.</output>
+
 ## STEP GOAL:
 
 Thoroughly review the existing PRD, analyze validation report findings (if provided), and prepare a detailed change plan before editing.

package/pennyfarthing-dist/workflows/prd/steps-e/step-e-03-edit.md

@@ -10,6 +10,12 @@ prdPurpose: '{project_root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/
 
 # Step E-3: Edit & Update
 
+<purpose>Apply changes to the PRD following the approved change plan, including content updates, structure improvements, and format conversion if needed.</purpose>
+
+<instructions>Load PRD document and approved change plan; execute each prioritized edit with user input and approval; apply content updates, structural improvements, and format conversions; verify changes maintain PRD consistency; save updated PRD; prepare for next step.</instructions>
+
+<output>Updated PRD document with all approved changes applied, improved structure and content, consistent formatting, and ready for completion or further review.</output>
+
 ## STEP GOAL:
 
 Apply changes to the PRD following the approved change plan from step e-02, including content updates, structure improvements, and format conversion if needed.

package/pennyfarthing-dist/workflows/prd/steps-e/step-e-04-complete.md

@@ -9,6 +9,12 @@ validationWorkflow: './steps-v/step-v-01-discovery.md'
 
 # Step E-4: Complete & Validate
 
+<purpose>Present summary of completed edits and offer next steps including seamless integration with validation workflow or publication options.</purpose>
+
+<instructions>Verify all approved edits have been applied; prepare comprehensive summary of changes made; present completion confirmation with user; offer options including full validation workflow, stakeholder review, or publication; route to next steps based on user choice.</instructions>
+
+<output>Complete summary of edits applied, confirmation of PRD status, options for next workflow steps (validation, review, or publication), and routing to selected next step.</output>
+
 ## STEP GOAL:
 
 Present summary of completed edits and offer next steps including seamless integration with validation workflow.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-01-discovery.md

@@ -11,6 +11,12 @@ prdPurpose: '../data/prd-purpose.md'
 
 # Step 1: Document Discovery & Confirmation
 
+<purpose>Handle fresh context validation by confirming PRD path, discovering and loading input documents from frontmatter, and initializing the validation report.</purpose>
+
+<instructions>Confirm PRD file path is valid; load complete PRD document and frontmatter; extract and reload input documents from inputDocuments array; create validation report with PRD metadata; confirm readiness to begin validation checks.</instructions>
+
+<output>Loaded PRD document with complete context, extracted and verified input documents, initialized validation report with PRD metadata, ready for format detection and validation checks.</output>
+
 ## STEP GOAL:
 
 Handle fresh context validation by confirming PRD path, discovering and loading input documents from frontmatter, and initializing the validation report.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-02-format-detection.md

@@ -11,6 +11,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 2: Format Detection & Structure Analysis
 
+<purpose>Detect if PRD follows BMAD format and route appropriately - classify as BMAD Standard, BMAD Variant, or Non-Standard format.</purpose>
+
+<instructions>Analyze PRD structure to detect format conformance; identify section presence and order; classify format type; for non-standard formats, offer optional parity check; update validation report with format classification; route to appropriate next validation step.</instructions>
+
+<output>PRD format classification (BMAD Standard/Variant/Non-Standard), structure analysis summary, validation report updated with format findings, ready for format-specific validation checks.</output>
+
 ## STEP GOAL:
 
 Detect if PRD follows BMAD format and route appropriately - classify as BMAD Standard / BMAD Variant / Non-Standard, with optional parity check for non-standard formats.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-02b-parity-check.md

@@ -10,6 +10,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 2B: Document Parity Check
 
+<purpose>Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity, presenting user with options for how to proceed.</purpose>
+
+<instructions>Load and deeply analyze non-standard PRD structure; identify missing sections and gaps relative to BMAD standard; map existing content to BMAD sections; prepare parity analysis with specific recommendations; present user with conversion options (full conversion, selective upgrade, continue as-is).</instructions>
+
+<output>Detailed parity analysis documenting gaps between current format and BMAD standard, conversion recommendations with effort estimates, and user-selected approach for proceeding with validation.</output>
+
 ## STEP GOAL:
 
 Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity, presenting user with options for how to proceed.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-03-density-validation.md

@@ -10,6 +10,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 3: Information Density Validation
 
+<purpose>Validate PRD meets BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.</purpose>
+
+<instructions>Analyze PRD content for information density violations; scan for anti-patterns including conversational filler, wordiness, redundancy, and verbose phrasing; calculate density metrics; document violations with location and severity; update validation report with findings; optionally suggest improvements.</instructions>
+
+<output>Density validation report with identified violations, severity classification, specific locations, density metrics, and optional improvement suggestions.</output>
+
 ## STEP GOAL:
 
 Validate PRD meets BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-04-brief-coverage-validation.md

@@ -11,6 +11,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 4: Product Brief Coverage Validation
 
+<purpose>Validate that PRD covers all content from Product Brief (if brief was used as input), mapping brief content to PRD sections and identifying gaps.</purpose>
+
+<instructions>Check if product brief exists in inputDocuments; if brief available, load it and analyze key content areas; map brief content to PRD sections; identify coverage gaps and unmapped content; calculate coverage percentage; update validation report with coverage findings.</instructions>
+
+<output>Coverage validation report with mapped brief content, identified coverage gaps, coverage percentage metric, and recommendations for addressing gaps.</output>
+
 ## STEP GOAL:
 
 Validate that PRD covers all content from Product Brief (if brief was used as input), mapping brief content to PRD sections and identifying gaps.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-05-measurability-validation.md

@@ -10,6 +10,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 5: Measurability Validation
 
+<purpose>Validate that all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) are measurable, testable, and follow proper format without implementation details.</purpose>
+
+<instructions>Extract all FRs and NFRs from PRD; analyze each requirement for measurability indicators (numeric targets, acceptance criteria, pass/fail conditions); check for implementation leakage; identify non-measurable requirements; classify severity of measurability issues; update validation report.</instructions>
+
+<output>Measurability validation report with analysis of each requirement, identification of non-measurable requirements, severity classification, implementation leakage findings, and recommendations for improvement.</output>
+
 ## STEP GOAL:
 
 Validate that all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) are measurable, testable, and follow proper format without implementation details.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-06-traceability-validation.md

@@ -10,6 +10,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 6: Traceability Validation
 
+<purpose>Validate the traceability chain from Executive Summary → Success Criteria → User Journeys → Functional Requirements is intact, ensuring every requirement traces back to a user need or business objective.</purpose>
+
+<instructions>Extract vision, success criteria, user journeys, and requirements from PRD; map traceability links from requirements back to journeys, success criteria, and vision; identify orphaned requirements without traceability; verify bidirectional traceability; calculate traceability completeness; update validation report.</instructions>
+
+<output>Traceability validation report with traceability chain visualization, identified gaps and orphaned requirements, bidirectional traceability verification, traceability coverage metrics.</output>
+
 ## STEP GOAL:
 
 Validate the traceability chain from Executive Summary → Success Criteria → User Journeys → Functional Requirements is intact, ensuring every requirement traces back to a user need or business objective.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-07-implementation-leakage-validation.md

@@ -10,6 +10,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 7: Implementation Leakage Validation
 
+<purpose>Ensure Functional Requirements and Non-Functional Requirements don't include implementation details - they should specify WHAT, not HOW.</purpose>
+
+<instructions>Extract all FRs and NFRs from PRD; scan each requirement for implementation keywords and patterns (specific technologies, frameworks, methodologies, HOW details); identify leakage violations; classify by severity; calculate leakage percentage; update validation report with findings and recommendations.</instructions>
+
+<output>Implementation leakage validation report with identified violations, severity classification, specific examples of leakage, leakage metrics, and recommendations for abstraction improvements.</output>
+
 ## STEP GOAL:
 
 Ensure Functional Requirements and Non-Functional Requirements don't include implementation details - they should specify WHAT, not HOW.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-08-domain-compliance-validation.md

@@ -12,6 +12,12 @@ domainComplexityData: '../data/domain-complexity.csv'
 
 # Step 8: Domain Compliance Validation
 
+<purpose>Validate domain-specific requirements are present for high-complexity domains (Healthcare, Fintech, GovTech, etc.), ensuring regulatory and compliance requirements are properly documented.</purpose>
+
+<instructions>Determine project domain from PRD frontmatter; check domain complexity level from CSV data; for high-complexity domains, verify domain-specific requirements section exists and covers applicable regulations; analyze compliance coverage; identify compliance gaps; update validation report.</instructions>
+
+<output>Domain compliance validation report with complexity assessment, identified compliance requirements, coverage analysis, compliance gaps, and recommendations for domain-specific improvements.</output>
+
 ## STEP GOAL:
 
 Validate domain-specific requirements are present for high-complexity domains (Healthcare, Fintech, GovTech, etc.), ensuring regulatory and compliance requirements are properly documented.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-09-project-type-validation.md

@@ -12,6 +12,12 @@ projectTypesData: '../data/project-types.csv'
 
 # Step 9: Project-Type Compliance Validation
 
+<purpose>Validate project-type specific requirements are properly documented - different project types (api_backend, web_app, mobile_app, etc.) have different required and excluded sections.</purpose>
+
+<instructions>Determine project type from PRD frontmatter; load project-type requirements from CSV data; verify all required sections for project type are present; check for prohibited sections; analyze type-specific requirement coverage; identify gaps; update validation report.</instructions>
+
+<output>Project-type compliance validation report with required/optional section verification, identified gaps, type-specific coverage analysis, and recommendations for project-type conformance.</output>
+
 ## STEP GOAL:
 
 Validate project-type specific requirements are properly documented - different project types (api_backend, web_app, mobile_app, etc.) have different required and excluded sections.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-10-smart-validation.md

@@ -11,6 +11,12 @@ advancedElicitationTask: '{project_root}/_bmad/core/workflows/advanced-elicitati
 
 # Step 10: SMART Requirements Validation
 
+<purpose>Validate Functional Requirements meet SMART quality criteria (Specific, Measurable, Attainable, Relevant, Traceable), ensuring high-quality requirements that can be implemented and tested.</purpose>
+
+<instructions>Extract all functional requirements from PRD; evaluate each requirement against SMART criteria; assess specificity, measurability, attainability, relevance, and traceability; score each requirement on SMART completeness; identify low-scoring requirements; calculate overall quality metrics; update validation report.</instructions>
+
+<output>SMART validation report with individual requirement scores, identified low-quality requirements, SMART criteria assessment, quality metrics, and improvement recommendations for each criterion.</output>
+
 ## STEP GOAL:
 
 Validate Functional Requirements meet SMART quality criteria (Specific, Measurable, Attainable, Relevant, Traceable), ensuring high-quality requirements.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -11,6 +11,12 @@ advancedElicitationTask: '{project_root}/_bmad/core/workflows/advanced-elicitati
 
 # Step 11: Holistic Quality Assessment
 
+<purpose>Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), BMAD PRD principles compliance, and overall quality rating.</purpose>
+
+<instructions>Review PRD holistically for flow and coherence; assess readability and clarity for human audience; evaluate machine-readability and AI-assistant usefulness; evaluate alignment with BMAD principles; identify strengths and improvement opportunities; provide overall quality rating and recommendations; update validation report.</instructions>
+
+<output>Holistic quality assessment report with document flow analysis, audience effectiveness evaluation, BMAD principles alignment, identified strengths and weaknesses, overall quality rating, and strategic improvement recommendations.</output>
+
 ## STEP GOAL:
 
 Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), BMAD PRD principles compliance, and overall quality rating.

package/pennyfarthing-dist/workflows/prd/steps-v/step-v-12-completeness-validation.md

@@ -11,6 +11,12 @@ validationReportPath: '{validation_report_path}'
 
 # Step 12: Completeness Validation
 
+<purpose>Final comprehensive completeness check - validate no template variables remain, each section has required content, section-specific completeness requirements are met, and frontmatter is properly populated.</purpose>
+
+<instructions>Scan PRD for remaining template variables and placeholders; verify all required sections have substantial content; check section-specific completeness requirements; validate frontmatter contains all required metadata; calculate completeness percentage; identify missing elements; update validation report with completeness findings.</instructions>
+
+<output>Completeness validation report with template variable scan results, section-by-section completeness assessment, frontmatter validation, completeness percentage metric, and list of outstanding items.</output>
+
 ## STEP GOAL:
 
 Final comprehensive completeness check - validate no template variables remain, each section has required content, section-specific completeness, and frontmatter is properly populated.