npm - @pennyfarthing/core - Versions diffs - 7.4.1 → 7.5.0 - Mend

@pennyfarthing/core 7.4.1 → 7.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (890) hide show

package/pennyfarthing-dist/skills/sprint/skill.md DELETED Viewed

@@ -1,465 +0,0 @@
----
-name: sprint
-description: |
-  Sprint status, backlog, and story management for Pennyfarthing. Use when checking current
-  sprint status, finding available stories, reviewing backlog, or understanding story context
-  and history.
-  IMPORTANT: Always use the provided scripts - never manually edit sprint YAML.
-args: "[status|backlog|work|archive|new|promote]"
----
-# /sprint - Sprint Management
-<critical>
-Never manually edit `sprint/current-sprint.yaml`. Use the scripts below for deterministic, correct YAML formatting.
-</critical>
-## Commands
-### `/sprint` or `/sprint status [filter]`
-Show current sprint status with story counts and points.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/sprint-status.sh [filter]
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `filter` | No | Filter stories: `todo`, `in-progress`, `done`, `cancelled` |
-</args>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/sprint-status.sh           # All stories
-.pennyfarthing/scripts/core/run.sh sprint/sprint-status.sh todo      # Backlog only
-.pennyfarthing/scripts/core/run.sh sprint/sprint-status.sh in-progress  # WIP only
-.pennyfarthing/scripts/core/run.sh sprint/sprint-status.sh done      # Completed only
-</example>
-<output>
-Sprint metadata, stories by status (grouped under epic headers), points breakdown, completed count from archive.
-When filtered, only shows epics with matching stories.
-</output>
----
-### `/sprint backlog`
-Show available stories grouped by epic with Jira context.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/available-stories.sh
-</run>
-<output>
-Backlog stories with epic descriptions, points, priority, and workflow tags.
-</output>
----
-### `/sprint work [story-id|epic-id|next]`
-Start work on a story. This is the primary entry point for development work.
-<when>
-- Starting new development work
-- `/new-work` is an alias for this command
-</when>
-#### Without argument: Interactive selection
-Shows backlog, user selects story, then proceeds to setup.
-<output>
-1. Load SM persona
-2. Check for in-progress work
-3. Show available stories
-4. User selects story
-5. Setup and handoff to TEA/Dev
-</output>
-#### With story ID: Direct start
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh <story-id>
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `story-id` | Yes | Jira key (e.g., `MSSCI-12038`) |
-</args>
-<output>
-- `available: true` - Skip backlog, proceed to setup
-- `available: false` - Report why (assigned, in progress, etc.)
-</output>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh MSSCI-12038
-# Returns: {"type": "story", "available": true, "title": "...", ...}
-</example>
-#### With epic ID: Start first available story in epic
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh <epic-id>
-</run>
-<output>
-Epic info with `first_story` (highest priority available story).
-Action: Automatically start work on `first_story` if available.
-</output>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh MSSCI-11952
-# Returns: {"type": "epic", "first_story": {"id": "MSSCI-11954", ...}, ...}
-</example>
-#### With `next`: Auto-select highest priority story
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh next
-</run>
-<output>
-Highest-priority available story across all epics.
-Action: Automatically start work on returned story.
-</output>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/check-story.sh next
-# Returns: {"type": "next", "story": {"id": "MSSCI-11950", "priority": "P1", ...}}
-</example>
----
-### `/sprint archive <story-id> [pr-number] [--apply]`
-Archive a completed story to the sprint archive file.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/archive-story.sh <story-id> [pr-number] [--apply]
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `story-id` | Yes | Story ID (e.g., `35-2`) |
-| `pr-number` | No | PR number if merged via PR |
-| `--apply` | No | Also remove story from current-sprint.yaml |
-</args>
-<example>
-# Archive only (manual removal needed)
-.pennyfarthing/scripts/core/run.sh sprint/archive-story.sh 35-2 368
-# Archive and remove atomically (recommended)
-.pennyfarthing/scripts/core/run.sh sprint/archive-story.sh 35-2 368 --apply
-</example>
-<output>
-1. Extracts story from `current-sprint.yaml`
-2. Appends to `sprint/archive/sprint-{YYWW}-completed.yaml`
-3. With `--apply`: Also removes from current sprint
-4. Without `--apply`: Outputs command to complete removal
-</output>
----
-### `/sprint new <yyww> <jira-id> <start> <end> "<goal>"`
-Initialize a new sprint from template.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/new-sprint.sh <yyww> <jira-id> <start> <end> "<goal>"
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `yyww` | Yes | Sprint identifier (e.g., `2605` for 2026 week 5) |
-| `jira-id` | Yes | Jira sprint ID number (e.g., `277`) |
-| `start` | Yes | Start date `YYYY-MM-DD` |
-| `end` | Yes | End date `YYYY-MM-DD` |
-| `goal` | Yes | Sprint goal (quoted string) |
-</args>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/new-sprint.sh 2605 277 2026-02-03 2026-02-16 "Polish and stabilization"
-</example>
-<output>
-Creates:
-- `sprint/current-sprint.yaml` - New sprint file
-- `sprint/archive/sprint-{YYWW}-completed.yaml` - Empty archive
-Warning: Prompts for confirmation if current sprint is still active.
-</output>
----
-### `/sprint future [--epic EPIC_ID]`
-Show future work initiatives and epics available for promotion.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/list-future.sh [--epic EPIC_ID]
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `--epic` | No | Show detailed stories for a specific epic |
-</args>
-<output>
-Without `--epic`:
-- Initiatives grouped by status (READY, BLOCKED, planning)
-- Epics with points, priority, and status
-- Summary of total epics and points
-- Promotion instructions
-With `--epic`:
-- Full epic details including description
-- All stories with points and status
-- Promotion command for that epic
-</output>
-<example>
-# Show all future work
-.pennyfarthing/scripts/core/run.sh sprint/list-future.sh
-# Show details for specific epic
-.pennyfarthing/scripts/core/run.sh sprint/list-future.sh --epic epic-55
-</example>
----
-### `/sprint promote <epic-id>`
-Move an epic from `future.yaml` to `current-sprint.yaml`.
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/promote-epic.sh <epic-id>
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `epic-id` | Yes | Local epic ID (e.g., `epic-41`) |
-</args>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/promote-epic.sh epic-41
-</example>
-<output>
-1. Finds epic in `sprint/planning.yaml`
-2. Extracts epic metadata and all stories
-3. Appends to `sprint/current-sprint.yaml` epics section
-4. Outputs yq command to remove from planning.yaml
-</output>
-<when>
-Next steps after promote:
-- Review appended YAML in current-sprint.yaml
-- Create Jira epic: `/jira create epic <epic-id>`
-- Remove from planning.yaml if desired
-</when>
----
-## Read Operations
-These scripts read sprint YAML without modifying it. Use these instead of direct `yq` queries.
-### Get Story Field
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/get-story-field.sh <story-id> <field>
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `story-id` | Yes | Story ID (e.g., `35-2`) |
-| `field` | Yes | Field name to extract |
-</args>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/get-story-field.sh 35-2 workflow   # Returns: tdd
-.pennyfarthing/scripts/core/run.sh sprint/get-story-field.sh 35-2 jira       # Returns: MSSCI-12345
-.pennyfarthing/scripts/core/run.sh sprint/get-story-field.sh 35-2 status     # Returns: in_progress
-</example>
-<output>
-Field value or "null" if not found. Common fields: `workflow`, `status`, `jira`, `points`, `title`, `repos`, `priority`.
-</output>
----
-### Get Epic Field
-<run>
-.pennyfarthing/scripts/core/run.sh sprint/get-epic-field.sh <epic-id> <field>
-</run>
-<args>
-| Arg | Required | Description |
-|-----|----------|-------------|
-| `epic-id` | Yes | Epic ID (e.g., `epic-35` or just `35`) |
-| `field` | Yes | Field name to extract |
-</args>
-<example>
-.pennyfarthing/scripts/core/run.sh sprint/get-epic-field.sh epic-35 jira    # Returns: MSSCI-11234
-.pennyfarthing/scripts/core/run.sh sprint/get-epic-field.sh 35 title        # Returns: Epic title
-</example>
-<output>
-Field value or "null" if not found. Common fields: `jira`, `title`, `description`, `status`.
-</output>
----
-## Jira Operations
-For Jira-specific operations, use the `/jira` skill:
-| Task | Command |
-|------|---------|
-| Create epic in Jira | `/jira create epic <epic-id>` |
-| Sync epic to Jira | `/jira sync <epic-id>` |
-| Reconcile YAML vs Jira | `/jira reconcile` |
-| Claim a story | `/jira claim <issue-key>` |
-| View issue details | `/jira view <issue-key>` |
----
-## Work Flow Details
-<when>
-When `/sprint work` (or `/new-work`) starts a story:
-</when>
-<agent-activation>
-Load SM persona first:
-```bash
-d="$PWD"; while [[ ! -d "$d/.claude" ]] && [[ "$d" != "/" ]]; do d="$(dirname "$d")"; done; "$d/.pennyfarthing/scripts/core/run.sh" core/agent-session.sh start "sm"
-```
-</agent-activation>
-### Story Setup Steps
-<output>
-1. **Check story** via `check-story.sh` (if ID provided)
-2. **Write context** to `.session/context-story-{id}.md`
-3. **Setup story** via `generic-sm-setup` subagent (claims Jira, creates branch)
-4. **Handoff** to next agent based on workflow:
-| Workflow | Route |
-|----------|-------|
-| `trivial` | SM → Dev |
-| `tdd` | SM → TEA → Dev → Reviewer |
-| `agent-docs` | SM → Orchestrator |
-</output>
-### Gates Before Handoff
-<critical>
-All gates must pass before handoff:
-- [ ] Session file exists at `.session/{story-id}-session.md`
-- [ ] Story context written with ACs
-- [ ] Jira claimed (assigned, In Progress)
-- [ ] Branch created
-</critical>
----
-## File Locations
-| File | Purpose |
-|------|---------|
-| `sprint/current-sprint.yaml` | Active/backlog work only |
-| `sprint/archive/sprint-{YYWW}-completed.yaml` | Completed stories for sprint |
-| `sprint/sprint-template.yaml` | Format reference |
-## YAML Constraints
-| Field | Valid Values |
-|-------|-------------|
-| Sprint name | `"TO Sprint YYWW"` (e.g., "TO Sprint 2604") |
-| Story IDs | Jira keys `MSSCI-XXXXX` |
-| Status | `backlog`, `ready`, `in_progress`, `done` |
-| Workflow | `tdd`, `trivial`, `agent-docs`, `bdd` |
-| Priority | `P0`, `P1`, `P2`, `P3` |
-| in_sprint | `true`, `false` - Jira sprint membership |
-## Sprint Schema
-### Sprint-level fields
-| Field | Description |
-|-------|-------------|
-| `name` | Sprint name in "TO Sprint YYWW" format |
-| `jira_sprint_id` | Numeric Jira sprint ID (e.g., 276) |
-| `jira_sprint_name` | Jira sprint name (should match name) |
-| `goal` | Sprint goal/objective |
-| `start_date` | YYYY-MM-DD |
-| `end_date` | YYYY-MM-DD |
-| `status` | `active` or `closed` |
-### Story-level fields
-| Field | Description |
-|-------|-------------|
-| `in_sprint` | `true/false` - whether story is in Jira sprint (synced bidirectionally) |
-<output>
-The `in_sprint` field tracks Jira sprint membership:
-- `in_sprint: true` - Story is in the Jira sprint
-- `in_sprint: false` - Story is not in Jira sprint (backlog)
-- Field omitted - Sprint membership not explicitly tracked
-</output>
-## Dependencies
-<run>
-brew install yq
-</run>
-<when>
-For Jira integration, see `/jira` skill prerequisites.
-</when>
-## Quick Reference
-| Command | Script/Action |
-|---------|---------------|
-| `/sprint` | `sprint-status.sh` |
-| `/sprint status` | `sprint-status.sh` |
-| `/sprint status todo` | `sprint-status.sh todo` |
-| `/sprint status in-progress` | `sprint-status.sh in-progress` |
-| `/sprint status done` | `sprint-status.sh done` |
-| `/sprint backlog` | `available-stories.sh` |
-| `/sprint work` | Interactive story selection → SM flow |
-| `/sprint work MSSCI-XXX` | `check-story.sh` → direct start |
-| `/sprint work EPIC-ID` | `check-story.sh` → start first story |
-| `/sprint work next` | `check-story.sh next` → start highest priority |
-| `/sprint archive MSSCI-XXX` | `archive-story.sh MSSCI-XXX` |
-| `/sprint new 2605 277 ...` | `new-sprint.sh 2605 277 ...` |
-| `/sprint future` | `list-future.sh` |
-| `/sprint future --epic X` | `list-future.sh --epic X` |
-| `/sprint promote epic-41` | `promote-epic.sh epic-41` |
-| `/new-work` | Alias for `/sprint work` |
-| `/new-work MSSCI-XXX` | Alias for `/sprint work MSSCI-XXX` |
-| `/new-work next` | Alias for `/sprint work next` |
-## Related Skills
-| Skill | Purpose |
-|-------|---------|
-| `/jira` | Jira operations (create, sync, reconcile, claim) |
-| `/story` | Story creation, sizing, finish workflow |

package/pennyfarthing-dist/skills/story/scripts/create-story.sh DELETED Viewed

@@ -1,159 +0,0 @@
-#!/usr/bin/env bash
-# create-story.sh - Generate a story YAML block for adding to sprint
-# Usage: create-story.sh <epic-id> <title> <points> [options]
-#   --type bug|feature|refactor|chore  Story type (default: feature)
-#   --workflow <name>                  Workflow override (auto-determined if not set)
-#   --priority P0|P1|P2|P3             Priority (default: P2)
-#   --repos <name>                     Repos affected
-#   --jira                             Also show Jira create command
-set -euo pipefail
-# Defaults
-TYPE="feature"
-WORKFLOW=""
-PRIORITY="P2"
-REPOS=""
-CREATE_JIRA=false
-# Parse args
-EPIC_ID=""
-TITLE=""
-POINTS=""
-while [[ $# -gt 0 ]]; do
-    case "$1" in
-        --type)
-            TYPE="$2"
-            shift 2
-            ;;
-        --workflow)
-            WORKFLOW="$2"
-            shift 2
-            ;;
-        --priority)
-            PRIORITY="$2"
-            shift 2
-            ;;
-        --repos)
-            REPOS="$2"
-            shift 2
-            ;;
-        --jira)
-            CREATE_JIRA=true
-            shift
-            ;;
-        *)
-            if [[ -z "$EPIC_ID" ]]; then
-                EPIC_ID="$1"
-            elif [[ -z "$TITLE" ]]; then
-                TITLE="$1"
-            elif [[ -z "$POINTS" ]]; then
-                POINTS="$1"
-            fi
-            shift
-            ;;
-    esac
-done
-# Validate required args
-if [[ -z "$EPIC_ID" ]] || [[ -z "$TITLE" ]] || [[ -z "$POINTS" ]]; then
-    cat << 'EOF'
-Usage: create-story.sh <epic-id> "<title>" <points> [options]
-Arguments:
-  epic-id    Parent epic (e.g., PROJ-1234)
-  title      Story title (quoted)
-  points     Story points (1, 2, 3, 5, 8)
-Options:
-  --type bug|feature|refactor|chore  Story type (default: feature)
-  --workflow <name>                  Override auto-workflow
-  --priority P0|P1|P2|P3             Priority (default: P2)
-  --repos <name>                     Affected repos
-  --jira                             Also show Jira create command
-Examples:
-  create-story.sh PROJ-1234 "Add error handling" 3
-  create-story.sh PROJ-1234 "Fix typo" 1 --type chore
-  create-story.sh PROJ-1234 "New feature" 5 --jira
-EOF
-    exit 1
-fi
-# Auto-determine workflow if not set
-if [[ -z "$WORKFLOW" ]]; then
-    case "$POINTS" in
-        1|2)
-            if [[ "$TYPE" == "chore" ]] || [[ "$TYPE" == "bug" ]]; then
-                WORKFLOW="trivial"
-            else
-                WORKFLOW="tdd"
-            fi
-            ;;
-        *)
-            WORKFLOW="tdd"
-            ;;
-    esac
-fi
-# Generate story ID placeholder
-STORY_ID="PROJ-XXXXX"
-# Output YAML block
-echo "# Add this to sprint/current-sprint.yaml under epic $EPIC_ID:"
-echo ""
-echo "      - id: $STORY_ID"
-echo "        title: \"$TITLE\""
-echo "        points: $POINTS"
-echo "        priority: $PRIORITY"
-echo "        status: backlog"
-if [[ -n "$REPOS" ]]; then
-    echo "        repos: $REPOS"
-fi
-echo "        workflow: $WORKFLOW"
-# Add type-specific fields
-case "$TYPE" in
-    bug)
-        cat << 'EOF'
-        acceptance_criteria:
-          - Bug no longer occurs
-          - Regression test added
-          - Related code audited for same issue
-EOF
-        ;;
-    feature)
-        cat << 'EOF'
-        acceptance_criteria:
-          - Feature works as specified
-          - Tests cover happy path and edge cases
-          - Error handling implemented
-EOF
-        ;;
-    refactor)
-        cat << 'EOF'
-        acceptance_criteria:
-          - All existing tests pass
-          - No behavior changes
-          - Code follows new pattern
-EOF
-        ;;
-    chore)
-        cat << 'EOF'
-        acceptance_criteria:
-          - Task completed
-          - No regressions introduced
-EOF
-        ;;
-esac
-echo ""
-echo "---"
-echo "Type: $TYPE | Workflow: $WORKFLOW | Points: $POINTS"
-if [[ "$CREATE_JIRA" == "true" ]]; then
-    echo ""
-    echo "To create in Jira:"
-    echo "  jira issue create -t Story -s \"$TITLE\" -P <PROJECT> --parent $EPIC_ID --custom story-points=$POINTS"
-fi