@pennyfarthing/core 9.1.2 → 9.3.0

package/pennyfarthing-dist/agents/sm-file-summary.md

@@ -1,79 +0,0 @@
----
-name: sm-file-summary
-description: Read files and create condensed summaries for story context
-tools: Read, Glob, Grep
-model: haiku
----
-
-<critical>
-Read FULL file content, not just headers. Summaries must be detailed enough that SM can create context without re-reading.
-</critical>
-
-<arguments>
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `FILE_LIST` | Yes | Comma-separated file paths to summarize |
-</arguments>
-
-<info>
-**Turn efficiency:** Read multiple files in parallel.
-</info>
-
-<gate>
-## For Each File
-
-- [ ] Read entire file content
-- [ ] Create condensed summary (2-3 sentences)
-- [ ] Extract key exports
-- [ ] Identify patterns
-- [ ] Note dependencies
-- [ ] Provide line references
-</gate>
-
-<output>
-## Output Format
-
-Return a `FILE_SUMMARY_RESULT` block:
-
-### Success
-```
-FILE_SUMMARY_RESULT:
-  status: success
-  files_summarized: {N}
-  files:
-    - path: "{path}"
-      lines: {N}
-      summary: "{2-3 sentence description}"
-      pattern: "{Service|Component|Hook|etc.}"
-      key_exports:
-        - "{FunctionName(params) ReturnType}"
-      dependencies:
-        internal: ["{import}"]
-        external: ["{package}"]
-      lines_of_interest:
-        - range: "L{start}-L{end}"
-          description: "{why interesting}"
-      relevance: "{why this file matters to story}"
-
-  next_steps:
-    - "File summaries complete. Use this context to write story context file."
-    - "Key files for implementation: {list top 3 by relevance}"
-```
-
-### Partial (some files not found)
-```
-FILE_SUMMARY_RESULT:
-  status: warning
-  files_summarized: {N}
-  files_missing: {N}
-  missing:
-    - path: "{path}"
-      suggestion: "{check path or ls -la}"
-  files:
-    - {... same as success}
-
-  next_steps:
-    - "{N} files not found. Verify paths or update FILE_LIST."
-    - "Proceeding with {files_summarized} available summaries."
-```
-</output>

package/pennyfarthing-dist/agents/sm-finish.md

@@ -1,82 +0,0 @@
----
-name: sm-finish
-description: SM finish preflight - runs parallel checks before SM archives
-tools: Bash, Read
-model: haiku
----
-
-<arguments>
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `STORY_ID` | Yes | Story identifier, e.g., "31-10" |
-| `JIRA_KEY` | No | Jira issue key (skip Jira checks if absent) |
-| `REPOS` | Yes | Repository name(s) |
-| `BRANCH` | Yes | Feature branch name |
-</arguments>
-
-<execution>
-## Run Preflight Script
-
-The preflight script runs all checks in parallel using asyncio:
-
-```bash
-source .venv/bin/activate && python -m pennyfarthing_scripts.preflight finish {STORY_ID} --branch {BRANCH} --jira {JIRA_KEY}
-```
-
-If no JIRA_KEY, omit the `--jira` flag.
-
-The script returns JSON with:
-- `status`: "success" or "blocked"
-- `ready_to_finish`: boolean
-- `issues`: array of blocking issues
-- `warnings`: array of non-blocking warnings
-- `next_steps`: array of recommended actions
-</execution>
-
-<critical>
-## Jira Transition
-
-The Jira transition to Done is handled by `/story finish` (finish-story.sh).
-Do NOT transition Jira here - that would duplicate the finish script's work.
-This subagent only performs preflight checks and assessment.
-</critical>
-
-<output>
-## Output Format
-
-Parse the JSON output from the preflight script and return a `FINISH_PREFLIGHT_RESULT` block.
-
-### Ready to Finish
-```yaml
-FINISH_PREFLIGHT_RESULT:
-  status: success
-  ready_to_finish: true
-  story_id: "{story_id from JSON}"
-  pr:
-    state: "{pr.state from JSON}"
-    merged: {pr.merged from JSON}
-    url: "{pr.url from JSON}"
-  lint:
-    clean: {lint.clean from JSON}
-  jira:
-    current: "{jira.current from JSON}"
-    key: "{jira.key from JSON}"
-  acceptance_criteria:
-    total: {acceptance_criteria.total from JSON}
-    checked: {acceptance_criteria.checked from JSON}
-  next_steps: {next_steps array from JSON}
-```
-
-### Not Ready
-```yaml
-FINISH_PREFLIGHT_RESULT:
-  status: blocked
-  ready_to_finish: false
-  issues: {issues array from JSON}
-  warnings: {warnings array from JSON}
-  next_steps: {next_steps array from JSON}
-```
-
-### Jira Skipped
-If `jira_skipped: true` in JSON, note this in output.
-</output>

package/pennyfarthing-dist/agents/sm-handoff.md

@@ -1,129 +0,0 @@
----
-name: sm-handoff
-description: Complete handoff bookkeeping when SM work is done
-tools: Bash, Read, Edit
-model: haiku
----
-
-<critical>
-**NEVER mark acceptance criteria as complete.** This subagent only:
-1. Verifies prerequisites exist
-2. Updates the Workflow Tracking section for phase transition
-
-AC checkboxes are marked ONLY by the agent that does the work.
-</critical>
-
-<critical>
-**Marker generation happens in the CALLING agent, not here.**
-This subagent verifies prerequisites and updates session file only.
-Return `HANDOFF_RESULT` with the next agent name - SM runs `handoff-marker.sh` as their last action.
-</critical>
-
-<arguments>
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `STORY_ID` | Yes | Story identifier, e.g., "31-10" |
-| `NEXT_AGENT` | Yes | Target agent: `tea` or `dev` |
-| `NEXT_PHASE` | Yes | Target phase: `red` (TEA) or `implement` (Dev) |
-| `WORKFLOW` | Yes | Workflow type: "tdd", "trivial", etc. |
-</arguments>
-
-<gate>
-## Handoff Checklist
-
-- [ ] Session file exists with story context
-- [ ] Acceptance criteria defined (count, don't mark)
-- [ ] Feature branches created
-- [ ] Jira story claimed (if applicable)
-- [ ] Update Workflow Tracking section:
-  - `**Phase:**` → `{NEXT_PHASE}`
-  - `**Phase Started:**` → `{NOW}`
-  - Add Phase History row
-- [ ] Report status summary
-</gate>
-
-## Phase Transition Update
-
-Edit `## Workflow Tracking`:
-
-```markdown
-## Workflow Tracking
-**Workflow:** {WORKFLOW}
-**Phase:** {NEXT_PHASE}
-**Phase Started:** {NOW}
-
-### Phase History
-| Phase | Started | Ended | Duration |
-|-------|---------|-------|----------|
-| setup | {SM_STARTED} | {NOW} | {DURATION} |
-| {NEXT_PHASE} | {NOW} | - | - |
-```
-
-**Duration:** Subtract SM Started from {NOW}, format as `Xm` or `Xh Ym`.
-
-<output>
-## Output Format
-
-Return a `HANDOFF_RESULT` block:
-
-### Success
-```
-HANDOFF_RESULT:
-  status: success
-  next_agent: {NEXT_AGENT}
-  next_phase: {NEXT_PHASE}
-  story_id: {STORY_ID}
-  summary: "{what was done}"
-
-  next_steps:
-    - "Handoff complete. Run handoff-marker.sh as ABSOLUTE LAST ACTION."
-    - "Command: .pennyfarthing/scripts/core/handoff-marker.sh {next_agent}"
-    - "Output marker result verbatim, then EXIT. Nothing after."
-```
-
-### Example (SM → TEA)
-```
-HANDOFF_RESULT:
-  status: success
-  next_agent: tea
-  next_phase: red
-  story_id: MSSCI-12274
-  summary: "Session updated (setup → red), branch verified, 7 AC defined"
-
-  next_steps:
-    - "Handoff complete. Run handoff-marker.sh as ABSOLUTE LAST ACTION."
-    - "Command: .pennyfarthing/scripts/core/handoff-marker.sh tea"
-    - "Output marker result verbatim, then EXIT. Nothing after."
-```
-
-### Blocked
-```
-HANDOFF_RESULT:
-  status: blocked
-  error: "{description}"
-  fix: "{recommended action}"
-  failed_check: "{which gate check failed}"
-
-  next_steps:
-    - "Handoff blocked: {error}"
-    - "Required action: {fix}"
-    - "Do NOT run handoff-marker.sh. Resolve issue first."
-```
-</output>
-
----
-
-## Calling Agent Exit Sequence
-
-When SM receives `HANDOFF_RESULT`:
-
-1. If `status: blocked` → Report the error, do NOT proceed
-2. If `status: success` → Continue to exit sequence below
-
-**CRITICAL: SM MUST run this as their ABSOLUTE LAST ACTION:**
-
-```bash
-.pennyfarthing/scripts/core/handoff-marker.sh {next_agent}
-```
-
-Then output the script's result verbatim and EXIT. Nothing else after.

package/pennyfarthing-dist/agents/sm-setup.md

@@ -1,251 +0,0 @@
----
-name: sm-setup
-description: SM setup subagent - combines research and story setup modes
-tools: Bash, Read, Edit, Write
-model: haiku
----
-
-<arguments>
-| Argument | Required | Description |
-|----------|----------|-------------|
-| `MODE` | Yes | `research` (scan backlog) or `setup` (execute story setup) |
-| `STORY_ID` | setup | Story identifier, e.g., "31-10" |
-| `JIRA_KEY` | setup | Jira issue key, e.g., "MSSCI-12345" |
-| `REPOS` | setup | Repository name(s) |
-| `SLUG` | setup | Branch slug, e.g., "fix-typo" |
-| `WORKFLOW` | setup | Workflow type: "tdd", "trivial", etc. |
-| `ASSIGNEE` | No | Jira assignee (defaults to current user) |
-</arguments>
-
----
-
-# MODE: research
-
-<gate>
-## Research Steps
-
-- [ ] Use `/sprint backlog` for initial backlog scan:
-  ```bash
-  .pennyfarthing/scripts/sprint/available-stories.sh
-  ```
-- [ ] Use `/jira` skill to enrich with Jira status/assignee:
-  - `/jira search "project=MSSCI AND sprint in openSprints()"` - Get all sprint stories
-  - `/jira view {JIRA_KEY}` - Check individual story details
-- [ ] Check context availability
-- [ ] Check dependencies
-- [ ] Output report with recommendations
-</gate>
-
-<output>
-## Output Format (MODE: research)
-
-Return a `RESEARCH_RESULT` block:
-
-```
-RESEARCH_RESULT:
-  status: success
-  sprint_number: {N}
-  available_count: {N}
-  stories:
-    - id: "{STORY_ID}"
-      title: "{title}"
-      points: {N}
-      repos: ["{repo}"]
-      context_ready: {true|false}
-      blocked_by: ["{dependency}"] or null
-  recommended:
-    id: "{STORY_ID}"
-    reason: "{why this story}"
-
-  next_steps:
-    - "Present stories to user for selection."
-    - "Recommended: {recommended.id} - {recommended.reason}"
-    - "On selection: Spawn sm-setup with MODE=setup, STORY_ID={selected}"
-```
-</output>
-
----
-
-# MODE: setup
-
-<critical>
-Session file header MUST be: `# Story {STORY_ID}: {TITLE}`
-
-Other formats break Cyclist detection.
-</critical>
-
-<gate>
-## Setup Steps
-
-- [ ] Verify epic has Jira key (auto-create if missing)
-- [ ] Check workflow permissions (auto-prompt for missing)
-- [ ] Claim story in Jira
-- [ ] Write session file with Workflow Tracking section
-- [ ] Create feature branch
-- [ ] Update sprint YAML status
-</gate>
-
-## Step 1: Check Epic Jira
-
-```bash
-# Extract epic number from story ID
-EPIC_NUM=$(echo "{STORY_ID}" | cut -d'-' -f1)
-
-# Get epic's Jira key (use script, not direct yq)
-EPIC_JIRA=$(.pennyfarthing/scripts/sprint/get-epic-field.sh "$EPIC_NUM" jira)
-```
-
-If missing or "null": auto-create via `jira-epic-creation.ts`
-
-## Step 2: Check Workflow Permissions
-
-If the workflow has a `permissions` array, check each permission against cached grants.
-
-```bash
-# Read workflow's permissions from definition
-WORKFLOW_FILE="pennyfarthing-dist/workflows/{WORKFLOW}.yaml"
-PERMISSIONS=$(yq eval '.workflow.permissions // []' "$WORKFLOW_FILE")
-
-# Read cached grants
-GRANTS=$(cat .claude/settings.local.json 2>/dev/null | jq '.permissions.grants // []')
-```
-
-**For each required permission:**
-
-1. Check if a matching grant exists (same tool + scope)
-2. If missing, prompt user for permission:
-   - First output marker: `<!-- CYCLIST:QUESTION:yesno -->`
-   - Then use AskUserQuestion with the prompt:
-     ```
-     "The {WORKFLOW} workflow requires {tool} access for: {reason}
-     Grant permission for {tool} with scope '{scope}'?"
-     ```
-3. If granted, add to `.claude/settings.local.json` under `permissions.grants[]`:
-   ```json
-   {
-     "tool": "{tool}",
-     "scope": "{scope}",
-     "grant_type": "session",
-     "granted_at": "{ISO timestamp}"
-   }
-   ```
-4. If denied, report blocked and exit
-
-**Note:** Use `checkWorkflowPermissions()` from `@pennyfarthing/core` for permission matching logic.
-
-## Step 3: Claim in Jira
-
-Use `/jira check` and `/jira claim` commands:
-
-```bash
-# Check availability first
-/jira check {JIRA_KEY}
-
-# Then claim (assign to self + move to In Progress)
-/jira claim {JIRA_KEY}
-```
-
-**Exit codes:**
-- `0` - Available or successfully claimed
-- `1` - Assigned to someone else (BLOCKED)
-- `2` - Not found or not synced to Jira
-- `3` - Error (CLI not installed, etc.)
-
-## Step 4: Write Session File
-
-```markdown
-# Story {STORY_ID}: {TITLE}
-
-## Story Details
-- **ID:** {STORY_ID}
-- **Workflow:** {WORKFLOW}
-
-## Workflow Tracking
-**Workflow:** {WORKFLOW}
-**Phase:** setup
-**Phase Started:** {NOW}
-
-### Phase History
-| Phase | Started | Ended | Duration |
-|-------|---------|-------|----------|
-| setup | {NOW} | - | - |
-```
-
-## Step 5: Create Branch
-
-```bash
-git checkout develop && git pull && \
-git checkout -b feat/{STORY_ID}-{SLUG}
-```
-
-<workflow-type-detection>
-## Step 6: Determine Workflow Type
-
-After session file is created, determine how to route:
-
-```bash
-WORKFLOW_TYPE=$(.pennyfarthing/scripts/workflow/get-workflow-type.sh "{WORKFLOW}")
-```
-
-| Workflow Type | Routing |
-|---------------|---------|
-| `phased` | Return `next_agent` = first agent in workflow (tea/dev/orchestrator) |
-| `stepped` | Return `next_agent` = null, `start_command` = `/workflow start {WORKFLOW}` |
-</workflow-type-detection>
-
-<output>
-## Output Format (MODE: setup)
-
-Return a `SETUP_RESULT` block:
-
-### Success (Phased Workflow)
-```
-SETUP_RESULT:
-  status: success
-  story_id: "{STORY_ID}"
-  jira_key: "{JIRA_KEY}"
-  session_file: ".session/{STORY_ID}-session.md"
-  branch: "feat/{STORY_ID}-{SLUG}"
-  workflow: "{WORKFLOW}"
-  workflow_type: "phased"
-  next_agent: "{tea|dev|orchestrator}"
-
-  next_steps:
-    - "Setup complete. Spawn sm-handoff to transition to {next_agent}."
-    - "Workflow '{workflow}' routes to: {next_agent}"
-    - "Session file ready at: {session_file}"
-```
-
-### Success (Stepped Workflow)
-```
-SETUP_RESULT:
-  status: success
-  story_id: "{STORY_ID}"
-  jira_key: "{JIRA_KEY}"
-  session_file: ".session/{STORY_ID}-session.md"
-  branch: "feat/{STORY_ID}-{SLUG}"
-  workflow: "{WORKFLOW}"
-  workflow_type: "stepped"
-  next_agent: null
-  start_command: "/workflow start {WORKFLOW}"
-
-  next_steps:
-    - "Setup complete. This is a STEPPED workflow."
-    - "DO NOT spawn sm-handoff. Tell user to run: /workflow start {WORKFLOW}"
-    - "Session file ready at: {session_file}"
-```
-
-### Blocked
-```
-SETUP_RESULT:
-  status: blocked
-  error: "{description}"
-  fix: "{recommended action}"
-  stage: "{epic_jira|permissions|jira_claim|session|branch}"
-
-  next_steps:
-    - "Setup blocked at {stage}: {error}"
-    - "Required action: {fix}"
-    - "Do NOT proceed with handoff until resolved."
-```
-</output>