@pennyfarthing/core 10.0.5 → 10.2.0

package/pennyfarthing-dist/commands/theme.md

@@ -0,0 +1,95 @@
+---
+description: Manage persona themes - list, show, set, create, or interactive wizard
+args: "[list|show|set|create|maker] [options]"
+---
+
+# Theme Management
+
+<purpose>
+Manage persona themes: list available themes, view details, switch themes, create custom themes, and run the interactive AI-driven theme wizard.
+</purpose>
+
+## Commands
+
+### `/theme` or `/theme show [name]`
+
+Show current theme or specific theme details.
+
+```bash
+pf theme show [name]
+
+# Show extended details (OCEAN scores, quirks, catchphrases)
+pf theme show [name] --full
+```
+
+### `/theme list`
+
+List all available themes with current theme highlighted.
+
+```bash
+pf theme list
+```
+
+Output shows current theme marked with `*` and tier brackets: `[S]` elite, `[A]` excellent, `[B]` strong, `[C]` good, `[D]` below average, `[U]` unbenchmarked.
+
+### `/theme set <name>`
+
+Set the active persona theme.
+
+```bash
+pf theme set <name>
+```
+
+After setting, refresh the current agent's persona:
+```bash
+pf agent start "sm"
+```
+
+### `/theme create <name> [--base <theme>] [--user]`
+
+Create a new custom theme by copying from a base.
+
+```bash
+# Create from default base (minimalist)
+pf theme create my-theme
+
+# Create from specific base
+pf theme create my-theme --base blade-runner
+
+# Create as user-level theme (available across all projects)
+pf theme create my-theme --user
+```
+
+### `/theme maker`
+
+Interactive wizard for AI-driven theme creation. Supports three modes:
+
+| Mode | Description |
+|------|-------------|
+| AI-Driven | Describe a concept, AI generates all 10 agent personas |
+| Guided | AI suggests characters per agent, you pick |
+| Manual | You specify character, style, and quote for each agent |
+
+## Quick Reference
+
+| Command | Action |
+|---------|--------|
+| `/theme` | Show current theme |
+| `/theme list` | List all themes |
+| `/theme show blade-runner` | Show specific theme |
+| `/theme show blade-runner --full` | Extended details |
+| `/theme set discworld` | Switch to theme |
+| `/theme create my-theme` | Create from base |
+| `/theme maker` | Interactive wizard |
+
+## Related
+
+| Skill | Purpose |
+|-------|---------|
+| `/theme` | Full skill with maker wizard details |
+
+<reference>
+- **Skill:** `.claude/skills/theme/skill.md`
+- **CLI:** `pf theme [list|show|set|create]`
+- **Config:** `.pennyfarthing/config.local.yaml`
+</reference>

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

@@ -2,8 +2,16 @@
 description: UX Designer - User experience design and UI patterns
 ---
 
+<agent-activation>
+**FIRST:** Use Bash tool to run:
 ```bash
-d="$PWD"; while [[ ! -d "$d/.pennyfarthing" ]] && [[ "$d" != "/" ]]; do d="$(dirname "$d")"; done
-export PYTHONPATH="$(dirname "$(dirname "$(cd "$d/.pennyfarthing/scripts" && pwd -P)")"):${PYTHONPATH:-}"
-python3 -m pennyfarthing_scripts.cli agent start "ux-designer"
+pf agent start "ux-designer"
 ```
+This loads your persona and agent context. Adopt the character shown in the output.
+</agent-activation>
+
+<instructions>
+You are now the UX Designer agent. Follow your agent instructions from the activation output.
+
+The activation output begins with a `# Workflow State` section containing `state`, `story_id`, `phase`, `phase_owner`, and `backlog_count`. Act on this state per your agent definition.
+</instructions>

package/pennyfarthing-dist/commands/work.md

@@ -7,11 +7,9 @@ description: Resume work or start new - smart entry point that picks up where yo
 <agent-activation>
 **FIRST:** Use Bash tool to run:
 ```bash
-d="$PWD"; while [[ ! -d "$d/.pennyfarthing" ]] && [[ "$d" != "/" ]]; do d="$(dirname "$d")"; done
-export PYTHONPATH="$(dirname "$(dirname "$(cd "$d/.pennyfarthing/scripts" && pwd -P)")"):${PYTHONPATH:-}"
-python3 -m pennyfarthing_scripts.cli agent start "sm"
+pf agent start "sm"
 ```
-This loads your persona. Adopt the character shown in the output.
+This loads your persona and agent context. Adopt the character shown in the output.
 </agent-activation>
 
 <purpose>
@@ -21,5 +19,5 @@ Smart entry point for picking up work. Activates SM who handles all work coordin
 <instructions>
 You are now the SM agent. Follow your agent instructions from the activation output.
 
-Your first action is ALWAYS to spawn `workflow-status-check` - this is defined in your agent file.
+The activation output begins with a `# Workflow State` section containing `state`, `story_id`, `phase`, `phase_owner`, and `backlog_count`. Act on this state per your agent definition.
 </instructions>

package/pennyfarthing-dist/guides/agent-behavior.md

@@ -13,7 +13,7 @@
 <critical>
 **Story completion is MANDATORY.** A story is NOT done until:
 1. Reviewer approves and merges the PR
-2. SM runs `finish-story.sh` (archive session, update Jira, clean up)
+2. SM runs `pf sprint story finish` (archive session, update Jira, clean up)
 
 **Never** start new work while stories have open PRs. The merge gate blocks `/sprint work` if open PRs exist.
 
@@ -40,6 +40,61 @@
 
 ---
 
+<tandem-protocol>
+## Tandem Backseat Observer
+
+On activation, check session file for a `**Tandem:**` line (e.g., `**Tandem:** architect (file-watch)`).
+
+**If no `**Tandem:**` line in session:** Skip entirely — no-op.
+
+**If tandem is configured:**
+
+1. **Resolve backseat persona** from theme:
+   ```bash
+   THEME=$(yq '.theme' .pennyfarthing/config.local.yaml)
+   PARTNER_CHARACTER=$(yq ".agents.{PARTNER}.character" .pennyfarthing/personas/themes/${THEME}.yaml)
+   ```
+
+2. **Initialize observation file:**
+   Create `.session/{STORY_ID}-tandem-{PARTNER}.md` with header:
+   ```markdown
+   # Tandem Observations: {STORY_ID}
+   **Observer:** {PARTNER} ({PARTNER_CHARACTER})
+   **Phase:** {PHASE}
+   **Started:** {ISO_TIMESTAMP}
+
+   ---
+   ```
+
+3. **Spawn backseat** (Task tool):
+   ```yaml
+   subagent_type: "general-purpose"
+   model: "haiku"
+   run_in_background: true
+   prompt: |
+     Read .pennyfarthing/agents/tandem-backseat.md for your instructions.
+
+     PARTNER: "{PARTNER}"
+     CHARACTER: "{PARTNER_CHARACTER}"
+     STORY_ID: "{STORY_ID}"
+     SCOPE: "{SCOPE}"
+     OBSERVATION_FILE: ".session/{STORY_ID}-tandem-{PARTNER}.md"
+     SESSION_FILE: ".session/{STORY_ID}-session.md"
+   ```
+
+4. **During work:** PostToolUse hook automatically detects new observations
+   and injects them as `[Tandem] {CHARACTER}: {observation}`.
+   When you receive a tandem injection, surface it naturally:
+   *"{PARTNER_CHARACTER} suggests we extract this into an adapter."*
+
+5. **Before handoff:** Terminate the backseat background task, then proceed
+   with normal handoff sequence.
+
+See `.pennyfarthing/guides/tandem-protocol.md` for full protocol details.
+</tandem-protocol>
+
+---
+
 ## Reflector
 
 <critical>
@@ -61,16 +116,17 @@
 ## Exit Protocol
 
 1. Write assessment to session
-2. Spawn `handoff` subagent → returns `HANDOFF_RESULT: {status, next_agent}`
-3. If blocked → report error, stop
-4. Run `.pennyfarthing/scripts/core/handoff-marker.sh {next_agent}`
-5. Extract marker from YAML output, emit it:
+2. Terminate tandem backseat (if active)
+3. Spawn `handoff` subagent → returns `HANDOFF_RESULT: {status, next_agent}`
+4. If blocked → report error, stop
+5. Run `.pennyfarthing/scripts/core/handoff-marker.sh {next_agent}`
+6. Extract marker from YAML output, emit it:
    ```
    <!-- CYCLIST:HANDOFF:/dev -->
 
    Run `/dev` to continue
    ```
-6. EXIT (nothing after marker)
+7. EXIT (nothing after marker)
 </agent-exit-protocol>
 
 <wrong-phase-detection>

package/pennyfarthing-dist/guides/agent-coordination.md

@@ -22,7 +22,7 @@ Handoffs between agents are managed by Haiku subagents.
 ### 1. Single Source of Truth
 - **Agent definitions:** `.pennyfarthing/agents/`
 - **Subagent prompts:** `.pennyfarthing/agents/`
-- **Scope configuration:** `.pennyfarthing/guides/agent-scopes.yaml`
+- **Scope configuration:** `.pennyfarthing/project/docs/agent-scopes.yaml`
 - **Sprint tracking:** `sprint/current-sprint.yaml`
 - **Session state:** `.session/{STORY_ID}-session.md`
 
@@ -55,7 +55,7 @@ Support Agents
 
 ```
 /$CLAUDE_PROJECT_DIR/
-├── .claude/                              # Pennyfarthing coordination directory
+├── .pennyfarthing/                       # Pennyfarthing coordination directory (symlinks to node_modules)
 │   ├── agents/                         # Agent definitions (symlinks to pennyfarthing-dist)
 │   │   ├── orchestrator.md             # Master orchestrator
 │   │   ├── pm.md                       # Product Manager
@@ -68,17 +68,18 @@ Support Agents
 │   │   ├── ux-designer.md              # UX Designer
 │   │   └── devops.md                   # DevOps Engineer
 │   │
-│   ├── commands/                       # 42 slash commands (symlinks)
+│   ├── commands/                       # Slash commands (symlinks)
 │   ├── guides/                         # Behavior guides (symlinks)
-│   ├── skills/                         # 18+ knowledge domain skills (symlinks)
+│   ├── skills/                         # Knowledge domain skills (symlinks)
 │   ├── scripts/                        # Utility scripts (symlinks)
 │   │
 │   ├── project/                        # Project-specific overrides
 │   │   ├── agents/                     # Agent sidecars (patterns, gotchas, decisions)
 │   │   └── commands/                   # Custom project commands
 │   │
-│   ├── persona-config.yaml             # Project default theme (shared with team)
-│   └── CLAUDE.md                       # Project instructions
+│   ├── sidecars/                       # Agent learning files (local, writable)
+│   ├── config.local.yaml               # Theme, bell_mode, relay_mode, permission_mode
+│   └── persona-config.yaml             # Project default theme (shared with team)
 │
 ├── .session/                           # Active work sessions
 │   └── {story-id}-session.md           # Session files (one per story)
@@ -309,9 +310,6 @@ SM → TEA → Dev → Reviewer → SM
 | `testing-runner.md` | Run tests and report results | haiku |
 | **Reviewer Subagents** | | |
 | `reviewer-preflight.md` | Pre-flight checks before review | haiku |
-| **Utility Subagents** | | |
-| `workflow-status-check.md` | Check workflow status across repos | haiku |
-
 ### SM → TEA (Story Setup)
 **Trigger:** User selects story via `/new-work`
 **Subagent:** `sm-setup MODE=setup` then `sm-handoff`
@@ -440,10 +438,10 @@ Dev Agent Example (API story):
 ### Directory Structure
 ```
 .pennyfarthing/agents/             # Agent definitions (symlinked)
-.claude/commands/           # 42 slash commands
-.claude/skills/             # 18+ knowledge domain skills
-.session/                   # Session files
-sprint/                     # Sprint tracking
+.pennyfarthing/commands/           # Slash commands (symlinked)
+.pennyfarthing/skills/             # Knowledge domain skills (symlinked)
+.session/                          # Session files
+sprint/                            # Sprint tracking
 ```
 
 ### Commands Reference

package/pennyfarthing-dist/guides/agent-template-tactical.md

@@ -62,8 +62,7 @@ From theme config. Model: haiku. Tasks: {What helpers do for this agent}
 </skills>
 
 <context>
-**See:** `.pennyfarthing/guides/agent-behavior.md` for shared tactical agent behavior.
-**See:** `.pennyfarthing/guides/agent-behavior.md` for project info and git strategy.
+**See:** `.pennyfarthing/guides/agent-behavior.md` for shared tactical agent behavior, project info, and git strategy.
 </context>
 
 <reasoning-mode>
@@ -87,7 +86,7 @@ REFLECT: {what this means}
 </reasoning-mode>
 
 <on-activation>
-1. Run workflow status check (helper: `.pennyfarthing/agents/workflow-status-check.md`)
+1. Workflow state is provided in prime activation output (`# Workflow State` section)
 2. Read session file if active work exists
 3. Verify actual state matches session file
 4. Check if handed off to me (Phase field)

package/pennyfarthing-dist/guides/bikelane.md

@@ -11,7 +11,9 @@ Workflow orchestration engine. Coordinates multi-agent development through three
 | Workflow | Flow |
 |----------|------|
 | `tdd` | SM → TEA (RED) → Dev (GREEN) → Reviewer → SM |
+| `tdd-tandem` | SM → TEA+Architect (RED) → Dev+TEA (GREEN) → Reviewer+PM → SM |
 | `bdd` | SM → UX → TEA → Dev → Reviewer → SM |
+| `bdd-tandem` | SM → UX+Architect → TEA → Dev+UX (GREEN) → Reviewer+PM → SM |
 | `trivial` | SM → Dev → Reviewer → SM |
 | `agent-docs` | SM → Orchestrator → Tech Writer → SM |
 
@@ -27,7 +29,7 @@ One step loaded at a time. User approval at decision points. Supports tri-modal
 | `sprint-planning` | Sprint planning facilitation |
 | `epics-and-stories` | Epic and story breakdown |
 | `release` | Release workflow with verification gates |
-| `ux-design`, `quick-dev`, `quick-spec`, `product-brief`, `project-context`, `implementation-readiness` | Other stepped workflows |
+| `ux-design`, `quick-dev`, `product-brief`, `project-context`, `implementation-readiness` | Other stepped workflows |
 
 ### Procedural — Flexible agent-guided processes
 
@@ -37,7 +39,6 @@ No fixed step sequence. Checklist-based, agent discretion on order.
 |----------|---------|
 | `brainstorming` | Structured problem-solving (62 techniques) |
 | `code-review` | Code review checklists |
-| `dev-story` | Story development guidance |
 | `retrospective` | Sprint retrospective |
 
 ## State Tracking

package/pennyfarthing-dist/guides/command-tag-taxonomy.md

@@ -0,0 +1,212 @@
+# Command Tag Taxonomy Reference
+
+**Status:** 46 command files audited. Last updated: 2026-02-08
+
+---
+
+## Tag Inventory Table
+
+| Tag | Meaning | Usage | Files |
+|-----|---------|-------|-------|
+| `<purpose>` | What the command does and when to use it | Core rationale & quick summary | 23 |
+| `<usage>` | How to invoke the command with syntax & examples | Syntax guide | 13 |
+| `<on-invoke>` | Detailed step-by-step execution logic | Complex workflows (benchmarking, solo, checks) | 7 |
+| `<workflow>` | High-level workflow phases and process flow | Process documentation | 11 |
+| `<when-to-use>` | Situations where command applies | Decision guide | 11 |
+| `<reference>` | Links to related files, scripts, skills | Resource index | 11 |
+| `<instructions>` | Specific setup or execution steps | Agent-specific | 10 |
+| `<agent-activation>` | How to activate agent with CLI | Agent commands | 10 |
+| `<execution>` | Detailed execution with options and examples | Script-based commands | 3 |
+| `<related>` | Related commands to consider | Cross-reference | 6 |
+| `<prerequisites>` | Required setup or conditions | Prerequisite checklist | 2 |
+| `<critical>` | Non-negotiable rules or restrictions | Mandatory rules | 2 |
+| `<output-format>` | Expected output structure | Output specification | 4 |
+| `<critical-integrity-requirements>` | Data integrity constraints (benchmarking) | Specialized validation | 2 |
+| `<when-not-to-use>` | When NOT to use this command | Exclusion guidance | 1 |
+| `<variants>` | Command variants & differences | Variation guide | 1 |
+| `<key-differences>` | How this differs from similar commands | Comparison | 1 |
+| `<error-handling>` | Error cases and messages | Error reference | 1 |
+| `<integration>` | Integration with other systems | System integration | 2 |
+| `<quick-start>` | Quick start for new users | Onboarding | 1 |
+| `<commands>` | Subcommands available | Command reference | 1 |
+| `<themes>` | Theme selection reference | Theme documentation | 1 |
+| `<context-aware>` | Context-aware help based on state | Conditional help | 1 |
+| `<health-checks>` | Health check details and procedures | Diagnostic procedures | 1 |
+| `<auto-fixes>` | Auto-fix capabilities and warnings | Auto-remediation | 1 |
+| `<drift-detection>` | Behavior drift detection | Monitoring | 1 |
+| `<requirements>` | Required tools and installations | Tool requirements | 1 |
+| `<detection-order>` | Detection priority order | Detection logic | 1 |
+| `<agents>` | Agent reference table | Agent directory | 1 |
+| `<command>` | YAML frontmatter directive | Metadata | 1 |
+| `<architecture>` | High-level architecture diagram | System design | 1 |
+| `<parallel-work-flow>` | Parallel work setup flow | Worktree workflow | 1 |
+| `<agent-exit>` | Agent exit behavior | State management | 1 |
+| `<no-checkpoints>` | Handling missing checkpoints | Edge case | 1 |
+| `<checkpoint-labels>` | Checkpoint label patterns | Checkpoint reference | 1 |
+| `<stale-checkpoint-warning>` | Stale checkpoint warnings | Warning handling | 1 |
+| `<skip-check>` | Emergency skip behavior | Override handling | 1 |
+| `<description>` | YAML frontmatter description | Metadata | 1 |
+| `<workflow>` (YAML) | YAML frontmatter workflow reference | Metadata | 1 |
+| `<skills>` | Related skills | Skill reference | 1 |
+| `<commands>` (sub) | Available subcommands | Subcommand reference | 1 |
+
+---
+
+## Recommended Standard
+
+### Mandatory (Expected in all commands)
+
+- **`<purpose>`** — Essential for user understanding
+- **`<usage>`** — Essential for activation
+
+### Conditional by Type
+
+**Workflow/Agent Commands (e.g., /sm, /dev, /tea)**
+- `<agent-activation>` — Required to show activation
+- `<instructions>` — Required for agent behavior
+
+**Script-Based Commands (e.g., /check, /run-ci)**
+- `<execution>` — Required with options
+- `<reference>` — Links to scripts
+
+**Complex Multi-Step (e.g., /benchmark, /solo)**
+- `<on-invoke>` — Step-by-step breakdown
+- `<reference>` — Links to judge, finalize-run
+
+**Decision-Making Commands (e.g., /patch, /chore)**
+- `<when-to-use>` — When to pick this
+- `<when-not-to-use>` — When NOT to pick this
+- `<related>` — Alternatives to consider
+
+**Workflow/Phase Commands (e.g., /sprint, /release)**
+- `<workflow>` — Phase breakdown
+- `<commands>` or subcommand table — Available subcommands
+
+### Optional but Helpful
+
+- `<reference>` — Always include links to related files
+- `<related>` — Cross-reference similar commands
+- `<error-handling>` — For commands that can fail
+- `<output-format>` — For structured output commands
+
+---
+
+## Consistency Gaps
+
+### Missing `<purpose>` (Core)
+- (None - all files have purpose or instruction)
+
+### Missing `<usage>` Examples
+Files with no usage examples (mostly pure-markdown or markdown+comment style):
+- brainstorming.md (informal, no examples needed)
+- party-mode.md (informal)
+- create-branches-from-story.md
+- create-theme.md
+- list-themes.md
+- permissions.md
+- repo-status.md
+- retro.md
+- show-theme.md
+- start-epic.md
+- sync-epic-to-jira.md
+- sync-work-with-sprint.md
+- theme-maker.md
+- update-domain-docs.md
+- set-theme.md
+
+**ACTION:** Recommend adding `<usage>` with minimal examples to non-markdown commands.
+
+### Missing `<reference>` (Helpful)
+Files without resource links:
+- brainstorming.md
+- create-branches-from-story.md
+- create-theme.md
+- fix-blocker.md
+- git-cleanup.md
+- job-fair.md
+- list-themes.md
+- party-mode.md
+- permissions.md
+- repo-status.md
+- retro.md
+- show-theme.md
+- start-epic.md
+- sync-epic-to-jira.md
+- sync-work-with-sprint.md
+- theme-maker.md
+- update-domain-docs.md
+- set-theme.md
+- architect.md
+- dev.md
+- devops.md
+- orchestrator.md
+- pm.md
+- reviewer.md
+- sm.md
+- tea.md
+- tech-writer.md
+- ux-designer.md
+
+**ACTION:** Consider adding `<reference>` section to guide files and agent files linking to relevant skill/agent docs.
+
+### Agent Commands Lack Consistency
+Agent activation commands (architect, dev, devops, orchestrator, pm, reviewer, sm, tea, tech-writer, ux-designer, work):
+- Only have `<agent-activation>` + `<instructions>`
+- Missing: `<purpose>`, `<when-to-use>`, `<reference>`
+
+**ACTION:** Add fuller `<purpose>` and `<reference>` to agent commands.
+
+### Missing Tag Patterns by Category
+
+| Command Type | Gap |
+|--------------|-----|
+| **Theme Commands** (create, set, show, list, theme-maker) | Inconsistent use of `<usage>`. Only `theme-maker` uses XML tags extensively. |
+| **Sprint Commands** (sprint, start-epic, close-epic) | Some pure markdown, no `<usage>`. |
+| **Git Commands** (chore, patch, git-cleanup, standalone) | Good coverage, no gaps. |
+| **Config/Setup** (setup, health-check, permissions) | Needs `<usage>` examples. |
+
+---
+
+## Patterns & Recommendations
+
+### High-Quality Examples (Model These)
+
+**benchmark.md** — Comprehensive tag coverage
+- `<purpose>` + `<critical-integrity-requirements>` + `<usage>` + `<on-invoke>` (11 detailed steps) + `<error-handling>` + `<reference>`
+
+**solo.md** — Well-structured complex command
+- `<purpose>` + `<architecture>` + `<usage>` + `<on-invoke>` (10 detailed steps) + `<reference>`
+
+**patch.md** — Good decision guidance
+- `<purpose>` + `<when-to-use>` + `<when-not-to-use>` + `<usage>` + `<key-differences>` + `<workflow>` + `<related>`
+
+### Improvement Opportunities
+
+**Low-quality (Pure Markdown, No Structure)**
+- brainstorming.md — Use `<purpose>`, `<usage>`, `<workflow>` tags
+- retro.md — Use `<purpose>`, `<workflow>`, `<reference>` tags
+- party-mode.md — Add structure with tags
+- start-epic.md → Already has good content, just needs XML tags
+
+**Mixed Quality (Some Tags)**
+- help.md — Good breadth, but inconsistent sections
+- workflow.md — Minimal; needs expansion
+- permissions.md — Good CLI reference, needs `<usage>` tags
+
+---
+
+## Summary
+
+**Total Commands:** 46
+**Commands with Purpose Tag:** 23+ (50%+)
+**Commands with Usage Tag:** 13 (28%)
+**Commands with On-Invoke Detail:** 7 (15%)
+
+**Consistency Score:** ~60% — Good foundation, room for improvement in usage examples and cross-references.
+
+**Key Recommendation:** Standardize on:
+1. **All files** → `<purpose>` + `<usage>` (minimum viable)
+2. **Complex workflows** → Add `<on-invoke>` with numbered steps
+3. **All files** → Add `<reference>` with related file links
+4. **Decision commands** → Add `<related>` for alternatives
+5. **Convert pure Markdown** → Wrap sections in XML tags for consistency

package/pennyfarthing-dist/guides/hooks.md

@@ -16,7 +16,7 @@ Hooks are shell scripts that Claude Code runs at specific events:
 
 ### SessionStart: session-start.sh
 
-**Location:** `.claude/pennyfarthing/scripts/hooks/session-start.sh`
+**Location:** `.pennyfarthing/scripts/hooks/session-start.sh`
 
 Initializes the Pennyfarthing environment:
 - Creates `.session/` directory structure
@@ -25,7 +25,7 @@ Initializes the Pennyfarthing environment:
 
 ### SessionStart: setup-env.sh
 
-**Location:** `.claude/project/hooks/setup-env.sh`
+**Location:** `.pennyfarthing/project/hooks/setup-env.sh`
 
 Project-specific environment setup. Edit this file to:
 - Set custom environment variables
@@ -34,12 +34,12 @@ Project-specific environment setup. Edit this file to:
 
 ### PreToolUse: pre-edit-check.sh
 
-**Location:** `.claude/pennyfarthing/scripts/hooks/pre-edit-check.sh`
+**Location:** `.pennyfarthing/scripts/hooks/pre-edit-check.sh`
 
 Protects sensitive files from accidental edits:
 - Blocks: `.env`, `.pem`, `.key`, credentials, secrets
 - Blocks: `.git/`, `node_modules/`, `vendor/`
-- Blocks: `.claude/pennyfarthing/*` (managed files)
+- Blocks: `.pennyfarthing/*` (managed files)
 
 ## Configuration Schema
 
@@ -225,6 +225,6 @@ If a hook fails or behaves unexpectedly:
 
 | Type | Location | Editable |
 |------|----------|----------|
-| Managed hooks | `.claude/pennyfarthing/scripts/hooks/` | No (use pennyfarthing repo) |
+| Managed hooks | `.pennyfarthing/scripts/hooks/` | No (use pennyfarthing repo) |
 | Project hooks | `.claude/project/hooks/` | Yes |
 | Settings | `.claude/settings.local.json` | Yes |

package/pennyfarthing-dist/guides/patterns/fan-out-fan-in-pattern.md

@@ -240,7 +240,7 @@ After collecting results, merge them into a unified structure:
 ```yaml
 # Orchestrator spawns parallel status checks
 Task:
-  subagent_type: "workflow-status-check"
+  subagent_type: "Explore"
   description: "Check pennyfarthing status"
   prompt: |
     REPO: pennyfarthing
@@ -248,7 +248,7 @@ Task:
     Report git status, branch, and uncommitted changes.
 
 Task:
-  subagent_type: "workflow-status-check"
+  subagent_type: "Explore"
   description: "Check API status"
   prompt: |
     REPO: api
@@ -256,7 +256,7 @@ Task:
     Report git status, branch, and uncommitted changes.
 
 Task:
-  subagent_type: "workflow-status-check"
+  subagent_type: "Explore"
   description: "Check UI status"
   prompt: |
     REPO: ui