sprint

Organize sprint status, backlog, and story workflows via the pf sprint CLI.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/slabgorb/sidequest --skill sprint-slabgorb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/slabgorb/sidequest/tree/main/.pennyfarthing/skills/pf-sprint
Command: npx skills add https://github.com/slabgorb/sidequest --skill sprint-slabgorb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficient sprint planning and tracking for Pennyfarthing by centralizing sprint status, backlog, and story workflow management, enabling teams to quickly view current work, understand epic context, and coordinate among stakeholders without manual YAML edits.

Core Features & Use Cases

  • View current sprint status, backlog by epic, and in-progress work to inform planning.
  • Start work on stories, update progress, and monitor velocity using the pf sprint CLI.
  • Sync with Jira and BMAD workflows to reflect changes in external tooling and reports.

Quick Start

Run pf sprint status to view the current sprint and pf sprint backlog to review available stories.

Frequently Asked Questions about sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view current sprint status and backlog by epic?

To view current sprint status and backlog by epic, run the `pf sprint status` and `pf sprint backlog` CLI commands. This provides a centralized overview of in-progress work and available stories for planning.

Can I manually edit sprint YAML files to update story progress?

You should not manually edit sprint YAML files to update story progress. The Skill enforces safe usage by generating deterministic YAML exclusively through `pf sprint` CLI commands to prevent configuration errors.

Does the pf sprint workflow integrate with Jira and BMAD?

Yes, the pf sprint workflow integrates with Jira and BMAD. It syncs story progress and epic updates to reflect changes automatically in external Jira tooling and BMAD workflow reports.

What's the best way to assign stories and track epic progress across sprints?

The best way to assign stories and track epic progress is using `pf sprint` CLI commands to start work, update progress, and monitor velocity across active and future sprints deterministically.

Why use a CLI tool for sprint planning instead of manual backlog tracking?

Using a CLI tool for sprint planning centralizes story workflows, backlog lists, and epic context for engineers. It eliminates manual YAML edits, ensuring deterministic sprint state generation and safe tracking.