@pennyfarthing/core 9.2.0 → 9.3.0

package/pennyfarthing-dist/workflows/retrospective/workflow.yaml

@@ -1,50 +0,0 @@
-# BMAD Retrospective Workflow - Imported for BMAD Compatibility
-#
-# This is a reference workflow imported from BMAD for compatibility with
-# BMAD-based projects. It provides structured retrospective ceremonies with
-# epic review and next epic preparation.
-#
-# Key features:
-# - Single-agent execution (Scrum Master facilitation)
-# - Party mode protocol with named agent roles
-# - Two-part format: Epic Review + Next Epic Preparation
-# - Deep story analysis and lesson extraction
-# - Previous retrospective integration for continuity
-#
-# For Pennyfarthing projects, the /retro skill provides a simpler
-# retrospective experience without the full BMAD ceremony format.
-#
-# Source: BMAD-METHOD/src/modules/bmm/workflows/4-implementation/retrospective/
-# Migrated: 2026-01-22
-
-workflow:
-  name: retrospective
-  description: |
-    BMAD reference workflow: Run after epic completion to review overall success,
-    extract lessons learned, and explore if new information emerged that might
-    impact the next epic. This is imported for BMAD compatibility.
-  version: "1.0.0"
-  type: procedural
-  author: BMad
-
-  # Primary agent for this workflow
-  agent: sm
-
-  # Instructions and validation files
-  instructions: ./instructions.md
-  checklist: ./checklist.md
-
-  # Variables available in instruction files
-  variables:
-    project_root: .
-    config_source: "./_bmad/bmm/config.yaml"
-    planning_artifacts: ./artifacts/planning
-    implementation_artifacts: ./artifacts
-    sprint_status_file: ./artifacts/sprint-status.yaml
-    story_directory: ./artifacts/stories
-    retrospectives_folder: ./artifacts
-
-  # Triggers - when to suggest this workflow
-  triggers:
-    types: [bmad-retro, bmad-retrospective, epic-completion]
-    tags: [bmad, reference, procedural, retrospective]

package/pennyfarthing-dist/workflows/sprint-planning/checklist.md

@@ -1,33 +0,0 @@
-# Sprint Planning Validation Checklist
-
-## Core Validation
-
-### Complete Coverage Check
-
-- [ ] Every epic found in epic\*.md files appears in sprint-status.yaml
-- [ ] Every story found in epic\*.md files appears in sprint-status.yaml
-- [ ] Every epic has a corresponding retrospective entry
-- [ ] No items in sprint-status.yaml that don't exist in epic files
-
-### Parsing Verification
-
-Compare epic files against generated sprint-status.yaml:
-
-```
-Epic Files Contains:                Sprint Status Contains:
-✓ Epic 1                            ✓ epic-1: [status]
-  ✓ Story 1.1: User Auth              ✓ 1-1-user-auth: [status]
-  ✓ Story 1.2: Account Mgmt           ✓ 1-2-account-mgmt: [status]
-  ✓ Story 1.3: Plant Naming           ✓ 1-3-plant-naming: [status]
-                                      ✓ epic-1-retrospective: [status]
-✓ Epic 2                            ✓ epic-2: [status]
-  ✓ Story 2.1: Personality Model      ✓ 2-1-personality-model: [status]
-  ✓ Story 2.2: Chat Interface         ✓ 2-2-chat-interface: [status]
-                                      ✓ epic-2-retrospective: [status]
-```
-
-### Final Check
-
-- [ ] Total count of epics matches
-- [ ] Total count of stories matches
-- [ ] All items are in the expected order (epic, stories, retrospective)

package/pennyfarthing-dist/workflows/sprint-planning/sprint-status-template.yaml

@@ -1,55 +0,0 @@
-# Sprint Status Template
-# This is an EXAMPLE showing the expected format
-# The actual file will be generated with all epics/stories from your epic files
-
-# generated: {date}
-# project: {project_name}
-# project_key: {project_key}
-# tracking_system: {tracking_system}
-# story_location: {story_location}
-
-# STATUS DEFINITIONS:
-# ==================
-# Epic Status:
-#   - backlog: Epic not yet started
-#   - in-progress: Epic actively being worked on
-#   - done: All stories in epic completed
-#
-# Story Status:
-#   - backlog: Story only exists in epic file
-#   - ready-for-dev: Story file created, ready for development
-#   - in-progress: Developer actively working on implementation
-#   - review: Implementation complete, ready for review
-#   - done: Story completed
-#
-# Retrospective Status:
-#   - optional: Can be completed but not required
-#   - done: Retrospective has been completed
-#
-# WORKFLOW NOTES:
-# ===============
-# - Mark epic as 'in-progress' when starting work on its first story
-# - SM typically creates next story ONLY after previous one is 'done' to incorporate learnings
-# - Dev moves story to 'review', then Dev runs code-review (fresh context, ideally different LLM)
-
-# EXAMPLE STRUCTURE (your actual epics/stories will replace these):
-
-generated: 05-06-2-2025 21:30
-project: My Awesome Project
-project_key: jira-1234
-tracking_system: file-system
-story_location: "{story_location}"
-
-development_status:
-  epic-1: backlog
-  1-1-user-authentication: done
-  1-2-account-management: ready-for-dev
-  1-3-plant-data-model: backlog
-  1-4-add-plant-manual: backlog
-  epic-1-retrospective: optional
-
-  epic-2: backlog
-  2-1-personality-system: backlog
-  2-2-chat-interface: backlog
-  2-3-llm-integration: backlog
-  epic-2-retrospective: optional

package/pennyfarthing-dist/workflows/sprint-planning/steps/step-01-parse-epic-files.md

@@ -1,69 +0,0 @@
----
-name: 'step-01-parse-epic-files'
-description: 'Parse epic files and extract all work items for sprint status tracking'
-
-# Path Definitions
-workflow_path: '{project_root}/.pennyfarthing/workflows/sprint-planning'
-
-# File References
-thisStepFile: './step-01-parse-epic-files.md'
-nextStepFile: './step-02-build-sprint-status.md'
----
-
-<purpose>
-Parse epic files and extract all work items for sprint status tracking. Build complete inventory of all epics and stories from all epic files.
-</purpose>
-
-<instructions>
-1. Look for all files matching `{epics_pattern}` in `{epics_location}` (could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files)
-2. For each epic file found, extract epic numbers from headers like `## Epic 1:` or `## Epic 2:` and story IDs and titles from patterns like `### Story 1.1: User Authentication`
-3. Convert story format from `Epic.Story: Title` to kebab-case key using these conversion rules: Replace period with dash for the ID (1-1), convert title to kebab-case (user-authentication), and final key is `1-1-user-authentication`
-4. Use flexible document discovery: Search for whole document first (epics.md, bmm-epics.md, *epic*.md), check for sharded version (epics/index.md), read index.md to understand structure, read all epic section files (epic-1.md, epic-2.md, etc.), and process all epics and stories from combined content. If both exist, use the whole document.
-</instructions>
-
-<output>
-Complete inventory of all epics and stories from all epic files, with proper kebab-case keys and structured data ready for sprint status building.
-</output>
-
-# Step 1: Parse Epic Files and Extract All Work Items
-
-## Goal
-
-Parse epic files and extract all work items for sprint status tracking.
-
-## Actions
-
-1. Look for all files matching `{epics_pattern}` in `{epics_location}`
-   - Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files
-
-2. For each epic file found, extract:
-   - Epic numbers from headers like `## Epic 1:` or `## Epic 2:`
-   - Story IDs and titles from patterns like `### Story 1.1: User Authentication`
-   - Convert story format from `Epic.Story: Title` to kebab-case key: `epic-story-title`
-
-## Story ID Conversion Rules
-
-- Original: `### Story 1.1: User Authentication`
-- Replace period with dash: `1-1`
-- Convert title to kebab-case: `user-authentication`
-- Final key: `1-1-user-authentication`
-
-## Output
-
-Build complete inventory of all epics and stories from all epic files.
-
-## Document Discovery
-
-**Strategy**: Sprint planning needs ALL epics and stories to build complete status tracking.
-
-**Epic Discovery Process:**
-
-1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file
-2. **Check for sharded version** - If whole document not found, look for `epics/index.md`
-3. **If sharded version found**:
-   - Read `index.md` to understand the document structure
-   - Read ALL epic section files listed in the index (e.g., `epic-1.md`, `epic-2.md`, etc.)
-   - Process all epics and their stories from the combined content
-4. **Priority**: If both whole and sharded versions exist, use the whole document
-
-**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc.

package/pennyfarthing-dist/workflows/sprint-planning/steps/step-02-build-sprint-status.md

@@ -1,61 +0,0 @@
----
-name: 'step-02-build-sprint-status'
-description: 'Build sprint status structure from parsed epic and story data'
-
-# Path Definitions
-workflow_path: '{project_root}/.pennyfarthing/workflows/sprint-planning'
-
-# File References
-thisStepFile: './step-02-build-sprint-status.md'
-nextStepFile: './step-03-status-detection.md'
----
-
-<purpose>
-Build sprint status structure from parsed epic and story data. Create the foundational structure that tracks all epics, stories, and retrospectives with their default statuses.
-</purpose>
-
-<instructions>
-For each epic found from step 1, create entries in this exact order:
-1. Epic entry with key `epic-{num}` and default status `backlog`
-2. Story entries with key `{epic}-{story}-{title}` and default status `backlog`
-3. Retrospective entry with key `epic-{num}-retrospective` and default status `optional`
-
-Ensure all items are properly grouped by epic: Epic N entry, all stories for Epic N, retrospective for Epic N, Epic N+1 entry, etc. Follow the example structure provided in the Goal section.
-</instructions>
-
-<output>
-A structured development_status YAML structure organized by epic, with all stories and retrospectives properly grouped, ready for status detection in the next step.
-</output>
-
-# Step 2: Build Sprint Status Structure
-
-## Goal
-
-Build sprint status structure from parsed epic and story data.
-
-## Actions
-
-For each epic found, create entries in this order:
-
-1. **Epic entry** - Key: `epic-{num}`, Default status: `backlog`
-2. **Story entries** - Key: `{epic}-{story}-{title}`, Default status: `backlog`
-3. **Retrospective entry** - Key: `epic-{num}-retrospective`, Default status: `optional`
-
-## Example Structure
-
-```yaml
-development_status:
-  epic-1: backlog
-  1-1-user-authentication: backlog
-  1-2-account-management: backlog
-  epic-1-retrospective: optional
-```
-
-## Ordering
-
-Ensure items are grouped by epic:
-- Epic N entry
-- All stories for Epic N
-- Retrospective for Epic N
-- Epic N+1 entry
-- etc.

package/pennyfarthing-dist/workflows/sprint-planning/steps/step-03-status-detection.md

@@ -1,80 +0,0 @@
----
-name: 'step-03-status-detection'
-description: 'Apply intelligent status detection based on file existence and existing status'
-
-# Path Definitions
-workflow_path: '{project_root}/.pennyfarthing/workflows/sprint-planning'
-
-# File References
-thisStepFile: './step-03-status-detection.md'
-nextStepFile: './step-04-generate-status-file.md'
----
-
-<purpose>
-Apply intelligent status detection based on file existence and existing status. Automatically upgrade story statuses based on physical story files and preserve advanced statuses from existing status files.
-</purpose>
-
-<instructions>
-For each story from step 2, apply the following detection logic:
-1. Check if story file exists at `{story_location}/{story-key}.md` (e.g., `stories/1-1-user-authentication.md`)
-2. If story file exists, upgrade status to at least `ready-for-dev`
-3. Apply preservation rule: If existing `{status_file}` exists with more advanced status, preserve it (never downgrade status)
-4. Use the status flow references provided: Epic flows from backlog → in-progress → done, Stories flow from backlog → ready-for-dev → in-progress → review → done, Retrospectives toggle between optional ↔ done
-</instructions>
-
-<output>
-Sprint status structure with all statuses intelligently detected and set based on file existence and existing status file values, ready for YAML generation.
-</output>
-
-# Step 3: Apply Intelligent Status Detection
-
-## Goal
-
-Apply intelligent status detection based on file existence and existing status.
-
-## Actions
-
-For each story, detect current status by checking files:
-
-### Story File Detection
-
-- Check: `{story_location}/{story-key}.md` (e.g., `stories/1-1-user-authentication.md`)
-- If exists → upgrade status to at least `ready-for-dev`
-
-### Preservation Rule
-
-- If existing `{status_file}` exists and has more advanced status, preserve it
-- Never downgrade status (e.g., don't change `done` to `ready-for-dev`)
-
-## Status Flow Reference
-
-### Epic Status
-
-```
-backlog → in-progress → done
-```
-
-- **backlog**: Epic not yet started
-- **in-progress**: Epic actively being worked on (stories being created/implemented)
-- **done**: All stories in epic completed
-
-### Story Status
-
-```
-backlog → ready-for-dev → in-progress → review → done
-```
-
-- **backlog**: Story only exists in epic file
-- **ready-for-dev**: Story file created (e.g., `stories/1-3-plant-naming.md`)
-- **in-progress**: Developer actively working
-- **review**: Ready for code review
-- **done**: Completed
-
-### Retrospective Status
-
-```
-optional ↔ done
-```
-
-- **optional**: Ready to be conducted but not required
-- **done**: Finished

package/pennyfarthing-dist/workflows/sprint-planning/steps/step-04-generate-status-file.md

@@ -1,90 +0,0 @@
----
-name: 'step-04-generate-status-file'
-description: 'Generate the sprint status YAML file with all epics, stories, and retrospectives'
-
-# Path Definitions
-workflow_path: '{project_root}/.pennyfarthing/workflows/sprint-planning'
-
-# File References
-thisStepFile: './step-04-generate-status-file.md'
-nextStepFile: './step-05-validate-and-report.md'
----
-
-<purpose>
-Generate the sprint status YAML file with all epics, stories, and retrospectives. Create or update the status file with complete metadata and development_status structure.
-</purpose>
-
-<instructions>
-Create or update `{status_file}` with the complete structure:
-1. Add metadata comments for documentation: generated date, project name, tracking_system (file-system), and story_location
-2. Include comprehensive status definitions comments for Epic, Story, and Retrospective statuses with their transitions
-3. Add workflow notes explaining epic transitions, parallel story work, SM story creation patterns, and dev to review workflow
-4. CRITICAL: Include metadata fields TWICE - once as comments for documentation, once as YAML key:value fields for parsing
-5. Populate development_status section with all items from step 3 in proper epic grouping order
-</instructions>
-
-<output>
-A complete, well-documented sprint status YAML file at `{status_file}` with all epics, stories, and retrospectives properly structured and ready for validation.
-</output>
-
-# Step 4: Generate Sprint Status File
-
-## Goal
-
-Generate the sprint status YAML file with all epics, stories, and retrospectives.
-
-## Actions
-
-Create or update `{status_file}` with the following structure:
-
-## File Structure
-
-```yaml
-# generated: {date}
-# project: {project_name}
-# tracking_system: file-system
-# story_location: {story_location}
-
-# STATUS DEFINITIONS:
-# ==================
-# Epic Status:
-#   - backlog: Epic not yet started
-#   - in-progress: Epic actively being worked on
-#   - done: All stories in epic completed
-#
-# Epic Status Transitions:
-#   - backlog → in-progress: Automatically when first story is created
-#   - in-progress → done: Manually when all stories reach 'done' status
-#
-# Story Status:
-#   - backlog: Story only exists in epic file
-#   - ready-for-dev: Story file created in stories folder
-#   - in-progress: Developer actively working on implementation
-#   - review: Ready for code review
-#   - done: Story completed
-#
-# Retrospective Status:
-#   - optional: Can be completed but not required
-#   - done: Retrospective has been completed
-#
-# WORKFLOW NOTES:
-# ===============
-# - Epic transitions to 'in-progress' automatically when first story is created
-# - Stories can be worked in parallel if team capacity allows
-# - SM typically creates next story after previous one is 'done' to incorporate learnings
-# - Dev moves story to 'review', then runs code-review
-
-generated: {date}
-project: {project_name}
-tracking_system: file-system
-story_location: {story_location}
-
-development_status:
-  # All epics, stories, and retrospectives in order
-```
-
-## Critical Notes
-
-- **CRITICAL**: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing
-- Ensure all items are ordered: epic, its stories, its retrospective, next epic...
-- Write the complete sprint status YAML to `{status_file}`

package/pennyfarthing-dist/workflows/sprint-planning/steps/step-05-validate-and-report.md

@@ -1,78 +0,0 @@
----
-name: 'step-05-validate-and-report'
-description: 'Validate the generated sprint status file and report results'
-
-# Path Definitions
-workflow_path: '{project_root}/.pennyfarthing/workflows/sprint-planning'
-
-# File References
-thisStepFile: './step-05-validate-and-report.md'
-nextStepFile: null
----
-
-<purpose>
-Validate the generated sprint status file and report results. Ensure data integrity and completeness before concluding the sprint planning workflow.
-</purpose>
-
-<instructions>
-Perform comprehensive validation checks on the generated `{status_file}`:
-1. Verify every epic in epic files appears in the status file
-2. Verify every story in epic files appears in the status file
-3. Verify every epic has a corresponding retrospective entry
-4. Verify no items in status file that don't exist in epic files
-5. Verify all status values are legal and match state machine definitions
-6. Verify file is valid YAML syntax
-
-Calculate and report totals: total epics, total stories, epics in-progress count, and stories done count.
-
-Display completion summary to user with file location, total counts, and next steps for status file usage.
-</instructions>
-
-<output>
-Validation report confirming all data integrity checks pass, summary statistics showing epic and story counts with status breakdowns, and confirmation message that sprint status has been successfully generated.
-</output>
-
-# Step 5: Validate and Report
-
-## Goal
-
-Validate the generated sprint status file and report results.
-
-## Validation Checks
-
-Perform the following validation checks:
-
-- [ ] Every epic in epic files appears in `{status_file}`
-- [ ] Every story in epic files appears in `{status_file}`
-- [ ] Every epic has a corresponding retrospective entry
-- [ ] No items in `{status_file}` that don't exist in epic files
-- [ ] All status values are legal (match state machine definitions)
-- [ ] File is valid YAML syntax
-
-## Count Totals
-
-Calculate and report:
-
-- Total epics: `{epic_count}`
-- Total stories: `{story_count}`
-- Epics in-progress: `{in_progress_count}`
-- Stories done: `{done_count}`
-
-## Completion Summary
-
-Display to user:
-
-**Sprint Status Generated Successfully**
-
-- **File Location:** `{status_file}`
-- **Total Epics:** `{epic_count}`
-- **Total Stories:** `{story_count}`
-- **Epics In Progress:** `{epics_in_progress_count}`
-- **Stories Completed:** `{done_count}`
-
-## Next Steps
-
-1. Review the generated `{status_file}`
-2. Use this file to track development progress
-3. Agents will update statuses as they work
-4. Re-run this workflow to refresh auto-detected statuses

package/pennyfarthing-dist/workflows/sprint-planning/workflow.yaml

@@ -1,34 +0,0 @@
-# sprint-planning Workflow - Migrated from BMAD format
-# Manual migration (source used workflow.yaml + instructions.md format)
-
-workflow:
-  name: sprint-planning
-  description: Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle.
-  version: "1.0.0"
-  type: stepped
-
-  # Step configuration
-  steps:
-    path: ./steps/
-    pattern: step-*.md
-
-  # Variables available in step files
-  variables:
-    project_root: .
-    planning_artifacts: ./artifacts
-    implementation_artifacts: ./artifacts
-    epics_location: ./artifacts
-    epics_pattern: "epic*.md"
-    status_file: artifacts/sprint-status.yaml
-    output_file: artifacts/sprint-status.yaml
-
-  # Agent assignment - SM handles sprint planning
-  agent: sm
-
-  # Triggers - when to suggest this workflow
-  triggers:
-    types: [sprint-planning, sprint-status]
-    tags: [sprint-planning, implementation, stepped]
-
-  # Standalone workflow (not part of TDD cycle)
-  standalone: true

package/pennyfarthing-dist/workflows/tdd.yaml

@@ -1,50 +0,0 @@
-# TDD Workflow - Test-Driven Development
-# Default workflow for feature development in Pennyfarthing
-#
-# Flow: SM → TEA → Dev → Reviewer → SM
-# Scale routing: 1-2 pts use 'trivial' workflow instead
-
-workflow:
-  name: tdd
-  description: Test-driven development with code review
-  version: "1.0.0"
-
-  phases:
-    - name: setup
-      agent: sm
-      output: [session_file, branches, story_context]
-
-    - name: red
-      agent: tea
-      input: [session_file, story_context]
-      output: [failing_tests]
-      gate:
-        type: tests_fail
-        condition: All acceptance criteria have test coverage
-
-    - name: green
-      agent: dev
-      input: [failing_tests, story_context]
-      output: [implementation, passing_tests]
-      gate:
-        type: tests_pass
-        condition: All tests passing, no skipped tests
-
-    - name: review
-      agent: reviewer
-      input: [implementation, passing_tests]
-      output: [approval]
-      gate:
-        type: approval
-        condition: Code review approved, no blocking issues
-
-    - name: finish
-      agent: sm
-      input: [approval]
-      output: [archived_session, story_summary]
-
-  triggers:
-    types: [feature, enhancement]
-    points:
-      min: 3
-    default: true

package/pennyfarthing-dist/workflows/trivial.yaml

@@ -1,40 +0,0 @@
-# Trivial Workflow - Quick Fixes
-# For small changes that don't need full TDD ceremony
-#
-# Flow: SM → Dev → Reviewer → SM (skips TEA)
-# Use for: chores, fixes, 1-2 point stories
-
-workflow:
-  name: trivial
-  description: Quick fixes without full TDD ceremony
-  version: "1.0.0"
-
-  phases:
-    - name: setup
-      agent: sm
-      output: [session_file, branches]
-
-    - name: impl
-      agent: dev
-      input: [session_file]
-      output: [implementation]
-      gate:
-        type: tests_pass
-        condition: Existing tests still pass
-
-    - name: review
-      agent: reviewer
-      input: [implementation]
-      output: [approval]
-      gate:
-        type: approval
-
-    - name: finish
-      agent: sm
-      input: [approval]
-      output: [archived_session]
-
-  triggers:
-    types: [chore, fix, refactor]
-    points:
-      max: 2