agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/sprint-planning/SKILL.md

sprint-planning

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Help with sprint planning by analyzing the backlog. Lists unassigned issues, identifies blocked items, shows issues ready for sprint, can add issues to sprint. Use when user says "sprint planning", "plan sprint", or "backlog analysis".

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sprint-review and retrospective.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nobufumi-tegoSkill

    sprint-review

    スプリント終了時に実行。DoD確認・デプロイ・CLAUDE.md更新・レトロ記録を行う。

    Also in 4 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If "command timed out": learn_tool_fix("jira_list_issues", "command timed out", "Jira API timeout", "Check VPN and retry")

    line 65

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sprint Planning

Analyzes backlog for sprint planning. Lists backlog, ready-for-dev, and blocked issues; identifies sprint candidates.

Inputs

InputTypeDefaultPurpose
projectstringAAPJira project key
sprintstring""Sprint name to add issues to
limitint20Max issues to show
sprint_idstring""Sprint ID for auto_add
auto_addboolfalseAuto-add top candidate to sprint
check_qualitybooltrueRun jira_lint on backlog issues

Workflow

1. Load Persona

  • persona_load(persona="developer")

2. Known Issues & Knowledge

  • check_known_issues(tool_name="jira_list_issues", error_text="")
  • knowledge_query(project="automation-analytics-backend", persona="developer", section="patterns")
  • knowledge_query(project="automation-analytics-backend", persona="developer", section="gotchas")

3. Jira Queries

  • jira_list_issues(project=project, status="Backlog", limit=limit) — Backlog issues
  • jira_list_blocked(project=project) — Blocked issues
  • jira_list_issues(project=project, status="Ready for Development", limit=limit) — Ready issues

4. Parse Results

  • Backlog: extract issue keys (AAP-XXXXX) and summaries
  • Blocked: extract blocked issue keys
  • Ready: extract ready issue keys and summaries

5. Quality Check (if check_quality and backlog has issues)

  • jira_lint(issue_key=backlog_issues[0].key) — Check first backlog issue quality

6. Identify Sprint Candidates

  • Candidates = ready issues NOT in blocked set
  • Sort/filter for best candidates (first 10)

7. Auto-Add (if auto_add and candidates exist)

  • jira_add_to_sprint(issue_key=candidates[0].key, sprint_id=sprint_id)

8. Save Context & Log

  • Save to state/shared_context: last_sprint_planning with backlog_count, blocked_count, candidates
  • memory_session_log(action="Sprint planning for {project}", details="Backlog: X, Blocked: Y, Candidates: Z")

9. Learning from Failures

  • If "command timed out": learn_tool_fix("jira_list_issues", "command timed out", "Jira API timeout", "Check VPN and retry")
  • If "unauthorized": learn_tool_fix("jira_list_issues", "unauthorized", "Jira auth failed", "Check credentials")

Output Format

## 📋 Sprint Planning: AAP

### 📥 Backlog (N issues)

- **AAP-12345**: Summary...

### ✅ Ready for Development (N)

- **AAP-12346**: Summary...

### 🚫 Blocked (N)

- AAP-12347

### 🎯 Sprint Candidates (N)

- **AAP-12346**: Summary...

### Add to Sprint (if sprint provided)

jira_add_to_sprint(issue_key='AAP-12346', sprint='Sprint 42')

Key MCP Tools

  • persona_load, jira_list_issues, jira_list_blocked, jira_add_to_sprint, jira_lint, knowledge_query, check_known_issues, memory_session_log, learn_tool_fix

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free