agentleFS
naman10parikhnaman10parikh/pixel/.claude/skills/sprint/SKILL.md

sprint

Skill0 starsChanged 27 days agoMITView on GitHub

Plan a focused development sprint. Breaks large goals into 2-hour chunks with dependencies and parallelization opportunities.

29 other projects use a version of this.

Adopted by

Most recently taken up by

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 22 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:

    Never exceed 12 tasks per sprint (cognitive overload)

    line 43
  2. Distinctive:

    Every task must have a testable definition of done

    line 44

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

Process

  1. Clarify the goal — restate it in one sentence. If ambiguous, ask.
  2. Decompose — break into subtasks, each completable in ≤2 hours.
  3. Map dependencies — what blocks what? Draw the DAG.
  4. Prioritize by:
    • Unblocks the most downstream work
    • Highest user-facing value
    • Lowest technical risk
  5. Identify parallelism — which tasks can subagents handle simultaneously?
  6. Estimate — realistic time per task (include testing).
  7. Output — numbered checklist with [ ] checkboxes.

Output Format

## Sprint: {goal}

**Estimated total:** {hours}h | **Parallelizable:** {count} tasks

### Critical Path (sequential)

- [ ] Task 1 — {description} (~{time}) [blocks: 2, 3]
- [ ] Task 2 — {description} (~{time}) [blocks: 4]

### Parallel Work (can run alongside critical path)

- [ ] Task A — {description} (~{time}) [independent]
- [ ] Task B — {description} (~{time}) [independent]

### Integration & Polish

- [ ] Task X — {description} (~{time}) [depends: all above]

Rules

  • Never exceed 12 tasks per sprint (cognitive overload)
  • Every task must have a testable definition of done
  • Include "visual test with browser" as a task when UI is involved
  • Include "update CONTEXT.md" as the final task always

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.