agentleFS
Sign inStart free
faizkhairifaizkhairi/claude-code-blueprint/skills/sprint-plan/SKILL.md

sprint-plan

Skill73 starsChanged 4 months agoMITView on GitHub

MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes. Produces: task breakdown with S/M/L/XL size estimates, dependency ordering, risk analysis, and a Definition of Done checklist; output is a structured markdown plan ready for implementation.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use balance-check, team-combat and 10 more.

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.
  • CoralGameSkill

    balance-check

    Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design.

    Also in 5 projects that use this

  • CoralGameSkill

    team-combat

    Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.

    Also in 5 projects that use this

  • +10 more from CoralGame

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a sprint plan for: $ARGUMENTS

    line 8
  2. Distinctive:

    Check existing code: Search codebase for related implementations that can be reused

    line 11

“Common” is measured: kept by at least 6 in 10 of the 34 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

Create a sprint plan for: $ARGUMENTS

  1. Analyze the requirement: Understand scope, constraints, dependencies
  2. Check existing code: Search codebase for related implementations that can be reused
  3. Break into tasks:
    • Each task should be independently deliverable
    • Include file paths that will be modified or created
    • Estimate size: S (< 1hr), M (1-4hr), L (4-8hr), XL (> 1 day)
  4. Sequence tasks: Identify dependencies, mark blocking tasks, find parallelizable work
  5. Identify risks: What could go wrong? What needs clarification?
  6. Output format:

Sprint Plan: [Feature Name]

Tasks

#TaskSizeDepends OnFiles
1...S-path/to/file

Risks

  • [Risk description and mitigation]

Definition of Done

  • All tasks completed
  • Tests written and passing
  • Code reviewed
  • Documentation updated
  • No security vulnerabilities introduced

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