@pennyfarthing/core 7.0.2 → 7.4.1

package/pennyfarthing-dist/scripts/prime.sh

@@ -1,161 +0,0 @@
-#!/usr/bin/env zsh
-# prime.sh - Load essential project context at agent activation
-# Usage: prime.sh [--minimal] [--full] [--quiet] [--agent <name>]
-#
-# Loads context in priority order:
-# 1. CLAUDE.md (project + user)
-# 2. Sprint summary (current-sprint.yaml key fields)
-# 3. Active session (.session/*-session.md)
-# 4. Agent sidecar (if --agent provided)
-# 5. Shared context (project info - all agents)
-# 6. Shared agent behavior (protocols - all agents)
-# 7. Tactical guide (for sm, tea, dev, reviewer)
-# 8. Domain docs (--full only)
-
-set -euo pipefail
-
-# Find project root
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-source "$SCRIPT_DIR/utils/find-root.sh"
-
-# Defaults
-QUIET=false
-MINIMAL=false
-FULL=false
-AGENT_NAME=""
-
-# Parse arguments
-while [[ $# -gt 0 ]]; do
-    case $1 in
-        --quiet) QUIET=true; shift ;;
-        --minimal) MINIMAL=true; shift ;;
-        --full) FULL=true; shift ;;
-        --agent) AGENT_NAME="$2"; shift 2 ;;
-        -h|--help)
-            echo "Usage: prime.sh [--minimal] [--full] [--quiet] [--agent <name>]"
-            echo "  --minimal      Load only CLAUDE.md files (fastest)"
-            echo "  --full         Include domain docs from .claude/project/"
-            echo "  --quiet        Suppress section headers"
-            echo "  --agent <name> Load agent's sidecar patterns"
-            exit 0
-            ;;
-        *) shift ;;
-    esac
-done
-
-# Helper to print headers (respects --quiet)
-print_header() {
-    if [[ "$QUIET" != "true" ]]; then
-        echo ""
-        echo "# $1"
-    fi
-}
-
-# 1. Project CLAUDE.md (always loaded first)
-if [[ -f "$PROJECT_ROOT/CLAUDE.md" ]]; then
-    print_header "CLAUDE.md"
-    cat "$PROJECT_ROOT/CLAUDE.md"
-fi
-
-# 2. User CLAUDE.md (if exists)
-if [[ -f "$HOME/.claude/CLAUDE.md" ]]; then
-    print_header "~/.claude/CLAUDE.md"
-    cat "$HOME/.claude/CLAUDE.md"
-fi
-
-# Stop here for minimal mode
-if [[ "$MINIMAL" == "true" ]]; then
-    exit 0
-fi
-
-# 3. Sprint summary (extract key info only, not full notes)
-if [[ -f "$PROJECT_ROOT/sprint/current-sprint.yaml" ]]; then
-    print_header "Sprint Context"
-
-    # Extract sprint number and goal
-    sprint_num=$(yq '.sprint.number // ""' "$PROJECT_ROOT/sprint/current-sprint.yaml" 2>/dev/null)
-    sprint_goal=$(yq '.sprint.goal // ""' "$PROJECT_ROOT/sprint/current-sprint.yaml" 2>/dev/null)
-    if [[ -n "$sprint_num" && "$sprint_num" != "null" ]]; then
-        echo "Sprint ${sprint_num}: ${sprint_goal}"
-    fi
-
-    # Extract progress
-    completed=$(yq '.summary.completed_points // 0' "$PROJECT_ROOT/sprint/current-sprint.yaml" 2>/dev/null)
-    total=$(yq '.summary.total_points // 0' "$PROJECT_ROOT/sprint/current-sprint.yaml" 2>/dev/null)
-    if [[ -n "$completed" && -n "$total" ]]; then
-        echo "Progress: ${completed}/${total} points"
-    fi
-fi
-
-# 4. Active session (if exists) - first 50 lines only
-SESSION_FILE=""
-if [[ -d "$PROJECT_ROOT/.session" ]]; then
-    # Find a session file (typically only one active at a time)
-    SESSION_FILE=$(find "$PROJECT_ROOT/.session" -maxdepth 1 -name "*-session.md" -type f 2>/dev/null | head -1)
-fi
-
-if [[ -n "$SESSION_FILE" && -f "$SESSION_FILE" ]]; then
-    print_header "Active Session: $(basename "$SESSION_FILE")"
-    head -50 "$SESSION_FILE"
-
-    # Indicate if truncated
-    total_lines=$(wc -l < "$SESSION_FILE" | tr -d ' ')
-    if [[ "$total_lines" -gt 50 ]]; then
-        echo ""
-        echo "... (truncated, ${total_lines} total lines)"
-    fi
-fi
-
-# 5. Agent sidecar (if --agent provided)
-if [[ -n "$AGENT_NAME" ]]; then
-    SIDECAR_DIR="$PROJECT_ROOT/.pennyfarthing/sidecars/${AGENT_NAME}"
-    if [[ -d "$SIDECAR_DIR" ]]; then
-        for pattern_file in "$SIDECAR_DIR"/*.md; do
-            if [[ -f "$pattern_file" ]]; then
-                print_header "Agent Sidecar: $(basename "$pattern_file")"
-                cat "$pattern_file"
-            fi
-        done
-    fi
-fi
-
-# 6. Shared context (project info - all agents get this)
-if [[ -n "$AGENT_NAME" ]]; then
-    SHARED_CONTEXT="$PROJECT_ROOT/.pennyfarthing/guides/shared-context.md"
-    if [[ -f "$SHARED_CONTEXT" ]]; then
-        print_header "Shared Context"
-        cat "$SHARED_CONTEXT"
-    fi
-fi
-
-# 7. Shared agent behavior (protocols - all agents get this)
-if [[ -n "$AGENT_NAME" ]]; then
-    SHARED_GUIDE="$PROJECT_ROOT/.pennyfarthing/guides/shared-agent-behavior.md"
-    if [[ -f "$SHARED_GUIDE" ]]; then
-        print_header "Shared Agent Behavior"
-        cat "$SHARED_GUIDE"
-    fi
-fi
-
-# 8. Tactical guide (for tactical agents: sm, tea, dev, reviewer)
-if [[ -n "$AGENT_NAME" ]]; then
-    case "$AGENT_NAME" in
-        sm|tea|dev|reviewer)
-            TACTICAL_GUIDE="$PROJECT_ROOT/.pennyfarthing/guides/tactical-agent-behavior.md"
-            if [[ -f "$TACTICAL_GUIDE" ]]; then
-                print_header "Tactical Agent Behavior"
-                cat "$TACTICAL_GUIDE"
-            fi
-            ;;
-    esac
-fi
-
-# 9. Domain docs (--full only)
-if [[ "$FULL" == "true" ]]; then
-    for doc in "$PROJECT_ROOT/.claude/project"/CLAUDE-*.md; do
-        if [[ -f "$doc" ]]; then
-            print_header "$(basename "$doc")"
-            cat "$doc"
-        fi
-    done
-fi

package/pennyfarthing-dist/scripts/run.sh

@@ -1,65 +0,0 @@
-#!/usr/bin/env zsh
-# Bootstrap script - finds PROJECT_ROOT and runs the requested script
-# Usage: ./scripts/run.sh <script-name> [args...]
-#
-# This solves the absolute path problem by:
-# 1. Finding PROJECT_ROOT by looking for the .claude/ directory
-# 2. Exporting PROJECT_ROOT for the script to use
-# 3. Running the script with full absolute paths
-
-set -euo pipefail
-
-# Find PROJECT_ROOT by looking for .claude/ marker
-find_project_root() {
-    local dir="$PWD"
-    while [[ ! -d "$dir/.claude" ]] && [[ "$dir" != "/" ]]; do
-        dir="$(dirname "$dir")"
-    done
-    if [[ -d "$dir/.claude" ]]; then
-        echo "$dir"
-    else
-        echo "Error: Could not find project root (no .claude/ directory found)" >&2
-        exit 1
-    fi
-}
-
-PROJECT_ROOT="$(find_project_root)"
-export PROJECT_ROOT
-
-# Get the script to run
-if [[ $# -lt 1 ]]; then
-    echo "Usage: ./scripts/run.sh <script-name> [args...]" >&2
-    echo "Example: ./scripts/run.sh agent-session.sh start sm" >&2
-    exit 1
-fi
-
-SCRIPT_NAME="$1"
-shift
-
-# Handle different script locations
-# Priority 1: .claude/scripts (npm-installed or copy-mode symlink)
-# Priority 2: .pennyfarthing/scripts (dogfooding - pennyfarthing repo itself)
-if [[ -d "$PROJECT_ROOT/.claude/scripts" ]]; then
-    SCRIPTS_DIR="$PROJECT_ROOT/.claude/scripts"
-elif [[ -d "$PROJECT_ROOT/.pennyfarthing/scripts" ]]; then
-    SCRIPTS_DIR="$PROJECT_ROOT/.pennyfarthing/scripts"
-else
-    echo "Error: No scripts directory found" >&2
-    echo "Expected: .claude/scripts or .pennyfarthing/scripts" >&2
-    exit 1
-fi
-
-if [[ -f "$SCRIPTS_DIR/$SCRIPT_NAME" ]]; then
-    exec "$SCRIPTS_DIR/$SCRIPT_NAME" "$@"
-elif [[ -f "$SCRIPTS_DIR/utils/$SCRIPT_NAME" ]]; then
-    exec "$SCRIPTS_DIR/utils/$SCRIPT_NAME" "$@"
-elif [[ -f "$SCRIPTS_DIR/hooks/$SCRIPT_NAME" ]]; then
-    exec "$SCRIPTS_DIR/hooks/$SCRIPT_NAME" "$@"
-else
-    echo "Error: Script not found: $SCRIPT_NAME" >&2
-    echo "Looked in:" >&2
-    echo "  $SCRIPTS_DIR/$SCRIPT_NAME" >&2
-    echo "  $SCRIPTS_DIR/utils/$SCRIPT_NAME" >&2
-    echo "  $SCRIPTS_DIR/hooks/$SCRIPT_NAME" >&2
-    exit 1
-fi

package/pennyfarthing-dist/skills/sprint-context/SKILL.md

@@ -1,120 +0,0 @@
----
-name: sprint-context
-description: Sprint status, backlog, and story management for Conductor. Use when checking current sprint status, finding available stories, reviewing backlog, or understanding story context and history.
----
-
-# Sprint Context Skill - Conductor Project
-
-## When to Use This Skill
-
-- Checking current sprint status
-- Finding available stories in backlog
-- Understanding story context and history
-- Reviewing completed work
-- Sprint planning and retrospectives
-
-## Sprint File Locations
-
-| File | Purpose |
-|------|---------|
-| `sprint/current-sprint.yaml` | Active sprint with all stories |
-| `sprint/backlog.yaml` | Future epics and stories |
-| `sprint/completed.yaml` | Archived completed work |
-| `sprint/context/epic-*-summary.md` | Epic-level context summaries |
-| `sprint/context/story-*-summary.md` | Story-level context summaries |
-| `sprint/archive/*.md` | Archived session files |
-
-## Quick Reference
-
-### Check Sprint Status
-```bash
-cat sprint/current-sprint.yaml
-```
-
-### Find Available Stories
-```bash
-# Stories ready for work
-grep -B2 -A5 "status: backlog\|status: ready" sprint/current-sprint.yaml
-```
-
-### Check Story Context
-```bash
-# Epic context
-cat sprint/context/epic-{N}-summary.md
-
-# Story context
-cat sprint/context/story-{X-Y}-summary.md
-```
-
-### Find Related Work
-```bash
-# Search archive for related stories
-grep -r "keyword" sprint/archive/
-grep -r "keyword" sprint/context/
-```
-
-## Sprint YAML Structure
-
-```yaml
-sprint:
-  number: 38
-  goal: "Sprint goal description"
-  start_date: 2025-01-06
-  end_date: 2025-01-17
-
-epics:
-  - id: epic-32
-    title: "Epic Title"
-    stories:
-      - id: "32-1"
-        description: "Story title"
-        points: 3
-        priority: P1
-        status: done | in-progress | backlog | ready
-        repos: api | ui | both
-        jira: MSSCI-12345
-```
-
-## Story Status Values
-
-| Status | Meaning |
-|--------|---------|
-| `backlog` | Not started, available for work |
-| `ready` | Groomed, ready to start |
-| `in-progress` | Currently being worked |
-| `review` | PR created, awaiting review |
-| `approved` | Review passed, ready to finish |
-| `done` | Completed and archived |
-
-## Context File Patterns
-
-### Epic Summary (`sprint/context/epic-{N}-summary.md`)
-- What the epic accomplishes
-- Key technical decisions across stories
-- Patterns established
-- Remaining work
-
-### Story Summary (`sprint/context/story-{X-Y}-summary.md`)
-- What was built
-- Key technical decisions
-- Implementation patterns
-- Files modified
-- Lessons learned
-
-## Common Tasks
-
-### Starting New Work
-1. Check `sprint/current-sprint.yaml` for available stories
-2. Look for `status: backlog` or `status: ready`
-3. Check for epic context in `sprint/context/`
-4. Review related archived work if needed
-
-### Finishing Work
-1. Update story status in `sprint/current-sprint.yaml`
-2. Create story summary in `sprint/context/`
-3. Archive session file to `sprint/archive/`
-
-### Sprint Planning
-1. Review `sprint/backlog.yaml` for upcoming work
-2. Check `sprint/completed.yaml` for velocity reference
-3. Review epic summaries for context

package/pennyfarthing-dist/skills/story-management/SKILL.md

@@ -1,208 +0,0 @@
----
-name: story-management
-description: Story creation, sizing, and sprint management patterns for Conductor. Use when creating stories, estimating work, or managing the sprint workflow.
----
-
-# Story Management Skill - Conductor Project
-
-## Overview
-
-This skill covers story creation, sizing, and management patterns for the Conductor project sprint workflow.
-
-## Story Sizing Guidelines
-
-### 1-2 Points (Trivial)
-
-- Single file change
-- Config update
-- Simple bug fix
-- No new tests needed
-- **Skip TEA, go directly to Dev**
-- **Example:** Fix typo, update env variable
-
-### 3 Points (Small)
-
-- Few files changed
-- Single component/handler
-- Straightforward implementation
-- Some tests needed
-- **Example:** Add validation, fix authorization bug
-
-### 5 Points (Medium)
-
-- Multiple files across layers
-- New feature component
-- API + UI changes
-- Comprehensive tests
-- **Example:** New admin page, new API endpoint
-
-### 8 Points (Large)
-
-- Significant feature
-- Multiple components
-- Database changes
-- Cross-repo coordination
-- **Example:** New integration, major refactor
-
-### 13+ Points (Epic-level)
-
-- **SPLIT THIS STORY**
-- Too complex for single story
-- Multiple unknowns
-- Break into 3-5 smaller stories
-
-## Story Templates
-
-### Bug Fix Story
-
-```yaml
-35-N-short-description:
-  status: backlog
-  points: 2-3
-  repos: api|ui|both
-  priority: P0-P2
-  description: "[Symptom] - [Root cause if known]"
-  error_details:
-    symptom: "What user sees"
-    error: "Error message"
-    affected: "Pages/endpoints affected"
-  ac:
-    - "Bug no longer occurs"
-    - "Regression test added"
-    - "Related code audited for same issue"
-```
-
-### Feature Story
-
-```yaml
-35-N-short-description:
-  status: backlog
-  points: 5-8
-  repos: api|ui|both
-  priority: P1-P2
-  description: "User can [action] to [benefit]"
-  ac:
-    - "Feature works as specified"
-    - "UI matches design"
-    - "API documented"
-    - "Tests cover happy path and edge cases"
-    - "Error handling implemented"
-```
-
-### Refactor Story
-
-```yaml
-35-N-short-description:
-  status: backlog
-  points: 3-5
-  repos: api|ui
-  priority: P2
-  description: "Refactor [component] to [improvement]"
-  ac:
-    - "All existing tests pass"
-    - "No behavior changes"
-    - "Code follows new pattern"
-    - "Documentation updated"
-```
-
-## Acceptance Criteria Patterns
-
-### Good AC (SMART)
-
-- "Admin users can access /admin/settings without 403"
-- "API returns 204 No Content on successful DELETE"
-- "Selected client persists in URL query param"
-- "Tests cover admin, manager, analyst roles"
-
-### Bad AC (Vague)
-
-- "Feature works correctly"
-- "No bugs"
-- "Good performance"
-- "User-friendly"
-
-## Priority Guidelines
-
-| Priority | Meaning | SLA |
-|----------|---------|-----|
-| P0 | Production blocker | Same day |
-| P1 | High impact bug/feature | This sprint |
-| P2 | Normal priority | Next sprint OK |
-| P3 | Nice to have | Backlog |
-
-## Cross-Repo Patterns
-
-### API-First Pattern
-
-1. **Story A (API):** Implement backend endpoint
-2. **Story B (UI):** Implement frontend consuming endpoint
-
-### Full-Stack Pattern
-
-1. Single story with `repos: both`
-2. AC covers both API and UI
-3. TEA writes tests for both
-
-## Scale-Adaptive Workflow
-
-Based on story complexity, determine workflow depth:
-
-| Points | Scale | Workflow | Handoff |
-|--------|-------|----------|---------|
-| 1-2 | Trivial | Skip TEA for chores | SM -> Dev directly |
-| 3-5 | Standard | Full TDD flow | SM -> TEA -> Dev |
-| 8+ | Complex | Add Architect review | SM -> Architect -> TEA -> Dev |
-
-## Sprint File Locations
-
-| File | Purpose |
-|------|---------|
-| `sprint/current-sprint.yaml` | Active stories only |
-| `sprint/backlog.yaml` | Future epics/stories |
-| `sprint/completed.yaml` | Done work archive |
-| `sprint/archive/story-X-Y-*.md` | Detailed session archives |
-| `sprint/context/story-X-Y-summary.md` | Quick context summaries |
-
-## Story Key Format
-
-- **Conductor:** `epic-N`, `N-M` stories (e.g., `epic-35`, `35-4`)
-- **Siemulator:** `sim-epic-N`, `sim-N-M` stories (e.g., `sim-epic-10`, `sim-10-1`)
-
-## Lessons Learned
-
-### Authorization Stories
-
-- Always audit related endpoints for same issue
-- Add tests for admin, manager, analyst roles
-- Use centralized utility pattern
-
-### UI Stories
-
-- Check for client selector needs (multi-client users)
-- Verify route configuration
-- Add E2E test for navigation
-
-### Integration Stories
-
-- Plan for mock infrastructure
-- Consider retry/timeout handling
-- Document external dependencies
-
-## Workflow Commands
-
-| Command | Purpose |
-|---------|---------|
-| `/new-work` | Start a new story (SM -> TEA -> Dev) |
-| `/start-epic` | Generate epic technical context |
-
-**Note:** Session completion is handled via `/sm` (finish-story task). Agents auto-detect active work on activation.
-
-## Jira Integration
-
-```bash
-# Claim a story before starting
-./scripts/jira-claim-story.sh 35-4-checklist-configuration-ui --claim
-
-# Sync sprint to Jira
-./scripts/sync-epic-to-jira.sh 35 --with-comments
-```