@pennyfarthing/core 11.0.0 → 11.1.1

package/pennyfarthing-dist/commands/pf-start-epic.md

@@ -1,168 +1,14 @@
 ---
-description: Start an epic - move to current sprint and generate tech context
+deprecated: true
+redirect: pf-epic
+description: "DEPRECATED: Use /pf-epic start instead."
 ---
 
-# Start Epic Workflow
+# /start-epic - DEPRECATED
 
-**This command prepares an epic for development by moving it to the current sprint and generating technical context.**
+Epic commands have been consolidated into `/pf-epic`. Use:
 
-## What This Does
-
-1. **Validates** the epic exists in backlog or current sprint
-2. **Moves** the epic to current sprint if not already there
-3. **Runs** the SM agent's `epic-tech-context` task to generate technical specifications
-
-## Prerequisites
-
-```bash
-cd $CLAUDE_PROJECT_DIR
-
-# Verify sprint files exist
-if [ ! -f "sprint/current-sprint.yaml" ] || [ ! -f "sprint/backlog.yaml" ]; then
-    echo "ERROR: Sprint files not found"
-    exit 1
-fi
-
-echo "Sprint files found - ready to start epic"
-```
-
-## Usage
-
-Provide the epic ID when invoking this command:
-- `epic-5` - Pennyfarthing epic (format: `epic-N`)
-
-## Workflow Steps
-
-### Step 0: Clean Previous Work Artifacts
-
-Before starting a new epic, clean up stale artifacts from previous work:
-
-```bash
-cd $CLAUDE_PROJECT_DIR
-
-# Run conservative cleanup (7+ day old artifacts)
-$CLAUDE_PROJECT_DIR/scripts/misc/session-cleanup.sh --dry-run
-
-# If dry-run looks good, run actual cleanup
-$CLAUDE_PROJECT_DIR/scripts/misc/session-cleanup.sh
-
-# Archive epic contexts for completed epics
-$CLAUDE_PROJECT_DIR/scripts/misc/session-cleanup.sh --aggressive
-```
-
-This ensures a clean slate before starting new epic work and archives contexts from completed epics.
-
-### Step 1: Identify Epic
-
-Ask the user for the epic ID if not provided:
-> "Which epic would you like to start? (e.g., epic-5, sim-epic-10)"
-
-### Step 2: Check Epic Location
-
-```bash
-cd $CLAUDE_PROJECT_DIR
-
-# Check if epic is in current sprint
-if grep -q "^$EPIC_ID:" sprint/current-sprint.yaml; then
-    echo "Epic $EPIC_ID is already in current sprint"
-    EPIC_LOCATION="current"
-elif grep -q "^$EPIC_ID:" sprint/backlog.yaml; then
-    echo "Epic $EPIC_ID found in backlog - will move to current sprint"
-    EPIC_LOCATION="backlog"
-else
-    echo "ERROR: Epic $EPIC_ID not found in sprint files"
-    exit 1
-fi
-```
-
-### Step 3: Move Epic to Current Sprint (if needed)
-
-If the epic is in backlog:
-
-1. **Extract** the epic block from `sprint/backlog.yaml`
-2. **Add** the epic to `sprint/current-sprint.yaml` under the active work section
-3. **Update** the epic status from `backlog` or `planned` to `in-progress`
-4. **Remove** the epic from `sprint/backlog.yaml`
-
-**Format for current-sprint.yaml:**
-```yaml
-  # ===========================================================================
-  # EPIC [N]: [Name]
-  # ===========================================================================
-  - id: MSSCI-XXXXX
-    type: epic
-    title: "Epic: [Name]"
-    points: [total_pts]
-    completed_points: 0
-    priority: P1
-    status: in_progress
-    stories:
-      # Stories added during tech context generation
-      - id: MSSCI-XXXXX
-        title: "[Story title]"
-        points: [N]
-        priority: P2
-        status: backlog
-        repos: [cyclist|pennyfarthing|both]
-        workflow: [tdd|trivial|agent-docs]
-        acceptance_criteria:
-          - [AC 1]
-          - [AC 2]
-```
-
-### Step 4: Generate Epic Tech Context
-
-Invoke the SM agent with the `epic-tech-context` task:
-
-**Run:** `/sm` with task: `epic-tech-context` for epic `$EPIC_ID`
-
-The SM agent will:
-1. Load the epic details from current sprint
-2. Analyze the codebase for relevant files
-3. Generate technical context including:
-   - Current state analysis
-   - Technical approach
-   - File modifications needed
-   - API/UI changes
-   - Database changes
-   - Testing strategy
-   - Story breakdown with acceptance criteria
-4. Save context to `.session/context-epic-$EPIC_ID.md`
-
-### Step 5: Confirm Ready
-
-After tech context is generated:
-
-```
-✅ Epic $EPIC_ID is ready for development
-
-Next steps:
-1. Review the tech context: cat .session/context-epic-$EPIC_ID.md
-2. Start first story: /new-work
-3. SM will select from this epic's stories
-```
-
-## Example
-
-```bash
-# User invokes: /start-epic epic-5
-
-# Output:
-# → Checking epic-5 location...
-# → Epic epic-5 found in backlog
-# → Moving epic-5 to current sprint...
-# → Updating status to in-progress...
-# → Invoking SM for epic-tech-context...
-# → [SM generates technical context]
-# → ✅ Epic epic-5 is ready for development
-```
-
-## Notes
-
-- This command does NOT start a story - use `/new-work` for that
-- The epic tech context provides the foundation for story-level work
-- Stories within the epic will be worked via the normal TDD flow
-
----
-
-**Flow:** `/start-epic` → SM (epic-tech-context) → `/new-work` → TDD cycle
+| Old Command | New Command |
+|-------------|-------------|
+| `/start-epic <id>` | `/pf-epic start <id>` |
+| `/close-epic <id>` | `/pf-epic close <id>` |

package/pennyfarthing-dist/commands/pf-sync-epic-to-jira.md

@@ -1,184 +1,13 @@
 ---
-description: Sync Pennyfarthing epic to Jira MSSCI project using jira CLI
+deprecated: true
+redirect: pf-jira
+description: "DEPRECATED: Use /pf-jira sync-epic instead."
 ---
 
-# Sync Epic to Jira Workflow
+# /sync-epic-to-jira - DEPRECATED
 
-This workflow syncs a Pennyfarthing epic and its stories to Jira using the `jira` CLI tool.
+Jira sync commands have been consolidated into `/pf-jira`. Use:
 
-**IMPORTANT:** All Pennyfarthing issues MUST be labeled with `pennyfarthing` to distinguish them from Pennyfarthing work.
-
-## Prerequisites
-
-- `jira` CLI installed: `brew install ankitpokhrel/jira-cli/jira-cli`
-- `jira` CLI configured: `jira init`
-- Epic exists in `sprint/current-sprint.yaml`
-
-**For complete jira CLI reference, see the `jira` skill** (`.claude/skills/jira/SKILL.md`). The examples below are quick references; the skill has troubleshooting, user mappings, and edge cases.
-
-## Label Requirement
-
-All Pennyfarthing epics and stories must include the `pennyfarthing` label:
-```bash
--l pennyfarthing
-```
-
-## Quick Sync
-
-### Sync a Single Story
-
-```bash
-# View story status
-./scripts/jira/jira-sync-story.sh 35-2-topology-editor
-
-# Transition to match Pennyfarthing status
-./scripts/jira/jira-sync-story.sh 35-2-topology-editor --transition
-
-# Add a comment
-./scripts/jira/jira-sync-story.sh 35-2-topology-editor --comment "Started development"
-```
-
-### Sync All Stories in Epic
-
-```bash
-# For each story in the epic, sync status
-for story in $(yq '.epic-35.stories | keys | .[]' sprint/current-sprint.yaml); do
-    ./scripts/jira/jira-sync-story.sh "$story" --transition
-done
-```
-
-## Manual Jira CLI Commands
-
-**IMPORTANT:** Most commands require `-p MSSCI` (project flag) even when the issue key contains the project prefix.
-
-### View Issue
-
-```bash
-jira issue view MSSCI-123
-```
-
-### Create Story
-
-```bash
-jira issue create \
-    -p MSSCI \
-    -tStory \
-    -s"Story 1-5: Add Epic Context Guardrail" \
-    -b"Description here" \
-    -yHigh \
-    -l pennyfarthing \
-    --no-input
-```
-
-### Create Epic
-
-```bash
-jira issue create \
-    -p MSSCI \
-    -tEpic \
-    -s"Epic 1: Agentic Best Practices Implementation" \
-    -b"Epic description" \
-    -l pennyfarthing \
-    --no-input
-```
-
-### Link Story to Epic
-
-```bash
-# Use --parent to link a story to its epic
-jira issue create \
-    -p MSSCI \
-    -tStory \
-    -s"Story Title" \
-    --parent MSSCI-EPIC_KEY \
-    -l pennyfarthing \
-    --no-input
-```
-
-### Assign Issue
-
-```bash
-# Assign to self
-jira issue assign -p MSSCI MSSCI-123 "$(jira me)"
-
-# Assign to someone else
-jira issue assign -p MSSCI MSSCI-123 "john.doe@1898andco.io"
-```
-
-### Transition Issue
-
-```bash
-jira issue move MSSCI-123 "In Progress" -p MSSCI
-jira issue move MSSCI-123 "In Review" -p MSSCI
-jira issue move MSSCI-123 "Done" -p MSSCI
-```
-
-### Add Comment
-
-```bash
-jira issue comment add MSSCI-123 "Development started on branch feat/35-2"
-```
-
-### Link Issues
-
-```bash
-jira issue link MSSCI-123 MSSCI-124 "Blocks"
-```
-
-### List Issues
-
-```bash
-# All in-progress stories
-jira issue list -s "In Progress"
-
-# Stories in current sprint
-jira sprint list --current
-
-# Stories assigned to me
-jira issue list -a$(jira me)
-```
-
-## Status Mapping
-
-| Pennyfarthing | Jira |
-|-----------|------|
-| `backlog` | To Do |
-| `in-progress` | In Progress |
-| `review` | In Review |
-| `done` | Done |
-
-## Priority Mapping
-
-| Pennyfarthing | Jira |
-|-----------|------|
-| `P0` | Highest |
-| `P1` | High |
-| `P2` | Medium |
-
-## Troubleshooting
-
-**jira CLI not configured:**
-```bash
-jira init
-# Follow prompts to authenticate
-```
-
-**Issue not found:**
-- Check the Jira key is correct
-- Verify you have access to the project
-
-**Transition not available:**
-- Some transitions require specific conditions
-- Check the Jira workflow for allowed transitions
-
-## Related Scripts
-
-| Script | Purpose |
-|--------|---------|
-| `jira-claim-story.sh` | Check/claim story assignment |
-| `jira-sync-story.sh` | Sync single story status |
-| `sync-epic-to-jira.sh` | Generate sync report for epic |
-
----
-
-**Last Updated**: 2025-12-16
+| Old Command | New Command |
+|-------------|-------------|
+| `/sync-epic-to-jira` | `/pf-jira sync-epic` |