@pennyfarthing/core 9.2.0 → 9.3.0

package/pennyfarthing-dist/commands/repo-status.md

@@ -1,49 +0,0 @@
----
-description: Check git status of all project repos
----
-
-# Repository Status Check
-
-Check the git status of all project repos at once.
-
-## Configuration
-
-Repos are configured in `.claude/project/repos.yaml`. The script automatically reads this configuration.
-
-## Instructions
-
-Run this command to show the status of all repos:
-
-```bash
-$CLAUDE_PROJECT_DIR/scripts/git/git-status-all.sh
-```
-
-For a brief one-line-per-repo summary:
-
-```bash
-$CLAUDE_PROJECT_DIR/scripts/git/git-status-all.sh --brief
-```
-
-## What It Shows
-
-For each configured repo:
-- Current branch
-- Whether there are uncommitted changes
-- Whether the repo is ahead/behind origin
-- Unpushed commits (if any)
-
-## Adding More Repos
-
-To add repos, edit `.claude/project/repos.yaml`:
-
-```yaml
-repos:
-  my-api:
-    path: my-api        # relative to project root
-    type: api
-    language: go
-  my-ui:
-    path: my-ui
-    type: ui
-    language: typescript
-```

package/pennyfarthing-dist/commands/retro.md

@@ -1,200 +0,0 @@
----
-description: Facilitate a sprint retrospective
----
-
-# Retro - Sprint Retrospective
-
-You are facilitating a **sprint retrospective** to reflect on what happened, learn from it, and improve.
-
-## Pre-Retro: Load Context
-
-First, load the sprint data:
-```bash
-# Check sprint status
-cat sprint/current-sprint.yaml
-
-# Check completed work
-ls -la sprint/archive/
-
-# Check any session handoffs
-cat .session/{STORY_ID}-session.md 2>/dev/null || echo "No active work"
-```
-
-## Retro Format: 4 Ls
-
-### 1. Liked (What went well?)
-- What worked?
-- What should we keep doing?
-- What made us proud?
-
-### 2. Learned (What did we discover?)
-- New techniques or approaches
-- Things we didn't know before
-- Surprises (good or bad)
-
-### 3. Lacked (What was missing?)
-- Resources we needed
-- Information gaps
-- Tools or processes that would have helped
-
-### 4. Longed For (What do we wish we had?)
-- Improvements for next time
-- Things to try
-- Experiments to run
-
-## Output Template
-
-```markdown
-## Sprint [N] Retrospective
-**Date**: [Date]
-**Sprint Goal**: [Goal from sprint file]
-**Velocity**: [Planned] planned / [Completed] completed
-
-### Liked
-- [Thing that went well]
-- [Another positive]
-
-### Learned
-- [Discovery or insight]
-- [Technical learning]
-
-### Lacked
-- [Missing resource/info]
-- [Gap identified]
-
-### Longed For
-- [Improvement idea]
-- [Experiment to try]
-
-### Action Items
-| Action | Owner | Due |
-|--------|-------|-----|
-| [Specific action] | [Agent/Person] | [Next sprint] |
-
-### Metrics
-- Stories completed: X/Y
-- Bugs fixed: N
-- Tech debt addressed: [List]
-- Tests added: N
-```
-
-## Sidecar Maintenance
-
-Review and consolidate agent sidecars during retro:
-
-### 1. Review Sidecar Entries
-
-```bash
-echo "=== Sidecar Entries This Sprint ==="
-for agent in dev tea sm reviewer architect; do
-    SIDECAR=".claude/project/agents/${agent}-sidecar"
-    if [ -d "$SIDECAR" ]; then
-        echo "--- $agent ---"
-        for file in "$SIDECAR"/*.md; do
-            [ -f "$file" ] && grep -l "$(date +%Y)" "$file" 2>/dev/null && cat "$file"
-        done
-    fi
-done
-```
-
-### 2. Consolidate Learnings
-
-For each sidecar entry, ask:
-- **Still relevant?** Keep if yes, remove if no
-- **Needs updating?** Refine based on experience
-- **Promote to docs?** If it's general knowledge, move to project docs
-
-### 3. Prune Stale Entries
-
-Remove entries that:
-- Were one-time fixes
-- No longer apply (code changed)
-- Have been superseded by newer learnings
-
-### 4. Cross-Pollinate
-
-If Dev learned something TEA should know:
-- Add reference to TEA's sidecar
-- Or move to shared docs if both need it
-
-### Sidecar Health Check
-
-```bash
-echo "=== Sidecar Health ==="
-for agent in dev tea sm reviewer; do
-    SIDECAR=".claude/project/agents/${agent}-sidecar"
-    if [ -d "$SIDECAR" ]; then
-        ENTRIES=$(grep -c "^## " "$SIDECAR"/*.md 2>/dev/null | awk -F: '{sum+=$2} END {print sum}')
-        echo "$agent: $ENTRIES entries"
-    fi
-done
-```
-
-**Target:** 5-15 entries per agent. More = too noisy. Fewer = not capturing enough.
-
----
-
-## Session Artifact Cleanup
-
-During retro, clean up accumulated session artifacts from the sprint:
-
-### 1. Preview Cleanup
-
-```bash
-# See what would be cleaned (dry-run)
-$CLAUDE_PROJECT_DIR/scripts/misc/session-cleanup.sh --dry-run --aggressive
-```
-
-Review the output. Look for:
-- Files that should NOT be cleaned (active work artifacts)
-- Unexpectedly large number of files (indicates cleanup wasn't running properly)
-
-### 2. Execute Cleanup
-
-```bash
-# Run full cleanup with aggressive mode (archives completed epic contexts)
-$CLAUDE_PROJECT_DIR/scripts/misc/session-cleanup.sh --aggressive
-```
-
-This removes:
-- Old test result files (7+ days): `test-*.log`, `test-*.md`
-- Old TEA artifacts: `tea-*.md`, `*-red-*.md`, `*-green-*.md`
-- Completed handoff files: `*-handoff*.md`, `*-handoff*.txt`
-- Old lint logs: `lint-*.log`
-- Rotates `session-log.txt` to last 1000 lines
-- Archives epic contexts for completed epics
-
-### 3. Verify Clean State
-
-```bash
-# Check remaining files
-ls -la .session/
-
-# Should only see:
-# - .gitkeep
-# - session-log.txt (rotated)
-# - agents/ directory
-# - Any active work artifacts
-```
-
----
-
-## Follow-Up Actions
-
-After the retro:
-1. Update sprint/current-sprint.yaml with lessons learned
-2. Create stories for improvement actions
-3. Archive the retro in sprint/archive/
-4. Commit sidecar updates
-5. Verify session cleanup completed successfully
-
-## Usage
-
-```
-/retro                    # Run retro for current sprint
-/retro sprint-1          # Run retro for specific sprint
-```
-
----
-
-**TIME TO REFLECT. WHAT SPRINT ARE WE REVIEWING?**

package/pennyfarthing-dist/commands/reviewer.md

@@ -1,9 +0,0 @@
----
-description: Code Reviewer - Critical code review and quality enforcement
----
-
-```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 "reviewer"
-```

package/pennyfarthing-dist/commands/run-ci.md

@@ -1,116 +0,0 @@
----
-description: Detect and run CI locally
----
-
-<purpose>
-Run CI locally by detecting the project's CI system and executing the appropriate commands. Thin wrapper that delegates to project configuration.
-</purpose>
-
-<when-to-use>
-- Before pushing to verify CI will pass
-- To reproduce CI failures locally
-- To run the full CI pipeline without pushing
-- When you want to know what CI system the project uses
-</when-to-use>
-
-<execution>
-
-## Running CI Locally
-
-Use the run-ci.sh script:
-
-```bash
-# Run CI locally (auto-detects CI system)
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh
-
-# Show what CI system is detected without running
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --detect-only
-
-# Show what command would run without executing
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --dry-run
-
-# Show help
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --help
-```
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--help`, `-h` | Show help message |
-| `--detect-only` | Show detected CI system without running |
-| `--dry-run` | Show what would run without executing |
-
-</execution>
-
-<detection-order>
-
-## CI System Detection
-
-The script detects CI systems in this order:
-
-| Priority | System | Detection | Command |
-|----------|--------|-----------|---------|
-| 1 | Justfile | `just --list` shows `ci` recipe | `just ci` |
-| 2 | GitHub Actions | `.github/workflows/*.yml` exists | `act` |
-| 3 | GitLab CI | `.gitlab-ci.yml` exists | `gitlab-runner exec` |
-| 4 | npm fallback | `package.json` exists | `npm run build && npm test && npm run lint` |
-
-### Package Manager Detection
-
-For npm fallback, the script detects package manager:
-- `pnpm-lock.yaml` or `pnpm-workspace.yaml` → `pnpm`
-- `yarn.lock` → `yarn`
-- Otherwise → `npm`
-
-</detection-order>
-
-<output-format>
-
-## Output Examples
-
-### --detect-only
-```
-Detected CI system: github-actions
-Would run: act
-```
-
-### --dry-run
-```
-Detected: github-actions
-Would run: act
-```
-
-### Running CI
-```
-Running CI: github-actions
-Command: act
-
-[act output follows...]
-```
-
-Exit codes:
-- `0` - CI ran successfully
-- `1` - CI failed or no CI system detected
-
-</output-format>
-
-<requirements>
-
-## Tool Requirements
-
-| CI System | Required Tool | Installation |
-|-----------|--------------|--------------|
-| GitHub Actions | `act` | `brew install act` |
-| GitLab CI | `gitlab-runner` | See GitLab docs |
-| Justfile | `just` | `brew install just` |
-| npm fallback | `npm`/`pnpm`/`yarn` | Comes with Node.js |
-
-If a required tool is not installed, the script will show a warning.
-
-</requirements>
-
-<reference>
-- **Script:** `.pennyfarthing/scripts/run-ci.sh`
-- **Story:** 21-4 (Command & Skill Expansion)
-</reference>

package/pennyfarthing-dist/commands/set-theme.md

@@ -1,56 +0,0 @@
----
-description: Set the active persona theme
----
-
-# Set Theme
-
-Change the active persona theme for all agents.
-
-## Arguments
-
-- `<name>` - Theme name to activate (required)
-
-## Instructions
-
-1. If no theme name provided, list available themes:
-   ```bash
-   ls pennyfarthing-dist/personas/themes/*.yaml | xargs -I{} basename {} .yaml | sort
-   ```
-   Then ask the user which theme they want to use.
-
-2. Validate theme exists:
-   ```bash
-   ls pennyfarthing-dist/personas/themes/<name>.yaml
-   ```
-   If not found, show error and list available themes.
-
-3. Read the current config file to prepare for editing:
-   ```bash
-   cat .pennyfarthing/config.local.yaml 2>/dev/null || echo "FILE_NOT_FOUND"
-   ```
-
-4. Set the theme in `.pennyfarthing/config.local.yaml`:
-
-   **If the file exists and has a `theme:` line:**
-   - Use the Edit tool to replace `theme: <old>` with `theme: <new>`
-
-   **If the file doesn't exist or lacks the theme line:**
-   - Use the Write tool to create/overwrite the file:
-   ```yaml
-   # Pennyfarthing Local Configuration
-   # This file is gitignored - your personal preferences
-
-   theme: <name>
-   ```
-
-5. Verify the change was written:
-   ```bash
-   cat .pennyfarthing/config.local.yaml
-   ```
-   Confirm the theme line shows the new value.
-
-6. Refresh the current agent's persona to apply the new theme:
-   ```bash
-   python3 -m pennyfarthing_scripts.cli agent start "sm"
-   ```
-   This outputs the updated persona. **Adopt the new character immediately** - do not continue using the old persona.

package/pennyfarthing-dist/commands/setup.md

@@ -1,65 +0,0 @@
-# /setup - Interactive Project Setup
-
-<command>setup</command>
-
-<purpose>
-Launch the interactive project-setup workflow to configure a Pennyfarthing project. This workflow guides you through discovering repos, generating CLAUDE.md, configuring themes, and more.
-</purpose>
-
-<usage>
-```bash
-# Run after pennyfarthing init
-/setup
-
-# Skip certain steps
-/setup --skip-theme
-/setup --skip-cyclist
-```
-</usage>
-
-<workflow>
-The setup workflow guides you through:
-
-1. **Discovery** - Detect project structure and tech stack
-2. **Clone Repos** - Optionally clone subrepos for orchestrator pattern
-3. **repos.yaml** - Generate repository configuration
-4. **CLAUDE.md** - Create project instruction file
-5. **shared-context.md** - Populate with real project info
-6. **Task Runner** - Create justfile/Makefile
-7. **Theme** - Select persona theme
-8. **Cyclist** - Optionally install visual terminal
-9. **Validation** - Run doctor and confirm setup
-</workflow>
-
-<when-to-use>
-- After running `pennyfarthing init` 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`)
-- Should be in project root directory
-</prerequisites>
-
-<execution>
-This skill launches the `project-setup` stepped workflow.
-
-Load the workflow definition:
-```bash
-cat .pennyfarthing/workflows/project-setup/workflow.yaml
-```
-
-Then follow the stepped workflow, starting with:
-```bash
-cat .pennyfarthing/workflows/project-setup/steps/step-01-discover.md
-```
-</execution>
-
-<related>
-- `/sprint` - Sprint management after setup
-- `/theme` - Change themes after setup
-- `/workflow` - View available workflows
-- `pennyfarthing doctor` - Validate installation
-</related>

package/pennyfarthing-dist/commands/show-theme.md

@@ -1,21 +0,0 @@
----
-description: Show details of a theme including all agent personas
----
-
-# Show Theme
-
-Display full details of a theme including all agent character mappings.
-
-## Arguments
-
-- `[name]` - Theme name to show (optional, defaults to current theme)
-
-## Instructions
-
-Run the pennyfarthing CLI to show theme details:
-
-```bash
-pennyfarthing theme show [name]
-```
-
-Present the theme information clearly, showing each agent's character, style, and quote.

package/pennyfarthing-dist/commands/sm.md

@@ -1,9 +0,0 @@
----
-description: Scrum Master - Story coordination and sprint management
----
-
-```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"
-```