@pennyfarthing/core 9.2.0 → 9.4.0

package/pennyfarthing-dist/skills/skill-registry.yaml

@@ -1,393 +0,0 @@
-# Pennyfarthing Skill Registry
-# Central metadata for all built-in skills
-# Schema: skill-registry.schema.json
-
-version: "1.0.0"
-
-skills:
-  agentic-patterns:
-    name: agentic-patterns
-    description: Core reasoning patterns for building effective LLM agents
-    category: ai-llm
-    tags: [reasoning, patterns, agents, llm]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Designing agent behavior
-        invocation: /agentic-patterns
-      - context: Debugging agent failures
-        invocation: /agentic-patterns troubleshooting
-    anti_patterns:
-      - Don't apply patterns mechanically without understanding context
-    related_skills: [context-engineering]
-    keywords: [react, reflection, planning, tool-use, chain-of-thought]
-    allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
-
-  changelog:
-    name: changelog
-    description: Maintain changelogs following Keep a Changelog format with conventional commits
-    category: documentation
-    tags: [changelog, releases, versioning]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Creating release notes
-        invocation: /changelog
-      - context: Auto-generating from commits
-        invocation: /changelog generate
-    anti_patterns:
-      - Don't manually edit CHANGELOG.md entries after generation
-    related_skills: []
-    keywords: [keepachangelog, conventional-commits, semver, release-notes]
-
-  code-review:
-    name: code-review
-    description: Code review checklists and patterns for quality assurance
-    category: development
-    tags: [review, quality, checklist]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Self-review before commit
-        invocation: /code-review
-      - context: Reviewing a PR
-        invocation: /code-review pr-checklist
-    anti_patterns:
-      - Don't skip security considerations in review
-      - Don't approve without running tests
-    related_skills: [testing, dev-patterns]
-    keywords: [pr, pull-request, quality, linting, security]
-
-  context-engineering:
-    name: context-engineering
-    description: Strategies for managing context windows in long-running agent sessions
-    category: ai-llm
-    tags: [context, optimization, agents]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Approaching context limits
-        invocation: /context-engineering
-      - context: Designing subagent prompts
-        invocation: /context-engineering subagent-design
-    anti_patterns:
-      - Don't load unnecessary context upfront
-      - Don't repeat large code blocks in prompts
-    related_skills: [agentic-patterns]
-    keywords: [context-window, tokens, summarization, lazy-loading]
-    allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
-
-  cyclist:
-    name: cyclist
-    description: Launch Cyclist visual terminal for Claude Code monitoring
-    category: tools
-    tags: [visual, monitoring, terminal]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Starting visual monitor
-        invocation: /cyclist
-      - context: Debugging sessions
-        invocation: /cyclist debug
-    anti_patterns:
-      - Don't run Cyclist in headless environments
-    related_skills: []
-    keywords: [tui, terminal, visualization, dashboard]
-
-  dev-patterns:
-    name: dev-patterns
-    description: Common development patterns, fixes, and gotchas
-    category: development
-    tags: [patterns, debugging, implementation]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Implementing features
-        invocation: /dev-patterns
-      - context: Avoiding known pitfalls
-        invocation: /dev-patterns gotchas
-    anti_patterns:
-      - Don't apply patterns from other frameworks blindly
-    related_skills: [code-review, testing]
-    keywords: [implementation, debugging, fixes, best-practices]
-    allowed_tools: [Read, Glob, Grep, Task]  # Reference material - read-only
-
-  finalize-run:
-    name: finalize-run
-    description: Validate and save benchmark run results - single exit point for all runs
-    category: benchmarking
-    tags: [benchmark, validation, results]
-    version: "1.0.0"
-    prerequisites: [judge]
-    examples:
-      - context: Completing a benchmark run
-        invocation: /finalize-run
-    anti_patterns:
-      - Never save results without passing through this skill
-    related_skills: [judge, persona-benchmark]
-    keywords: [benchmark, save, validate, guardrail]
-
-  jira:
-    name: jira
-    description: Jira CLI commands for sprint management
-    category: project-management
-    tags: [jira, issues, sprint]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Viewing sprint issues
-        invocation: /jira sprint
-      - context: Assigning issues
-        invocation: /jira assign ISSUE-123
-    anti_patterns:
-      - Don't bypass Jira for sprint tracking
-    related_skills: [sprint, story]
-    keywords: [atlassian, issues, tickets, backlog]
-
-  judge:
-    name: judge
-    description: Evaluate agent responses using standardized rubrics
-    category: benchmarking
-    tags: [evaluation, rubrics, scoring]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Evaluating agent response
-        invocation: /judge evaluate
-      - context: Running benchmark comparison
-        invocation: /judge compare
-    anti_patterns:
-      - Don't modify rubrics during a benchmark run
-    related_skills: [finalize-run, persona-benchmark]
-    keywords: [evaluation, scoring, metrics, grading]
-
-  just:
-    name: just
-    description: Run just recipes for project tasks like dev servers, tests, and databases
-    category: tools
-    tags: [tasks, runner, automation]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Starting dev servers
-        invocation: /just dev
-      - context: Running database tasks
-        invocation: /just db-reset
-    anti_patterns:
-      - Don't create complex recipes - keep them simple and composable
-    related_skills: [testing]
-    keywords: [justfile, make, tasks, automation, command-runner]
-
-  mermaid:
-    name: mermaid
-    description: Generate diagrams using Mermaid syntax for documentation
-    category: tools
-    tags: [diagrams, visualization, documentation]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Creating architecture diagrams
-        invocation: /mermaid architecture
-      - context: Sequence diagrams
-        invocation: /mermaid sequence
-    anti_patterns:
-      - Don't create overly complex diagrams - split into multiple if needed
-    related_skills: [changelog]
-    keywords: [flowchart, sequence, er-diagram, gantt, class-diagram]
-
-  otel:
-    name: otel
-    description: Claude Code OTEL telemetry format documentation for span interception and enrichment
-    category: tools
-    tags: [telemetry, monitoring, otel]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Working with OTEL spans
-        invocation: /otel
-      - context: Enriching tool telemetry in Cyclist
-        invocation: /otel enrichment
-    anti_patterns:
-      - Don't assume fields exist - verify against this documentation
-    related_skills: [cyclist]
-    keywords: [opentelemetry, spans, traces, enrichment, correlation]
-
-  permissions:
-    name: permissions
-    description: Manage runtime permission grants - list, grant, and revoke tool access
-    category: project-management
-    tags: [permissions, security, tools]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Viewing active grants
-        invocation: /permissions
-      - context: Granting WebFetch access
-        invocation: /permissions grant WebFetch "*.github.com"
-      - context: Revoking tool access
-        invocation: /permissions revoke Bash
-    anti_patterns:
-      - Don't manually edit settings.local.json permissions - use skill
-      - Don't grant overly broad scope patterns
-    related_skills: []
-    keywords: [grants, scopes, tools, runtime, security]
-
-  persona-benchmark:
-    name: persona-benchmark
-    description: Run benchmarks to compare persona effectiveness
-    category: benchmarking
-    tags: [benchmark, personas, comparison]
-    version: "1.0.0"
-    prerequisites: [judge]
-    examples:
-      - context: Testing persona on code review
-        invocation: /persona-benchmark cr-001 discworld
-      - context: Testing tech writer persona
-        invocation: /persona-benchmark tw-001 literary-classics
-    anti_patterns:
-      - Don't compare results across different rubric versions
-    related_skills: [judge, finalize-run, theme]
-    keywords: [benchmark, comparison, personas, testing]
-
-  sprint:
-    name: sprint
-    description: Sprint status, backlog, and story management for Pennyfarthing
-    category: project-management
-    tags: [sprint, status, backlog]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Checking sprint status
-        invocation: /sprint
-      - context: Finding available stories
-        invocation: /sprint backlog
-    anti_patterns:
-      - Don't manually edit sprint YAML - use scripts
-    related_skills: [story, jira]
-    keywords: [sprint, backlog, velocity, kanban]
-    allowed_tools: [Read, Glob, Grep, Bash, Task]
-
-  systematic-debugging:
-    name: systematic-debugging
-    description: Systematic debugging approach for isolating and fixing issues
-    category: development
-    tags: [debugging, troubleshooting, root-cause]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Debugging test failures
-        invocation: /systematic-debugging
-      - context: Investigating regressions
-        invocation: /systematic-debugging bisect
-    anti_patterns:
-      - Don't jump to solutions without reproducing the issue first
-      - Don't fix symptoms instead of root causes
-    related_skills: [testing, dev-patterns, agentic-patterns]
-    keywords: [debugging, bisect, reproduce, isolate, root-cause, regression]
-
-  story:
-    name: story
-    description: Story creation, sizing, and templates for Pennyfarthing workflow
-    category: project-management
-    tags: [stories, sizing, workflow]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Creating new stories
-        invocation: /story create
-      - context: Sizing stories
-        invocation: /story size
-    anti_patterns:
-      - Don't create stories without acceptance criteria
-    related_skills: [sprint, jira]
-    keywords: [user-stories, estimation, points, acceptance-criteria]
-
-  testing:
-    name: testing
-    description: Test commands and TDD workflow patterns
-    category: development
-    tags: [tdd, testing, quality]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Running project tests
-        invocation: /testing
-      - context: Debugging test failures
-        invocation: /testing troubleshoot
-    anti_patterns:
-      - Don't run tests directly - use testing-runner subagent
-      - Don't skip RED phase in TDD workflow
-    related_skills: [dev-patterns, code-review]
-    keywords: [jest, vitest, pytest, unit-test, integration, tdd, red-green]
-
-  theme:
-    name: theme
-    description: Manage persona themes - list, show, and set active theme
-    category: theming
-    tags: [personas, themes, customization]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Listing available themes
-        invocation: /list-themes
-      - context: Showing current theme
-        invocation: /show-theme
-      - context: Setting active theme
-        invocation: /set-theme discworld
-    anti_patterns:
-      - Don't edit config.local.yaml directly - use skill
-    related_skills: [theme-creation]
-    keywords: [personas, characters, discworld, literary-classics]
-
-  theme-creation:
-    name: theme-creation
-    description: Create custom persona themes with AI-driven generation
-    category: theming
-    tags: [personas, themes, creation]
-    version: "1.0.0"
-    prerequisites: [theme]
-    examples:
-      - context: Creating new theme
-        invocation: /theme-maker
-      - context: Interactive theme wizard
-        invocation: /create-theme
-    anti_patterns:
-      - Don't create incomplete themes missing required agents
-    related_skills: [theme]
-    keywords: [personas, custom, generation, wizard]
-
-  workflow:
-    name: workflow
-    description: Manage workflows - list, show, set, start, resume, and check status
-    category: project-management
-    tags: [workflow, phases, tdd]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Listing available workflows
-        invocation: /workflow
-      - context: Showing current workflow
-        invocation: /workflow show
-      - context: Starting stepped workflow
-        invocation: /workflow start architecture
-    anti_patterns:
-      - Don't switch workflows mid-story unless requirements fundamentally changed
-    related_skills: [sprint, story]
-    keywords: [tdd, trivial, agent-docs, bdd, architecture, bikelane, stepped, phased]
-
-  yq:
-    name: yq
-    description: YAML processor for reading, modifying, and querying YAML files
-    category: tools
-    tags: [yaml, processing, cli]
-    version: "1.0.0"
-    prerequisites: []
-    examples:
-      - context: Reading YAML values
-        invocation: /yq read
-      - context: Modifying YAML files
-        invocation: /yq modify
-    anti_patterns:
-      - Don't use complex expressions without testing first
-    related_skills: [just]
-    keywords: [yaml, jq, parsing, query, mikefarah]

package/pennyfarthing-dist/skills/sprint/scripts/archive-story.sh

@@ -1,101 +0,0 @@
-#!/bin/bash
-# Archive a completed story from current-sprint.yaml to the sprint archive
-# Usage: .pennyfarthing/scripts/sprint/archive-story.sh <story-id> [pr-number]
-#
-# Example: .pennyfarthing/scripts/sprint/archive-story.sh MSSCI-11945 368
-
-set -euo pipefail
-
-STORY_ID="${1:-}"
-PR_NUMBER="${2:-}"
-
-if [[ -z "$STORY_ID" ]]; then
-  echo "Usage: archive-story.sh <story-id> [pr-number]"
-  echo "Example: archive-story.sh MSSCI-11945 368"
-  exit 1
-fi
-
-# PROJECT_ROOT should be set by find-root.sh, but find it if not
-if [[ -z "${PROJECT_ROOT:-}" ]]; then
-  d="$PWD"
-  while [[ ! -d "$d/.claude" ]] && [[ "$d" != "/" ]]; do
-    d="$(dirname "$d")"
-  done
-  PROJECT_ROOT="$d"
-fi
-
-SPRINT_FILE="$PROJECT_ROOT/sprint/current-sprint.yaml"
-
-if [[ ! -f "$SPRINT_FILE" ]]; then
-  echo "Error: Sprint file not found at $SPRINT_FILE"
-  exit 1
-fi
-
-# Extract sprint name to determine archive file
-SPRINT_NAME=$(grep -E "^\s+name:" "$SPRINT_FILE" | head -1 | sed 's/.*"TO Sprint \([0-9]*\)".*/\1/')
-if [[ -z "$SPRINT_NAME" ]]; then
-  echo "Error: Could not extract sprint name from $SPRINT_FILE"
-  exit 1
-fi
-
-ARCHIVE_FILE="$PROJECT_ROOT/sprint/archive/sprint-${SPRINT_NAME}-completed.yaml"
-
-# Check if archive file exists
-if [[ ! -f "$ARCHIVE_FILE" ]]; then
-  echo "Error: Archive file not found at $ARCHIVE_FILE"
-  echo "Create it first with new-sprint.sh or manually"
-  exit 1
-fi
-
-# Use yq to extract story data
-if ! command -v yq &> /dev/null; then
-  echo "Error: yq is required but not installed"
-  echo "Install with: brew install yq"
-  exit 1
-fi
-
-# Find the story in current sprint
-STORY_DATA=$(yq eval ".epics[].stories[] | select(.id == \"$STORY_ID\")" "$SPRINT_FILE")
-
-if [[ -z "$STORY_DATA" ]]; then
-  echo "Error: Story $STORY_ID not found in $SPRINT_FILE"
-  exit 1
-fi
-
-# Extract story fields
-TITLE=$(echo "$STORY_DATA" | yq eval '.title' -)
-POINTS=$(echo "$STORY_DATA" | yq eval '.points' -)
-EPIC_ID=$(yq eval ".epics[] | select(.stories[].id == \"$STORY_ID\") | .id" "$SPRINT_FILE" | head -1)
-
-# Get today's date
-COMPLETED_DATE=$(date +%Y-%m-%d)
-
-# Build the archive entry
-echo ""
-echo "Archiving story:"
-echo "  ID: $STORY_ID"
-echo "  Title: $TITLE"
-echo "  Points: $POINTS"
-echo "  Epic: $EPIC_ID"
-echo "  Completed: $COMPLETED_DATE"
-[[ -n "$PR_NUMBER" ]] && echo "  PR: $PR_NUMBER"
-echo ""
-
-# Append to archive file
-{
-  echo "  - id: $STORY_ID"
-  echo "    epic: $EPIC_ID"
-  echo "    title: \"$TITLE\""
-  echo "    points: $POINTS"
-  echo "    completed: $COMPLETED_DATE"
-  [[ -n "$PR_NUMBER" ]] && echo "    pr: $PR_NUMBER"
-} >> "$ARCHIVE_FILE"
-
-echo "Added to $ARCHIVE_FILE"
-
-# Remove from current sprint
-echo ""
-echo "Now remove the story from $SPRINT_FILE"
-echo "Use: yq eval -i 'del(.epics[].stories[] | select(.id == \"$STORY_ID\"))' $SPRINT_FILE"
-echo ""
-echo "If the epic has no more stories, also remove the epic section."

package/pennyfarthing-dist/skills/sprint/scripts/available-stories.sh

@@ -1,97 +0,0 @@
-#!/bin/bash
-# Display available stories grouped by epic with Jira context
-# Usage: .pennyfarthing/scripts/sprint/available-stories.sh
-#
-# Shows backlog stories with epic context, points, and workflow
-
-set -euo pipefail
-
-# PROJECT_ROOT should be set by find-root.sh, but find it if not
-if [[ -z "${PROJECT_ROOT:-}" ]]; then
-  d="$PWD"
-  while [[ ! -d "$d/.claude" ]] && [[ "$d" != "/" ]]; do
-    d="$(dirname "$d")"
-  done
-  PROJECT_ROOT="$d"
-fi
-
-SPRINT_FILE="$PROJECT_ROOT/sprint/current-sprint.yaml"
-
-if [[ ! -f "$SPRINT_FILE" ]]; then
-  echo "Error: Sprint file not found at $SPRINT_FILE"
-  exit 1
-fi
-
-if ! command -v yq &> /dev/null; then
-  echo "Error: yq is required but not installed"
-  echo "Install with: brew install yq"
-  exit 1
-fi
-
-if ! command -v jira &> /dev/null; then
-  echo "Error: jira CLI is required but not installed"
-  echo "Install with: brew install ankitpokhrel/jira/jira"
-  exit 1
-fi
-
-# Extract sprint info
-SPRINT_NAME=$(yq '.sprint.name' "$SPRINT_FILE")
-echo "# Available Stories - $SPRINT_NAME"
-echo ""
-
-# Get all epic IDs from the sprint file
-EPIC_IDS=$(yq '.epics[].id' "$SPRINT_FILE" | tr '\n' ' ')
-
-# Batch fetch epic details from Jira
-echo "Fetching epic details from Jira..."
-echo ""
-
-# Process each epic
-for EPIC_ID in $EPIC_IDS; do
-  # Get epic title from sprint YAML (faster than Jira for display)
-  EPIC_TITLE=$(yq ".epics[] | select(.id == \"$EPIC_ID\") | .title" "$SPRINT_FILE")
-
-  # Get stories for this epic that are available (backlog or ready)
-  STORY_COUNT=$(yq ".epics[] | select(.id == \"$EPIC_ID\") | .stories[] | select(.status == \"backlog\" or .status == \"ready\") | .id" "$SPRINT_FILE" 2>/dev/null | wc -l | tr -d ' ')
-
-  if [[ "$STORY_COUNT" -eq 0 ]]; then
-    continue
-  fi
-
-  # Fetch epic description from Jira for context (if it's a valid Jira key)
-  # Jira uses Atlassian Document Format - extract text content from paragraphs
-  EPIC_DESCRIPTION=""
-  if [[ "$EPIC_ID" =~ ^MSSCI-[0-9]+$ ]]; then
-    EPIC_DESCRIPTION=$(jira issue view "$EPIC_ID" --raw 2>/dev/null | \
-      jq -r '.fields.description.content[]? | select(.type == "paragraph") | .content[]? | select(.type == "text") | .text' 2>/dev/null | \
-      head -3 | tr '\n' ' ' | cut -c1-200)
-  fi
-
-  echo "## $EPIC_TITLE"
-  if [[ -n "$EPIC_DESCRIPTION" ]]; then
-    echo "*$EPIC_DESCRIPTION*"
-  fi
-  echo ""
-  echo "| ID | Title | Pts | Pri | Status | Workflow |"
-  echo "|----|-------|-----|-----|--------|----------|"
-
-  # Get available stories for this epic (backlog or ready)
-  yq -o=json ".epics[] | select(.id == \"$EPIC_ID\") | .stories[] | select(.status == \"backlog\" or .status == \"ready\")" "$SPRINT_FILE" 2>/dev/null | \
-    jq -r '[.id, .title, (.points | tostring), (.priority // "P2"), (.status // "backlog"), (.workflow // "tdd")] | @tsv' | \
-    while IFS=$'\t' read -r story_id story_title story_points story_priority story_status story_workflow; do
-      # Truncate title if too long
-      if [[ ${#story_title} -gt 40 ]]; then
-        story_title="${story_title:0:37}..."
-      fi
-      echo "| $story_id | $story_title | $story_points | $story_priority | $story_status | $story_workflow |"
-    done
-
-  echo ""
-done
-
-# Summary
-TOTAL_BACKLOG=$(yq '[.epics[].stories[] | select(.status == "backlog" or .status == "ready")] | length' "$SPRINT_FILE")
-TOTAL_POINTS=$(yq '.epics[].stories[] | select(.status == "backlog" or .status == "ready") | .points' "$SPRINT_FILE" | paste -sd+ - | bc 2>/dev/null || echo "0")
-
-echo "---"
-echo "**Total available:** $TOTAL_BACKLOG stories, $TOTAL_POINTS points"