@pennyfarthing/core 11.0.0 → 11.1.1

package/pennyfarthing-dist/commands/pf-epic.md

@@ -0,0 +1,67 @@
+---
+description: Epic lifecycle - start epics for development and close completed epics
+args: "[start|close] <epic-id>"
+---
+
+# Epic Management
+
+<purpose>
+Manage epic lifecycle. Start an epic by moving it to the current sprint and generating tech context. Close an epic by verifying completion, updating status, and archiving context.
+</purpose>
+
+## Commands
+
+### `/pf-epic start <epic-id>`
+
+Start an epic — move to current sprint and generate technical context.
+
+```bash
+pf epic start 79
+pf epic start epic-79
+```
+
+<workflow>
+1. Parse epic ID (strip `epic-` prefix if present)
+2. Check epic location (current sprint or backlog)
+3. Move to current sprint if needed, set status to `in-progress`
+4. Invoke SM agent for `epic-tech-context` task
+5. Generate tech context to `sprint/context/context-epic-{N}.md`
+</workflow>
+
+### `/pf-epic close <epic-id>`
+
+Close an epic — verify completion, update status, and archive context.
+
+```bash
+pf epic close 79
+pf epic close epic-79
+```
+
+<workflow>
+1. Parse epic ID
+2. Verify all stories have `status: done`
+3. Update epic: `status: done`, calculate `completed_points`
+4. Recalculate sprint summary totals
+5. Transition Jira epic to Done (if jira key exists)
+6. Archive context file to `sprint/archive/`
+7. Commit and push sprint changes
+</workflow>
+
+## Quick Reference
+
+| Command | Description |
+|---------|-------------|
+| `/pf-epic start <id>` | Start epic for development |
+| `/pf-epic close <id>` | Close completed epic |
+
+## CLI Equivalent
+
+```bash
+pf epic start <epic-id>
+pf epic close <epic-id>
+```
+
+## Related
+
+- `/pf-sprint` — Sprint management
+- `/sm` — Scrum Master for epic tech context

package/pennyfarthing-dist/commands/pf-git-cleanup.md

@@ -1,57 +1,16 @@
 ---
-description: Clean up git repos by organizing changes into proper commits/branches by initiative
-workflow: git-cleanup
+deprecated: true
+redirect: pf-git
+description: "DEPRECATED: Use /pf-git cleanup instead."
 ---
 
-# Git Cleanup Command
+# /git-cleanup - DEPRECATED
 
-Organize uncommitted changes into proper commits and branches across **all configured repos**.
+Git commands have been consolidated into `/pf-git`. Use:
 
-## Quick Start
-
-Run `/git-cleanup` to start the stepped workflow.
-
-## Multi-Repo Support
-
-This workflow handles multiple repos defined in `.claude/project/pennyfarthing-settings.yaml`.
-
-**CRITICAL:** Always use the multi-repo status script, not plain `git status`:
-
-```bash
-.pennyfarthing/scripts/git/git-status-all.sh
-```
-
-For operations in a specific repo, use `git -C {repo_path}`:
-
-```bash
-git -C pennyfarthing status --short
-git -C pennyfarthing diff
-```
-
-## Workflow Steps
-
-| Step | Name | Purpose |
-|------|------|---------|
-| 1 | Analyze | Gather status from ALL repos |
-| 2 | Categorize | Group changes by initiative (may span repos) |
-| 3 | Execute | Create branches, commit, merge in each repo |
-| 4 | Verify | Confirm clean state across all repos |
-| 5 | Complete | Push and summary |
-
-## Critical Rules
-
-- **NEVER** commit directly to develop (use branches)
-- **NEVER** force push
-- **ALWAYS** use `git -C {repo_path}` for subrepo operations
-- **ALWAYS** check ALL repos, not just the orchestrator
-
-## Commit Types
-
-| Prefix | Use For |
-|--------|---------|
-| `feat:` | New features |
-| `fix:` | Bug fixes |
-| `chore:` | Maintenance |
-| `docs:` | Documentation |
-| `refactor:` | Code improvement |
-| `test:` | Test changes |
+| Old Command | New Command |
+|-------------|-------------|
+| `/repo-status` | `/pf-git status` |
+| `/git-cleanup` | `/pf-git cleanup` |
+| `/create-branches-from-story` | `/pf-git branches` |
+| `/release` | `/pf-git release` |

package/pennyfarthing-dist/commands/pf-git.md

@@ -0,0 +1,75 @@
+---
+description: Repository operations - status, cleanup, branches, and release management
+args: "[status|cleanup|branches|release] [args...]"
+---
+
+# Git Operations
+
+<purpose>
+Manage git operations across all configured repos. Consolidates repository status, git cleanup, branch creation, and release management into a single resource group.
+</purpose>
+
+## Commands
+
+### `/pf-git status`
+
+Check git status of all project repos.
+
+```bash
+pf git status [--brief]
+```
+
+Shows branch, uncommitted changes, and ahead/behind status for each configured repo.
+
+### `/pf-git cleanup`
+
+Organize uncommitted changes into proper commits and branches.
+
+```bash
+pf git cleanup
+```
+
+Starts the git-cleanup stepped workflow via BikeLane. Handles multiple repos.
+
+### `/pf-git branches <story-id>`
+
+Create feature branches in both repos from a story.
+
+```bash
+pf git branches 86-3
+```
+
+### `/pf-git release`
+
+Interactive release with verification gates.
+
+```bash
+pf git release
+```
+
+Starts the release stepped workflow — an 11-step process with gates at each stage.
+
+## Quick Reference
+
+| Command | Description |
+|---------|-------------|
+| `/pf-git status` | Check all repo status |
+| `/pf-git cleanup` | Organize changes into commits/branches |
+| `/pf-git branches <id>` | Create feature branches from story |
+| `/pf-git release` | Interactive release workflow |
+
+## CLI Equivalent
+
+All commands are also available via `pf git`:
+
+```bash
+pf git status
+pf git cleanup
+pf git branches 86-3
+pf git release
+```
+
+## Related
+
+- `/pf-chore` — Quick commit for small changes
+- `/pf-standalone` — Wrap changes into standalone story + PR

package/pennyfarthing-dist/commands/pf-help.md

@@ -7,23 +7,15 @@ Get help with Pennyfarthing commands, agents, themes, and workflows.
 Provides quick-start guidance for new users and context-aware suggestions based on current work state.
 </purpose>
 
-<when-to-use>
-- New to Pennyfarthing and need orientation
-- Looking for a specific command or agent
-- Want to understand the TDD workflow
-- Need to check available themes
-- Forgot what command to use next
-</when-to-use>
-
 <quick-start>
 
 ## New to Pennyfarthing?
 
 Start here:
 
-1. **`/work`** - Smart entry point (resumes existing work or starts new)
-2. **`/new-work`** - Start a fresh work session from backlog
-3. **`/health-check`** - Verify your installation is working
+1. **`/pf-work`** - Smart entry point (resumes existing work or starts new)
+2. **`/pf-session new`** - Start a fresh work session from backlog
+3. **`/pf-health-check`** - Verify your installation is working
 
 ### First Time Setup
 
@@ -52,120 +44,127 @@ SM → TEA → Dev → Reviewer → SM (finish)
 | Review | Reviewer | `/reviewer` | Code review, quality enforcement |
 | Finish | SM | `/sm` | Merge PR, archive session |
 
-### Workflow Commands
-
-| Command | Description |
-|---------|-------------|
-| `/new-work` | Start a new work session with Pennyfarthing |
-| `/work` | Resume work or start new - smart entry point |
-| `/sm` | Scrum Master - Story coordination and sprint management |
-| `/tea` | Test Engineer/Architect - Test strategy and TDD |
-| `/dev` | Developer - Feature implementation and coding |
-| `/reviewer` | Code Reviewer - Critical code review and quality enforcement |
-| `/check` | Run quality gates (lint, type check, tests) before handoff |
-
 </workflow>
 
-<agents>
-
-## All Agents (24)
-
-### TDD Workflow Agents
-
-| Agent | Command | Role |
-|-------|---------|------|
-| SM | `/sm` | Scrum Master - Story coordination, sprint management, workflow entry/exit |
-| TEA | `/tea` | Test Engineer - Test strategy, TDD design, RED phase |
-| Dev | `/dev` | Developer - Implementation, feature shipping, GREEN phase |
-| Reviewer | `/reviewer` | Code Reviewer - Quality enforcement, adversarial review |
+<commands>
 
-### Specialist Agents
+## Resource Groups
 
-| Agent | Command | Role |
-|-------|---------|------|
-| Architect | `/architect` | System Architect - Technical design and architecture |
-| PM | `/pm` | Product Manager - Strategic planning and prioritization |
-| DevOps | `/devops` | DevOps Engineer - Infrastructure and deployment automation |
-| Tech-Writer | `/tech-writer` | Technical Writer - Documentation creation and maintenance |
-| UX-Designer | `/ux-designer` | UX Designer - User experience design and UI patterns |
-| Orchestrator | `/orchestrator` | Orchestrator - Coordinator of all agents and meta operations |
+Commands are organized by resource. Each group is accessible via both slash commands and CLI.
 
-</agents>
+### Sprint — `/pf-sprint` · `pf sprint`
 
-<commands>
+| Command | Description |
+|---------|-------------|
+| `/pf-sprint` | Show sprint status |
+| `/pf-sprint backlog` | Available stories |
+| `/pf-sprint work [id\|next]` | Start work on a story |
+| `/pf-sprint archive <id>` | Archive completed story |
+| `/pf-sprint plan` | Sprint planning session |
+| `/pf-sprint sync` | Sync work with sprint |
+| `/pf-sprint story [show\|add\|update\|size\|finish]` | Story operations |
+| `/pf-sprint epic [show\|add\|promote\|archive]` | Epic operations |
 
-## All Commands (43)
+### Git — `/pf-git` · `pf git`
 
-### TDD Workflow (7)
 | Command | Description |
 |---------|-------------|
-| `/new-work` | Start a new work session with Pennyfarthing |
-| `/work` | Resume work or start new - smart entry point |
-| `/sm` | Scrum Master - Story coordination and sprint management |
-| `/tea` | Test Engineer/Architect - Test strategy and TDD |
-| `/dev` | Developer - Feature implementation and coding |
-| `/reviewer` | Code Reviewer - Critical code review and quality enforcement |
-| `/check` | Run quality gates (lint, type check, tests) before handoff |
-
-### Specialist Agents (6)
+| `/pf-git status` | Check all repo status |
+| `/pf-git cleanup` | Organize changes into commits/branches |
+| `/pf-git branches <id>` | Create feature branches from story |
+| `/pf-git release` | Interactive release workflow |
+
+### Session — `/pf-session` · `pf session`
+
 | Command | Description |
 |---------|-------------|
-| `/architect` | System Architect - Technical design and architecture |
-| `/pm` | Product Manager - Strategic planning and prioritization |
-| `/devops` | DevOps Engineer - Infrastructure and deployment automation |
-| `/tech-writer` | Technical Writer - Documentation creation and maintenance |
-| `/ux-designer` | UX Designer - User experience design and UI patterns |
-| `/orchestrator` | Orchestrator - Coordinator of all agents and meta operations |
-
-### Sprint & Planning (5)
+| `/pf-session new` | Start next available story |
+| `/pf-session continue` | Resume from checkpoint |
+
+### Epic — `/pf-epic` · `pf epic`
+
 | Command | Description |
 |---------|-------------|
-| `/sprint-planning` | Facilitate sprint planning session |
-| `/start-epic` | Start an epic - move to current sprint and generate tech context |
-| `/retro` | Facilitate a sprint retrospective |
-| `/sync-work-with-sprint` | Sync Pennyfarthing work session with unified sprint status |
-| `/sync-epic-to-jira` | Sync Pennyfarthing epic to Jira MSSCI project |
+| `/pf-epic start <id>` | Start epic for development |
+| `/pf-epic close <id>` | Close completed epic |
+
+### Jira — `/pf-jira` · `pf jira`
 
-### Context & Loading (2)
 | Command | Description |
 |---------|-------------|
-| `/prime` | Load essential project context at agent activation |
-| `/health-check` | Check Pennyfarthing installation health and apply updates |
+| `/pf-jira view <key>` | View issue details |
+| `/pf-jira claim <key>` | Claim issue |
+| `/pf-jira sync <epic-id>` | Sync YAML to Jira |
+| `/pf-jira sync-epic` | Sync epic to Jira |
+| `/pf-jira reconcile` | Report mismatches |
+
+### Theme — `/pf-theme` · `pf theme`
 
-### Theme Management (1)
 | Command | Description |
 |---------|-------------|
-| `/theme [list\|show\|set\|create\|maker]` | Manage persona themes — list, show, set, create, or interactive wizard |
+| `/pf-theme list` | List all themes |
+| `/pf-theme show [name]` | Show theme details |
+| `/pf-theme set <name>` | Set active theme |
+| `/pf-theme create <name>` | Create custom theme |
+| `/pf-theme maker` | Interactive theme wizard |
+
+### Workflow — `/pf-workflow` · `pf workflow`
 
-### Creative & Brainstorm (4)
 | Command | Description |
 |---------|-------------|
-| `/party-mode` | Free-form creative brainstorming with all agents |
-| `/brainstorm` | Structured problem-solving brainstorm session |
-| `/job-fair` | Discover which characters in a theme excel at each role |
-| `/solo` | Run a single agent on a scenario with absolute rubric scoring |
+| `/pf-workflow` | List available workflows |
+| `/pf-workflow show` | Current workflow details |
+| `/pf-workflow start <name>` | Start stepped workflow |
+| `/pf-workflow resume` | Resume workflow |
+
+## Agents (11)
+
+| Agent | Command | Role |
+|-------|---------|------|
+| SM | `/sm` | Scrum Master — Story coordination, sprint management |
+| TEA | `/tea` | Test Engineer — Test strategy, TDD design |
+| Dev | `/dev` | Developer — Implementation, feature shipping |
+| Reviewer | `/reviewer` | Code Reviewer — Quality enforcement |
+| Architect | `/architect` | System Architect — Technical design |
+| PM | `/pm` | Product Manager — Strategic planning |
+| DevOps | `/devops` | DevOps — Infrastructure and deployment |
+| Tech-Writer | `/tech-writer` | Technical Writer — Documentation |
+| UX-Designer | `/ux-designer` | UX Designer — User experience |
+| Orchestrator | `/orchestrator` | Orchestrator — Multi-agent coordination |
+| BA | `/ba` | Business Analyst — Requirements discovery |
+
+## Utilities
 
-### Benchmarking (2)
 | Command | Description |
 |---------|-------------|
-| `/benchmark` | Compare an agent's performance against a stored baseline |
-| `/benchmark-control` | Create control baseline for a scenario |
+| `/pf-work` | Smart entry point — resume or start new |
+| `/pf-check` | Run quality gates before handoff |
+| `/pf-prime` | Load project context at agent activation |
+| `/pf-health-check` | Check installation health |
+| `/pf-setup` | First-time project setup |
+| `/pf-chore` | Quick commit for small changes |
+| `/pf-patch` | Bug fix during active story work |
+| `/pf-standalone` | Wrap changes into standalone story |
+| `/pf-ci run` | Detect and run CI locally |
+| `/pf-docs update` | Update domain documentation |
+| `/pf-permissions` | Manage runtime permissions |
+
+## Benchmarking
 
-### Git & Repository (4)
 | Command | Description |
 |---------|-------------|
-| `/repo-status` | Check git status of all project repos |
-| `/git-cleanup` | Clean up git repos by organizing changes into commits/branches |
-| `/create-branches-from-story` | Create feature branches in both repos from a story |
-| `/release` | Merge develop to main and push (optional version bump) |
+| `/pf-benchmark` | Compare performance against baseline |
+| `/pf-benchmark-control` | Create control baseline |
+| `/pf-job-fair` | Discover best characters per role |
+| `/pf-solo` | Single agent rubric scoring |
+
+## Creative
 
-### Utility (4)
 | Command | Description |
 |---------|-------------|
-| `/continue-session` | Resume work from a saved checkpoint after context circuit breaker |
-| `/parallel-work` | Start parallel work in a new worktree |
-| `/update-domain-docs` | Update CLAUDE-*.md domain documentation files |
-| `/help` | This help command |
+| `/pf-party-mode` | Creative brainstorming with all agents |
+| `/pf-brainstorming` | Structured problem-solving session |
+| `/pf-retro` | Sprint retrospective |
 
 </commands>
 
@@ -188,24 +187,7 @@ Pennyfarthing agents adopt personas from themed character sets. There are **102
 | `breaking-bad` | Breaking Bad characters |
 | `battlestar-galactica` | Battlestar Galactica characters |
 
-Run `/theme list` to see all 102 available themes.
-
-### Theme Commands
-
-| Command | Description |
-|---------|-------------|
-| `/theme list` | See all available themes |
-| `/theme show [name]` | View current theme with character mappings |
-| `/theme set <name>` | Change to a different theme |
-| `/theme create <name>` | Create a custom theme |
-| `/theme maker` | Interactive theme creation wizard |
-
-### Current Theme
-
-Check your current theme:
-```bash
-cat .pennyfarthing/config.local.yaml
-```
+Run `/pf-theme list` to see all 102 available themes.
 
 </themes>
 
@@ -216,11 +198,11 @@ cat .pennyfarthing/config.local.yaml
 Based on your current state, here's what you might need:
 
 ### No Active Session
-- Use `/work` or `/new-work` to begin
-- Check `/health-check` if first time
+- Use `/pf-work` or `/pf-session new` to begin
+- Check `/pf-health-check` if first time
 
 ### In Dev Phase
-- Run `/check` before handoff
+- Run `/pf-check` before handoff
 - Then `/reviewer` for code review
 
 ### In Review Phase
@@ -228,13 +210,24 @@ Based on your current state, here's what you might need:
 - Then `/sm` to finish the story
 
 ### Between Stories
-- `/work` to pick up next story
-- `/sprint-planning` for planning session
+- `/pf-work` to pick up next story
+- `/pf-sprint plan` for planning session
 
 </context-aware>
 
 <reference>
 
+## CLI Help
+
+For detailed help on any command group:
+```bash
+pf help           # Overview of all groups
+pf help sprint    # Sprint commands
+pf help git       # Git commands
+pf help session   # Session commands
+pf help epic      # Epic commands
+```
+
 ## Documentation
 
 - **Project Setup:** `CLAUDE.md`
@@ -242,19 +235,8 @@ Based on your current state, here's what you might need:
 - **Active Session:** `.session/*-session.md`
 - **Agent Definitions:** `pennyfarthing-dist/agents/*.md`
 - **Command Definitions:** `pennyfarthing-dist/commands/*.md`
+- **Command Registry:** `pennyfarthing-dist/command-registry.yaml`
 - **Theme Files:** `pennyfarthing-dist/personas/themes/*.yaml`
 - **Guides:** `.pennyfarthing/guides/*.md`
 
-## Getting More Help
-
-For detailed help on a specific command, read its definition file:
-```bash
-cat pennyfarthing-dist/commands/<command-name>.md
-```
-
-For agent documentation:
-```bash
-cat pennyfarthing-dist/agents/<agent-name>.md
-```
-
 </reference>

package/pennyfarthing-dist/commands/pf-job-fair.md

@@ -0,0 +1,102 @@
+---
+description: Discover which characters in a theme excel at each role
+argument-hint: <theme> [--runs N] [--roles <list>]
+---
+
+# Job Fair
+
+Run every character in a theme against benchmarks to find hidden talents.
+
+## Usage
+
+```
+/job-fair <theme>
+/job-fair <theme> --runs 2
+/job-fair <theme> --roles dev,reviewer
+```
+
+## On Invoke
+
+**Arguments:** $ARGUMENTS
+
+### Step 1: Parse and Validate
+
+```bash
+# Theme is first positional arg (strip any --flags)
+THEME=$(echo "$ARGUMENTS" | awk '{print $1}' | sed 's/^--theme[= ]//')
+
+# Check theme exists
+ls pennyfarthing-dist/personas/themes/${THEME}.yaml
+```
+
+If not found, list available themes and stop.
+
+Extract `--runs N` (default: 4) and `--roles x,y` (default: all with baselines).
+
+### Step 2: Load Characters
+
+Read `pennyfarthing-dist/personas/themes/${THEME}.yaml` and list agents:
+
+| Role | Character |
+|------|-----------|
+| sm | {agents.sm.character} |
+| dev | {agents.dev.character} |
+| ... | ... |
+
+### Step 3: Find Baselines
+
+Pick ONE scenario per role from `internal/results/baselines/`:
+
+```bash
+# For each role, find first available baseline
+for role in dev reviewer tea sm architect; do
+  baseline=$(ls -d internal/results/baselines/*/${role} 2>/dev/null | head -1)
+  if [ -n "$baseline" ]; then
+    scenario=$(basename $(dirname "$baseline"))
+    summary="$baseline/summary.yaml"
+    # Read statistics.mean and statistics.n from summary.yaml
+  fi
+done
+```
+
+Show table:
+
+| Role | Scenario | Baseline | n |
+|------|----------|----------|---|
+| dev | race-condition-cache | 76.8 | 10 |
+
+### Step 4: Confirm
+
+Show: `{characters} × {roles} × {runs} = {total} runs`
+
+Ask user to confirm or cancel.
+
+### Step 5: Execute
+
+For each role, for each character:
+
+```bash
+# Native role
+scripts/solo-runner.sh "${THEME}:${role}" "${scenario}" ${runs}
+
+# Cross-role (character playing different role)
+scripts/solo-runner.sh "${THEME}:${native_role}" "${scenario}" ${runs} --as ${target_role}
+```
+
+Show progress as each completes.
+
+### Step 6: Report Results
+
+Show champions per role and full matrix:
+
+| Character | dev | reviewer | tea | sm | Avg |
+|-----------|-----|----------|-----|-----|-----|
+| ... | ... | ... | ... | ... | ... |
+
+Save to `internal/results/job-fair/${THEME}-${timestamp}/summary.yaml`
+
+## Reference
+
+- Theme files: `pennyfarthing-dist/personas/themes/*.yaml`
+- Baselines: `internal/results/baselines/{scenario}/{role}/summary.yaml`
+- Solo runner: `scripts/solo-runner.sh`

package/pennyfarthing-dist/commands/pf-new-work.md

@@ -1,23 +1,14 @@
 ---
-description: Start the next available story from the sprint backlog
+deprecated: true
+redirect: pf-session
+description: "DEPRECATED: Use /pf-session new instead."
 ---
 
-# New Work
+# /new-work - DEPRECATED
 
-<purpose>
-Shortcut to start the highest priority available story. Alias for `/pf-sprint work next`.
-</purpose>
+Session commands have been consolidated into `/pf-session`. Use:
 
-<on-invoke>
-Invoke the sprint work command with "next" to auto-select the highest priority story:
-
-```
-/pf-sprint work next
-```
-</on-invoke>
-
-<related>
-- `/pf-sprint work` - Interactive story selection
-- `/pf-sprint backlog` - View available stories
-- `/work` - Resume existing work or start new
-</related>
+| Old Command | New Command |
+|-------------|-------------|
+| `/new-work` | `/pf-session new` |
+| `/continue-session` | `/pf-session continue` |