agentleFS
lglucaslglucas/ai-dev-operating-system/.claude/skills/sprint-management/SKILL.md

sprint-management

Skill12 starsChanged 48 days agoMITView on GitHub

Manage the sprint lifecycle — open a sprint, maintain the sprint branch and docs, close it, update the changelog, and prepare tags. Powers /sprint-start, /sprint-plan and /sprint-close. Use when the user says "vamos começar a sprint", "fecha a sprint", "o que tá nessa sprint?", "terminei essa etapa", "qual o próximo ciclo?".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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. Distinctive:

    Ensure main is clean and up to date.

    line 11
  2. Very specific:

    Create docs/sprints/sprint-XX-topic.md from template.

    line 13
  3. Distinctive:

    Update project constitution/current sprint metadata.

    line 14
  4. Distinctive:

    Use feature branches for isolated work.

    line 19
  5. Distinctive:

    Keep sprint doc updated with scope changes and delivered work.

    line 21
  6. Distinctive:

    Use session logs for important decisions.

    line 22
  7. Distinctive:

    Run tests and quality gates.

    line 28
  8. Distinctive:

    Update sprint doc with final status and retrospective.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Management

Open sprint

  1. Confirm sprint number, theme, duration, and objectives.
  2. Ensure main is clean and up to date.
  3. Create sprint-XX-topic branch.
  4. Create docs/sprints/sprint-XX-topic.md from template.
  5. Update project constitution/current sprint metadata.
  6. Commit kickoff.

During sprint

  • Use feature branches for isolated work.
  • Merge into sprint branch.
  • Keep sprint doc updated with scope changes and delivered work.
  • Use session logs for important decisions.
  • Regenerate CODEMAP.md with every code change — node scripts/codemap.js. The map records each file's line count, so editing a mapped file is usually enough to make --check fail. Commit the map together with the change.

Close sprint

  1. Confirm all intended work is merged or explicitly deferred.
  2. Run tests and quality gates.
  3. Invoke coordinator review.
  4. Invoke adversarial review for meaningful releases.
  5. Update changelog.
  6. Regenerate the codemap — node scripts/codemap.js — and commit it if it changed.
  7. Update sprint doc with final status and retrospective.
  8. Merge sprint branch into main.
  9. Tag release.

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.