@pennyfarthing/core 11.4.0 → 12.0.0

package/packages/core/src/public/styles/tailwind.css

@@ -1615,6 +1615,13 @@
   border-radius: 2px;
 }
 
+.enhanced-sprint-panel .epic-ordinal {
+  font-size: 0.7rem;
+  font-family: var(--font-mono, 'SF Mono', Monaco, monospace);
+  color: var(--text-secondary, #8b8b8b);
+  flex-shrink: 0;
+}
+
 .enhanced-sprint-panel .epic-title {
   font-weight: 500;
   flex: 1;
@@ -1752,6 +1759,14 @@
   font-family: var(--font-mono, 'SF Mono', Monaco, monospace);
 }
 
+.enhanced-sprint-panel .story-item .story-ordinal {
+  font-size: 0.65rem;
+  font-family: var(--font-mono, 'SF Mono', Monaco, monospace);
+  color: var(--text-secondary, #8b8b8b);
+  flex-shrink: 0;
+  min-width: 3.5em;
+}
+
 .enhanced-sprint-panel .story-item .story-points {
   font-size: 0.65rem;
   color: var(--text-secondary, #8b8b8b);
@@ -2428,87 +2443,6 @@
   padding: 4px 0;
 }
 
-/* Background panel */
-.background-panel {
-  padding: 8px;
-}
-
-.background-panel .panel-header {
-  display: flex;
-  justify-content: space-between;
-  align-items: center;
-  margin-bottom: 8px;
-}
-
-.background-panel .task-counts {
-  font-size: 0.75rem;
-  color: var(--text-secondary, #8b8b8b);
-}
-
-.background-panel .pending-count {
-  color: var(--accent-color, #007acc);
-  margin-right: 8px;
-}
-
-.background-panel .clear-button {
-  padding: 2px 8px;
-  background: transparent;
-  border: 1px solid var(--border-color, #3c3c3c);
-  border-radius: 3px;
-  color: var(--text-secondary, #8b8b8b);
-  cursor: pointer;
-  font-size: 0.7rem;
-}
-
-.background-panel .task-item {
-  display: flex;
-  align-items: center;
-  gap: 8px;
-  padding: 6px 0;
-  border-bottom: 1px solid var(--border-color, #3c3c3c);
-}
-
-.background-panel .task-status {
-  width: 20px;
-  text-align: center;
-  font-size: 0.8rem;
-}
-
-.background-panel .task-pending .task-status {
-  color: var(--accent-color, #007acc);
-}
-
-.background-panel .task-completed .task-status {
-  color: var(--success-color, #4ec9b0);
-}
-
-.background-panel .task-error .task-status {
-  color: var(--error-color, #f14c4c);
-}
-
-.background-panel .task-content {
-  flex: 1;
-  min-width: 0;
-}
-
-.background-panel .task-description {
-  font-size: 0.8rem;
-  display: block;
-  overflow: hidden;
-  text-overflow: ellipsis;
-  white-space: nowrap;
-}
-
-.background-panel .task-type {
-  font-size: 0.7rem;
-  color: var(--text-secondary, #8b8b8b);
-}
-
-.background-panel .task-elapsed {
-  font-size: 0.7rem;
-  color: var(--text-secondary, #8b8b8b);
-}
-
 /* Diffs panel */
 .diffs-panel {
   padding: 8px;
@@ -2952,26 +2886,6 @@
   color: var(--text-secondary, #8b8b8b);
 }
 
-/* Switch (Radix) - explicit colors since Tailwind v4 data-[state] variants don't generate */
-.cyclist-switch {
-  background: var(--bg-tertiary, #2d2d2d);
-  border-color: var(--border-color, #3c3c3c);
-}
-
-.cyclist-switch[data-state="checked"] {
-  background: var(--accent, #4f46e5);
-  border-color: var(--accent, #4f46e5);
-}
-
-.cyclist-switch-thumb {
-  background: var(--text-primary, #e4e4e7);
-}
-
-/* ThemePalette in settings - ensure solid background for dropdown */
-.settings-panel .theme-palette-menu {
-  background: var(--bg-secondary, #252526);
-}
-
 /* Audit Log panel - Tufte-inspired: maximize data-ink, minimize chrome */
 .audit-log-panel {
   font-size: 0.8rem;

package/packages/core/src/public/utils/slash-commands.ts

@@ -164,10 +164,6 @@ export const SLASH_COMMANDS: SlashCommand[] = [
     "name": "/pf-patch",
     "description": "Interrupt-driven bug fix during active story work"
   },
-  {
-    "name": "/pf-permissions",
-    "description": "View and manage runtime permission grants - list, grant, revoke, or show details"
-  },
   {
     "name": "/pf-pm",
     "description": "Product Manager - Strategic planning and prioritization"

package/pennyfarthing-dist/agents/architect.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # Architect Agent - System Architect
 <role>
 System design, technical decisions, pattern definition, ADRs

package/pennyfarthing-dist/agents/ba.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # BA Agent - Business Analyst
 
 <role>

package/pennyfarthing-dist/agents/dev.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # Dev Agent - Developer
 <role>
 Feature implementation, making tests pass, code changes
@@ -89,10 +97,10 @@ STORY_ID: "{STORY_ID}"
 
 Read `**Workflow:**` and `**Phase:**` from session. Query:
 ```bash
-OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
+OWNER=$(pf workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "dev":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
+**If OWNER != "dev":** Run `pf handoff marker $OWNER`, output result, tell user.
 </phase-check>
 
 <on-activation>

package/pennyfarthing-dist/agents/devops.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # DevOps Agent - DevOps Engineer
 
 <role>

package/pennyfarthing-dist/agents/orchestrator.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # Orchestrator Agent - Meta Operations
 <role>
 Process improvement, agent coordination, workflow refinement, retrospectives

package/pennyfarthing-dist/agents/pm.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # PM Agent - Product Manager
 
 <role>

package/pennyfarthing-dist/agents/reviewer.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # Reviewer Agent - Adversarial Code Reviewer
 <role>
 Adversarial code review, quality gate enforcement, security and correctness analysis
@@ -46,10 +54,10 @@ PR_NUMBER: "{PR_NUMBER}"
 
 Read `**Workflow:**` and `**Phase:**` from session. Query:
 ```bash
-OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
+OWNER=$(pf workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "reviewer":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
+**If OWNER != "reviewer":** Run `pf handoff marker $OWNER`, output result, tell user.
 </phase-check>
 
 <on-activation>
@@ -125,13 +133,13 @@ OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-c
 <exit>
 ### If APPROVED:
 1. Write Reviewer Assessment (verdict: APPROVED)
-2. Update story: `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint story update {STORY_ID} --review-verdict approved`
+2. Update story: `pf sprint story update {STORY_ID} --review-verdict approved`
 3. Follow <agent-exit-protocol> (resolve-gate → complete-phase review→finish → marker sm)
 4. **DO NOT merge PRs** — SM handles PR creation and merge in the finish phase.
 
 ### If REJECTED:
 1. Write Reviewer Assessment (verdict: REJECTED, with severity table)
-2. Update story: `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint story update {STORY_ID} --review-verdict rejected --review-findings "summary of findings"`
+2. Update story: `pf sprint story update {STORY_ID} --review-verdict rejected --review-findings "summary of findings"`
 3. If findings are testable (logic bugs, missing edge cases):
    - Follow <agent-exit-protocol> (resolve-gate → complete-phase → marker tea)
 4. If findings are lint/format/dead-code only:

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

@@ -26,7 +26,7 @@ model: haiku
 
 - [ ] Use `/pf-sprint backlog` for initial backlog scan:
   ```bash
-  "$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint backlog
+  pf 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=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint epic field "$EPIC_NUM" jira)
+EPIC_JIRA=$(pf sprint epic field "$EPIC_NUM" jira)
 ```
 
-If missing or "null": auto-create via `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira create epic {EPIC_NUM}`
+If missing or "null": auto-create via `pf 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 the pf wrapper for Jira commands:
+Use pf for Jira commands:
 
 ```bash
 # Check availability first
-"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira check {JIRA_KEY}
+pf jira check {JIRA_KEY}
 
 # Then claim (assign to self + move to In Progress)
-"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh jira claim {JIRA_KEY}
+pf 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=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow type "{WORKFLOW}")
+WORKFLOW_TYPE=$(pf workflow type "{WORKFLOW}")
 ```
 
 | Workflow Type | Routing |

package/pennyfarthing-dist/agents/sm.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # SM Agent - Scrum Master
 <role>
 Story coordination, session management, workflow entry/exit
@@ -25,12 +33,12 @@ The moment you start reading implementation files or planning how code should wo
 </critical>
 
 <critical>
-Use the pf wrapper for all Jira interactions. Key commands:
+Use pf for all Jira interactions. Key commands:
 ```
-"$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
+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
 ```
 If they are broken, COMPLAIN LOUDLY
 </critical>
@@ -107,7 +115,7 @@ Prime script provides workflow state. Route based on state from activation outpu
 
 2. **Run finish command:**
    ```bash
-   "$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint story finish {STORY_ID}
+   pf sprint story finish {STORY_ID}
    ```
 
 3. **Commit results:**
@@ -153,8 +161,8 @@ Present to user:
 
 1. **Get workflow type:**
    ```bash
-   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")
+   WORKFLOW=$(pf sprint story field X-Y workflow)
+   WORKFLOW_TYPE=$(pf workflow type "$WORKFLOW")
    ```
 
 2. **Spawn `sm-setup MODE=setup`** with:
@@ -167,7 +175,7 @@ Present to user:
    ```
 
 4. **Route based on workflow type:**
-   - **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`
+   - **Phased workflow** → Run exit protocol: `pf handoff complete-phase` then `pf handoff marker`
    - **Stepped workflow** → Tell user to run `/pf-workflow start {workflow}` (no handoff)
 </session-new-flow>
 
@@ -199,7 +207,7 @@ Enforced by `gates/sm-setup-exit`: session exists, fields set, context exists, b
 > **Triggered when:** `EMPTY_BACKLOG_STATE`
 
 1. Report: "Sprint backlog empty. All stories done or cancelled."
-2. Show future work: `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh sprint future`
+2. Show future work: `pf 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.
@@ -249,10 +257,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=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
+OWNER=$(pf workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "sm":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
+**If OWNER != "sm":** Run `pf handoff marker $OWNER`, output result, tell user.
 
 **Note:** SM also handles `approved` status (finish phase).
 </phase-check>

package/pennyfarthing-dist/agents/tea.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # TEA Agent - Test Engineer/Architect
 <role>
 Test writing, TDD RED phase, acceptance criteria analysis
@@ -44,10 +52,10 @@ STORY_ID: "{STORY_ID}"
 
 Read `**Workflow:**` and `**Phase:**` from session. Query:
 ```bash
-OWNER=$("$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh workflow phase-check {workflow} {phase})
+OWNER=$(pf workflow phase-check {workflow} {phase})
 ```
 
-**If OWNER != "tea":** Run `"$CLAUDE_PROJECT_DIR"/.pennyfarthing/scripts/core/pf.sh handoff marker $OWNER`, output result, tell user.
+**If OWNER != "tea":** Run `pf handoff marker $OWNER`, output result, tell user.
 </phase-check>
 
 <on-activation>

package/pennyfarthing-dist/agents/tech-writer.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # Tech Writer Agent - Technical Writer
 <role>
 Documentation, API docs, user guides, README files

package/pennyfarthing-dist/agents/ux-designer.md

@@ -1,3 +1,11 @@
+---
+hooks:
+  PreToolUse:
+    - command: pf hooks schema-validation
+      matcher: Write
+  Stop:
+    - command: pf hooks reflector-check
+---
 # UX Designer Agent - UX Designer
 <role>
 UX design, wireframes, user flows, accessibility

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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "architect"
+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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "ba"
+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-dev.md

@@ -5,7 +5,7 @@ description: Developer - Feature implementation and coding
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "dev"
+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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "devops"
+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-health-check.md

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

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

@@ -11,6 +11,8 @@ Provides quick-start guidance for new users and context-aware suggestions based
 
 ## New to Pennyfarthing?
 
+Read the **[What Is Pennyfarthing?](../guides/what-is-pennyfarthing.md)** reference card for a 60-second overview.
+
 Start here:
 
 1. **`/pf-work`** - Smart entry point (resumes existing work or starts new)
@@ -21,7 +23,7 @@ Start here:
 
 If Pennyfarthing isn't installed yet:
 ```bash
-npx pennyfarthing init
+pf setup
 ```
 
 </quick-start>
@@ -147,7 +149,6 @@ Commands are organized by resource. Each group is accessible via both slash comm
 | `/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
 

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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "orchestrator"
+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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "pm"
+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-reviewer.md

@@ -5,7 +5,7 @@ description: Code Reviewer - Critical code review and quality enforcement
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "reviewer"
+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-setup.md

@@ -12,7 +12,7 @@ Launch the interactive project-setup workflow to configure a Pennyfarthing proje
 
 <usage>
 ```bash
-# Run after pennyfarthing init
+# Run after pf setup
 /setup
 
 # Skip certain steps
@@ -38,14 +38,14 @@ The setup workflow guides you through:
 </workflow>
 
 <when-to-use>
-- After running `pennyfarthing init` for the first time
+- After running `pf setup` for the first time
 - When setting up a new orchestrator with subrepos
 - When repos.yaml or CLAUDE.md don't exist
 - When converting an existing project to use Pennyfarthing
 </when-to-use>
 
 <prerequisites>
-- Pennyfarthing must be initialized (`pennyfarthing init`)
+- Pennyfarthing must be initialized (`pf setup`)
 - Should be in project root directory
 </prerequisites>
 
@@ -67,5 +67,5 @@ cat .pennyfarthing/workflows/project-setup/steps/step-01-discover.md
 - `/pf-sprint` - Sprint management after setup
 - `/theme set` - Change themes after setup
 - `/pf-workflow` - View available workflows
-- `pennyfarthing doctor` - Validate installation
+- `pf doctor` - Validate installation
 </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
-source .pennyfarthing/scripts/lib/env.sh && source "$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/lib/run-pf.sh" && run_pf agent start "sm"
+pf agent start "sm"
 ```
 This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>