@pennyfarthing/core 11.2.0 → 11.2.2

package/pennyfarthing-dist/agents/sm-finish.md

@@ -15,7 +15,24 @@ model: haiku
 </arguments>
 
 <execution>
-## Run Preflight Script
+## 1. Create PR (if needed)
+
+Before running preflight, check if a PR exists for the branch. If not, create one
+using the project's `pr_mode` config:
+
+```bash
+# Read pr_mode: draft | ready | none
+PR_MODE=$(source .venv/bin/activate && python -m pennyfarthing_scripts.common.pr_config)
+```
+
+- If `PR_MODE=draft`: `gh pr create --draft --title "feat({STORY_ID}): {title}" --body "..." --base develop`
+- If `PR_MODE=ready`: `gh pr create --title "feat({STORY_ID}): {title}" --body "..." --base develop`
+- If `PR_MODE=none`: Skip PR creation entirely.
+
+Check for existing PR first: `gh pr list --head {BRANCH} --json number --jq '.[0].number'`
+If a PR already exists, skip creation.
+
+## 2. Run Preflight Script
 
 The preflight script runs all checks in parallel using asyncio:
 
@@ -36,7 +53,7 @@ The script returns JSON with:
 <critical>
 ## Jira Transition
 
-The Jira transition to Done is handled by `pf sprint story finish`.
+The Jira transition to Done is handled by `pf.sh sprint story finish`.
 Do NOT transition Jira here - that would duplicate the finish script's work.
 This subagent only performs preflight checks and assessment.
 </critical>

package/pennyfarthing-dist/agents/sm-setup.md

@@ -26,7 +26,7 @@ model: haiku
 
 - [ ] Use `/pf-sprint backlog` for initial backlog scan:
   ```bash
-  pf sprint backlog
+  "$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint backlog
   ```
 - [ ] Use `/pf-jira` skill to enrich with Jira status/assignee:
   - `/pf-jira search "project=MSSCI AND sprint in openSprints()"` - Get all sprint stories
@@ -92,10 +92,10 @@ Other formats break Cyclist detection.
 EPIC_NUM=$(echo "{STORY_ID}" | cut -d'-' -f1)
 
 # Get epic's Jira key (use script, not direct yq)
-EPIC_JIRA=$(pf sprint epic field "$EPIC_NUM" jira)
+EPIC_JIRA=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint epic field "$EPIC_NUM" jira)
 ```
 
-If missing or "null": auto-create via `pf jira create epic {EPIC_NUM}`
+If missing or "null": auto-create via `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira create epic {EPIC_NUM}`
 
 ## Step 2: Check Workflow Permissions
 
@@ -135,14 +135,14 @@ GRANTS=$(cat .claude/settings.local.json 2>/dev/null | jq '.permissions.grants /
 
 ## Step 3: Claim in Jira
 
-Use `pf jira check` and `pf jira claim` commands:
+Use the pf wrapper for Jira commands:
 
 ```bash
 # Check availability first
-pf jira check {JIRA_KEY}
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira check {JIRA_KEY}
 
 # Then claim (assign to self + move to In Progress)
-pf jira claim {JIRA_KEY}
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira claim {JIRA_KEY}
 ```
 
 **Exit codes:**
@@ -184,7 +184,7 @@ git checkout -b feat/{STORY_ID}-{SLUG}
 After session file is created, determine how to route:
 
 ```bash
-WORKFLOW_TYPE=$(pf workflow type "{WORKFLOW}")
+WORKFLOW_TYPE=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow type "{WORKFLOW}")
 ```
 
 | Workflow Type | Routing |

package/pennyfarthing-dist/agents/sm.md

@@ -25,12 +25,12 @@ The moment you start reading implementation files or planning how code should wo
 </critical>
 
 <critical>
-Use `pf jira <command>` for all Jira interactions. Key commands:
+Use the pf wrapper for all Jira interactions. Key commands:
 ```
-pf jira check MSSCI-XXXXX       # Check story availability
-pf jira claim MSSCI-XXXXX       # Claim story (assign + In Progress)
-pf jira move MSSCI-XXXXX "Done" # Transition status
-pf jira reconcile               # Audit YAML vs Jira
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira check MSSCI-XXXXX       # Check story availability
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira claim MSSCI-XXXXX       # Claim story (assign + In Progress)
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira move MSSCI-XXXXX "Done" # Transition status
+"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira reconcile               # Audit YAML vs Jira
 ```
 If they are broken, COMPLAIN LOUDLY
 </critical>
@@ -107,7 +107,7 @@ Prime script provides workflow state. Route based on state from activation outpu
 
 2. **Run finish command:**
    ```bash
-   pf sprint story finish {STORY_ID}
+   "$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint story finish {STORY_ID}
    ```
 
 3. **Commit results:**
@@ -153,8 +153,8 @@ Present to user:
 
 1. **Get workflow type:**
    ```bash
-   WORKFLOW=$(pf sprint story field X-Y workflow)
-   WORKFLOW_TYPE=$(pf workflow type "$WORKFLOW")
+   WORKFLOW=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint story field X-Y workflow)
+   WORKFLOW_TYPE=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow type "$WORKFLOW")
    ```
 
 2. **Spawn `sm-setup MODE=setup`** with:
@@ -167,7 +167,7 @@ Present to user:
    ```
 
 4. **Route based on workflow type:**
-   - **Phased workflow** → Run exit protocol: `pf handoff complete-phase` then `pf handoff marker`
+   - **Phased workflow** → Run exit protocol: `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff complete-phase` then `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker`
    - **Stepped workflow** → Tell user to run `/pf-workflow start {workflow}` (no handoff)
 </session-new-flow>
 
@@ -212,7 +212,7 @@ Before handoff, verify ALL of these:
 > **Triggered when:** `EMPTY_BACKLOG_STATE`
 
 1. Report: "Sprint backlog empty. All stories done or cancelled."
-2. Show future work: `pf sprint future`
+2. Show future work: `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint future`
 3. Offer: "Promote stories from `future.yaml`?" → `/pf-sprint promote {epic-id}`
 
 **Never suggest:** Closing sprint early, starting sprint planning. Sprints are fixed two-week periods.
@@ -262,10 +262,10 @@ SM does NOT hand off to agents. Instead, use `/pf-workflow start {name}` to begi
 
 Read `**Workflow:**` and `**Phase:**` from session. Query:
 ```bash
-OWNER=$(pf workflow phase-check {workflow} {phase})
+OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "sm":** Run `pf handoff marker $OWNER`, output result, tell user.
+**If OWNER != "sm":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
 
 **Note:** SM also handles `approved` status (finish phase).
 </phase-check>

package/pennyfarthing-dist/agents/tea.md

@@ -44,10 +44,10 @@ STORY_ID: "{STORY_ID}"
 
 Read `**Workflow:**` and `**Phase:**` from session. Query:
 ```bash
-OWNER=$(pf workflow phase-check {workflow} {phase})
+OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "tea":** Run `pf handoff marker $OWNER`, output result, tell user.
+**If OWNER != "tea":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
 </phase-check>
 
 <on-activation>

package/pennyfarthing-dist/agents/testing-runner.md

@@ -40,7 +40,7 @@ This runs lint + typecheck + tests. Exit 0 = all passed.
 ## Setup
 
 ```bash
-# Repo config available via: pf git status, or Python API:
+# Repo config available via: pf.sh git status, or Python API:
 # from pennyfarthing_scripts.git.repos import load_repos_config
 source .pennyfarthing/scripts/test/test-setup.sh
 

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

@@ -5,7 +5,7 @@ description: System Architect - Technical design and architecture
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "architect"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "architect"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -5,7 +5,7 @@ description: Business Analyst - Requirements discovery and stakeholder analysis
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "ba"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "ba"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -68,7 +68,7 @@ git status --short
 git -C pennyfarthing status --short 2>/dev/null
 
 # Or use the multi-repo status script:
-pf git status --brief
+pf.sh git status --brief
 ```
 
 Collect which repos have changes. If ALL repos are clean, abort with "No changes to commit."
@@ -191,7 +191,7 @@ cd {orchestrator_root}
 
 After all repos are processed:
 ```bash
-pf git status --brief
+pf.sh git status --brief
 ```
 
 All repos should show clean.

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

@@ -5,7 +5,7 @@ description: Developer - Feature implementation and coding
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "dev"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "dev"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -5,7 +5,7 @@ description: DevOps Engineer - Infrastructure and deployment automation
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "devops"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "devops"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -16,8 +16,8 @@ Manage epic lifecycle. Start an epic by moving it to the current sprint and gene
 Start an epic — move to current sprint and generate technical context.
 
 ```bash
-pf epic start 79
-pf epic start epic-79
+pf.sh epic start 79
+pf.sh epic start epic-79
 ```
 
 <workflow>
@@ -33,8 +33,8 @@ pf epic start epic-79
 Close an epic — verify completion, update status, and archive context.
 
 ```bash
-pf epic close 79
-pf epic close epic-79
+pf.sh epic close 79
+pf.sh epic close epic-79
 ```
 
 <workflow>
@@ -57,8 +57,8 @@ pf epic close epic-79
 ## CLI Equivalent
 
 ```bash
-pf epic start <epic-id>
-pf epic close <epic-id>
+pf.sh epic start <epic-id>
+pf.sh epic close <epic-id>
 ```
 
 ## Related

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

@@ -16,7 +16,7 @@ Manage git operations across all configured repos. Consolidates repository statu
 Check git status of all project repos.
 
 ```bash
-pf git status [--brief]
+pf.sh git status [--brief]
 ```
 
 Shows branch, uncommitted changes, and ahead/behind status for each configured repo.
@@ -25,18 +25,20 @@ Shows branch, uncommitted changes, and ahead/behind status for each configured r
 
 Organize uncommitted changes into proper commits and branches.
 
+**When this subcommand is invoked, immediately start the stepped workflow:**
+
 ```bash
-pf git cleanup
+pf.sh workflow start git-cleanup
 ```
 
-Starts the git-cleanup stepped workflow via BikeLane. Handles multiple repos.
+Then follow each step's instructions. Use `pf.sh workflow complete-step git-cleanup` to advance between steps. The workflow handles multi-repo analysis, change categorization, branch creation, commits, and push.
 
 ### `/pf-git branches <story-id>`
 
 Create feature branches in both repos from a story.
 
 ```bash
-pf git branches 86-3
+pf.sh git branches 86-3
 ```
 
 ### `/pf-git release`
@@ -44,7 +46,7 @@ pf git branches 86-3
 Interactive release with verification gates.
 
 ```bash
-pf git release
+pf.sh git release
 ```
 
 Starts the release stepped workflow — an 11-step process with gates at each stage.
@@ -60,13 +62,13 @@ Starts the release stepped workflow — an 11-step process with gates at each st
 
 ## CLI Equivalent
 
-All commands are also available via `pf git`:
+All commands are also available via `pf.sh git`:
 
 ```bash
-pf git status
-pf git cleanup
-pf git branches 86-3
-pf git release
+pf.sh git status
+pf.sh git cleanup
+pf.sh git branches 86-3
+pf.sh git release
 ```
 
 ## Related

package/pennyfarthing-dist/commands/pf-health-check.md

@@ -3,7 +3,7 @@ description: Check Pennyfarthing installation health and apply updates
 ---
 
 ```bash
-pf agent start "devops"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "devops"
 ```
 
 <agent-activation>

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

@@ -52,7 +52,7 @@ SM → TEA → Dev → Reviewer → SM (finish)
 
 Commands are organized by resource. Each group is accessible via both slash commands and CLI.
 
-### Sprint — `/pf-sprint` · `pf sprint`
+### Sprint — `/pf-sprint` · `pf.sh sprint`
 
 | Command | Description |
 |---------|-------------|
@@ -65,7 +65,7 @@ Commands are organized by resource. Each group is accessible via both slash comm
 | `/pf-sprint story [show\|add\|update\|size\|finish]` | Story operations |
 | `/pf-sprint epic [show\|add\|promote\|archive]` | Epic operations |
 
-### Git — `/pf-git` · `pf git`
+### Git — `/pf-git` · `pf.sh git`
 
 | Command | Description |
 |---------|-------------|
@@ -74,21 +74,21 @@ Commands are organized by resource. Each group is accessible via both slash comm
 | `/pf-git branches <id>` | Create feature branches from story |
 | `/pf-git release` | Interactive release workflow |
 
-### Session — `/pf-session` · `pf session`
+### Session — `/pf-session` · `pf.sh session`
 
 | Command | Description |
 |---------|-------------|
 | `/pf-session new` | Start next available story |
 | `/pf-session continue` | Resume from checkpoint |
 
-### Epic — `/pf-epic` · `pf epic`
+### Epic — `/pf-epic` · `pf.sh epic`
 
 | Command | Description |
 |---------|-------------|
 | `/pf-epic start <id>` | Start epic for development |
 | `/pf-epic close <id>` | Close completed epic |
 
-### Jira — `/pf-jira` · `pf jira`
+### Jira — `/pf-jira` · `pf.sh jira`
 
 | Command | Description |
 |---------|-------------|
@@ -98,7 +98,7 @@ Commands are organized by resource. Each group is accessible via both slash comm
 | `/pf-jira sync-epic` | Sync epic to Jira |
 | `/pf-jira reconcile` | Report mismatches |
 
-### Theme — `/pf-theme` · `pf theme`
+### Theme — `/pf-theme` · `pf.sh theme`
 
 | Command | Description |
 |---------|-------------|
@@ -108,7 +108,7 @@ Commands are organized by resource. Each group is accessible via both slash comm
 | `/pf-theme create <name>` | Create custom theme |
 | `/pf-theme maker` | Interactive theme wizard |
 
-### Workflow — `/pf-workflow` · `pf workflow`
+### Workflow — `/pf-workflow` · `pf.sh workflow`
 
 | Command | Description |
 |---------|-------------|
@@ -221,11 +221,11 @@ Based on your current state, here's what you might need:
 
 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
+pf.sh help           # Overview of all groups
+pf.sh help sprint    # Sprint commands
+pf.sh help git       # Git commands
+pf.sh help session   # Session commands
+pf.sh help epic      # Epic commands
 ```
 
 ## Documentation

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

@@ -5,7 +5,7 @@ description: Orchestrator - Coordinator of all agents and meta operations
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "orchestrator"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "orchestrator"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -5,7 +5,7 @@ description: Product Manager - Strategic planning and prioritization
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "pm"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "pm"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -4,7 +4,7 @@ description: Load essential project context at agent activation
 
 <purpose>
 Quickly load essential context files to reduce agent cold-start overhead.
-Automatically invoked on agent activation via `pf agent start`.
+Automatically invoked on agent activation via `pf.sh agent start`.
 </purpose>
 
 <when-to-use>
@@ -21,19 +21,19 @@ Use the `pf` CLI:
 
 ```bash
 # Load all essential context (default)
-pf agent start "sm"
+pf.sh agent start "sm"
 
 # Minimal mode - fastest startup
-pf agent start "sm" --minimal
+pf.sh agent start "sm" --minimal
 
 # Full mode - include domain docs
-pf agent start "sm" --full
+pf.sh agent start "sm" --full
 
 # Skip persona loading
-pf agent start "sm" --no-persona
+pf.sh agent start "sm" --no-persona
 
 # JSON output (for Cyclist integration)
-pf agent start "sm" --json
+pf.sh agent start "sm" --json
 ```
 
 ## Options
@@ -111,7 +111,7 @@ With `--quiet`, section headers are suppressed.
 The `/prime` command is automatically invoked when agents activate:
 
 1. User invokes `/sm`, `/tea`, `/dev`, or `/reviewer`
-2. `pf agent start <name>` runs
+2. `pf.sh agent start <name>` runs
 3. Context is loaded: workflow state, agent definition, persona, behavior guide, sprint context, session, sidecars
 4. Agent starts with full context AND their learned patterns loaded
 
@@ -129,7 +129,7 @@ If context becomes stale mid-session, run `/prime` manually:
 </integration>
 
 <reference>
-- **CLI:** `pf agent start <name>` or `python3 -m pennyfarthing_scripts.cli agent start <name>`
+- **CLI:** `pf.sh agent start <name>` or `python3 -m pennyfarthing_scripts.cli agent start <name>`
 - **Loads:** Workflow state, agent definition, persona, behavior guide, sprint context, session, sidecars
 - **Sidecar location:** `.pennyfarthing/sidecars/{agent}/*.md`
 - **Behavior guide:** `.pennyfarthing/guides/agent-behavior.md` (all agents)

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

@@ -5,7 +5,7 @@ description: Code Reviewer - Critical code review and quality enforcement
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "reviewer"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "reviewer"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -16,19 +16,19 @@ Manage work session lifecycle. Start new stories from the backlog or resume from
 Start the next available story from the sprint backlog.
 
 ```bash
-pf session new
+pf.sh session new
 ```
 
-Equivalent to `pf sprint work next`. Auto-selects the highest priority story.
+Equivalent to `pf.sh sprint work next`. Auto-selects the highest priority story.
 
 ### `/pf-session continue [--list] [--story-id ID]`
 
 Resume work from a saved checkpoint after context circuit breaker.
 
 ```bash
-pf session continue            # Interactive checkpoint selection
-pf session continue --list     # Show available checkpoints
-pf session continue --story-id MSSCI-12345  # Resume specific story
+pf.sh session continue            # Interactive checkpoint selection
+pf.sh session continue --list     # Show available checkpoints
+pf.sh session continue --story-id MSSCI-12345  # Resume specific story
 ```
 
 ## Quick Reference
@@ -41,8 +41,8 @@ pf session continue --story-id MSSCI-12345  # Resume specific story
 ## CLI Equivalent
 
 ```bash
-pf session new
-pf session continue [--list] [--story-id ID]
+pf.sh session new
+pf.sh session continue [--list] [--story-id ID]
 ```
 
 ## Related

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

@@ -5,7 +5,7 @@ description: Scrum Master - Story coordination and sprint management
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "sm"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "sm"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

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

@@ -20,7 +20,7 @@ Never manually edit `sprint/current-sprint.yaml`. Always use the provided script
 Show current sprint status with story counts and points.
 
 ```bash
-pf sprint status [filter]
+pf.sh sprint status [filter]
 ```
 
 | Filter | Description |
@@ -35,7 +35,7 @@ pf sprint status [filter]
 Show available stories ready for work, grouped by epic.
 
 ```bash
-pf sprint backlog
+pf.sh sprint backlog
 ```
 
 ### `/pf-sprint work [story-id|epic-id|next]`
@@ -59,7 +59,7 @@ if [[ "$OPEN_PRS" -gt 0 ]]; then
 fi
 
 # Check if story is available
-pf sprint check <story-id>
+pf.sh sprint check <story-id>
 
 # Then load SM to begin work
 ```
@@ -78,7 +78,7 @@ When starting work, this command:
 Archive a completed story.
 
 ```bash
-pf sprint archive <story-id> [pr-number] [--apply]
+pf.sh sprint archive <story-id> [pr-number] [--apply]
 ```
 
 | Option | Description |
@@ -90,7 +90,7 @@ pf sprint archive <story-id> [pr-number] [--apply]
 Initialize a new sprint.
 
 ```bash
-pf sprint new 2605 277 2026-02-03 2026-02-16 "Sprint goal"
+pf.sh sprint new 2605 277 2026-02-03 2026-02-16 "Sprint goal"
 ```
 
 ### `/pf-sprint future [--epic EPIC_ID]`
@@ -98,7 +98,7 @@ pf sprint new 2605 277 2026-02-03 2026-02-16 "Sprint goal"
 Show future work available for promotion.
 
 ```bash
-pf sprint future [--epic epic-XX]
+pf.sh sprint future [--epic epic-XX]
 ```
 
 ### `/pf-sprint promote <epic-id>`
@@ -106,7 +106,7 @@ pf sprint future [--epic epic-XX]
 Move an epic from future.yaml to current sprint.
 
 ```bash
-pf sprint epic promote epic-XX
+pf.sh sprint epic promote epic-XX
 ```
 
 ## Quick Reference

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

@@ -5,7 +5,7 @@ description: Test Engineer/Architect - Test strategy and TDD
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "tea"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "tea"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>

package/pennyfarthing-dist/commands/pf-tech-writer.md

@@ -5,7 +5,7 @@ description: Technical Writer - Documentation creation and maintenance
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-pf agent start "tech-writer"
+source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "tech-writer"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>