agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/sprint-plan/SKILL.md

sprint-plan

Skill9 starsChanged 7 months agoMITView on GitHub

Create a sprint plan from the systems-index and current priorities. Breaks features into tasks with estimates and owners.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report and team-audio.

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

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 4 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Read production/decision-log.md (if exists)

    line 24
  2. Very specific:

    Check open bug tickets (production/bugs/ if tracked here)

    line 26
  3. Very specific:

    Content-focused: Add maps/quests/items to existing systems

    line 32
  4. Very specific:

    Use /estimate for each task

    line 45
  5. Very specific:

    Write to production/sprints/sprint-<N>-plan.md using .claude/docs/templates/sprint-plan-template.md.

    line 51
  6. Very specific:

    Add sprint plan filename to production/session-state/current-sprint.txt.

    line 65

“Common” is measured: kept by at least 6 in 10 of the 35 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-plan — Sprint Planning Workflow

Delegate to: producer

Prerequisites

  • design/gdd/systems-index.md exists (run /map-systems first if not)
  • Current sprint context in production/session-state/ (if any)

Steps

1. Ask Planning Context

  • "What's the sprint length?" (default: 2 weeks)
  • "What's the theme/goal for this sprint?"
  • "Any hard deadlines or events driving priorities?"
  • "What went well / poorly last sprint?" (if returning)

2. Review Backlog

  • Read design/gdd/systems-index.md
  • Read production/decision-log.md (if exists)
  • Read production/risk-register.md (if exists)
  • Check open bug tickets (production/bugs/ if tracked here)

3. Propose Sprint Goals

Present 2-4 sprint theme options based on priorities:

  • Feature-focused: Ship N new features
  • Quality-focused: Polish existing, fix bugs, reduce tech debt
  • Content-focused: Add maps/quests/items to existing systems
  • Infrastructure-focused: Refactor, CI/CD, tools
  • Live-ops-focused: Events, balance tweaks, retention features

4. Break Into Tasks

For the chosen theme, break into tasks:

  • Design tasks: GDDs to write/update
  • Implementation tasks: Code to write
  • Art tasks: Assets needed
  • QA tasks: Tests to run
  • Polish tasks: Fixes and improvements

5. Estimate & Assign

  • Use /estimate for each task
  • Assign each to a specialist (not a human, but the agent that would own it)
  • Flag dependencies
  • Sum total effort; verify it fits sprint capacity

6. Generate Sprint Plan Document

Write to production/sprints/sprint-<N>-plan.md using .claude/docs/templates/sprint-plan-template.md.

Sprint Plan Template Sections

  1. Sprint Goal (1-2 sentences)
  2. Duration (start date, end date)
  3. Theme
  4. Committed Tasks (list with estimates and owners)
  5. Stretch Goals (if capacity allows)
  6. Risks (known blockers, unknowns)
  7. Definition of Done (what "sprint complete" means)
  8. Review Cadence (when to check progress)

Output

Present the draft plan to the user for approval. On approval, save to disk. Add sprint plan filename to production/session-state/current-sprint.txt.

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.