Menu
Jira CLI commands for sprint management. Use when viewing, assigning, or updating Jira issues from the command line.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Interactive playtest — full-stack (UI + Playwright + UX Designer) or headless (API-only + Python driver). Coordinates cross-workspace bug reporting via ping-pong file with FIXER.
LLM cost and cache forensics — reconcile server-log narrator costs against the Anthropic Admin API, attribute per-model spend, detect dead caching and invisible callers. Use when analyzing API costs, auditing cache efficiency, or when the Console bill doesn't match expectations.
Create epic or story context documents. Reads sprint YAML for epic/story data, reads context-schema.yaml for required sections, populates templates, and writes output to sprint/context/. Epic context is a single-agent operation (no tandem). Story context uses PM + tandem partner for domain-specific observations.
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 `pf sprint` CLI commands - never manually edit sprint YAML.
List available workflows, show current workflow details, and switch workflows mid-session. Use when checking available workflow types (TDD, trivial, agent-docs), viewing current workflow phase, switching to a different workflow pattern, or managing BikeLane stepped workflows.
Create epic or story context documents. Reads sprint YAML for epic/story data, reads context-schema.yaml for required sections, populates templates, and writes output to sprint/context/. Epic context is a single-agent operation (no tandem). Story context uses PM + tandem partner for domain-specific observations.
Based on SOC occupation classification
| name | jira |
| description | Jira CLI commands for sprint management. Use when viewing, assigning, or updating Jira issues from the command line. |
| args | [view|check|claim|move|assign|create|sync|bidirectional|reconcile|link|search|sprint] |
| Command | CLI | Purpose |
|---|---|---|
/pf-jira view <key> | pf jira view <key> | View issue details |
/pf-jira check <key> | pf jira check <key> | Check availability |
/pf-jira claim <key> | pf jira claim <key> [--dry-run] | Assign to self + In Progress |
/pf-jira move <key> <status> | pf jira move <key> "<status>" [--dry-run] | Transition status |
/pf-jira assign <key> <user> | pf jira assign <key> <user> [--dry-run] | Assign to user |
/pf-jira link <p> <c> [type] | pf jira link <parent> <child> [type] [--dry-run] | Link two issues |
/pf-jira search "<jql>" | pf jira search "<jql>" | Search by JQL |
/pf-jira create epic <id> | pf jira create epic <id> [--dry-run] | Create epic + stories |
/pf-jira create story <ek> <sid> | pf jira create story <epic-key> <story-id> [--dry-run] | Create single story |
/pf-jira create standalone | pf jira create standalone "<title>" [opts] | Create standalone story |
/pf-jira sync <epic> | pf jira sync <epic> [--transition] [--points] [--all] [--dry-run] | Sync epic to Jira |
/pf-jira bidirectional | pf jira bidirectional [opts] | Bidirectional sync |
/pf-jira reconcile | pf jira reconcile [--fix] | Reconciliation report |
/pf-jira sprint add <sid> <key> | pf jira sprint add <sprint-id> <issue-key> [--dry-run] | Add issue to sprint |
| GitHub | Jira Email |
|---|---|
| slabgorb | slabgorb@gmail.com |
| arcaven | michael.pursifull@1898andco.io |
| RoseSecurity | michael.rosenfeld@1898andco.io |
| Zious11 | jared.richards@1898andco.io |
| drbothen | joshua.magady@1898andco.io |
brew install ankitpokhrel/jira-cli/jira-cli
jira init
export JIRA_API_TOKEN='your-token'
Detailed options and behavior: usage.md Practical examples: examples.md