agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/delivery/planning/SKILL.md

planning

Skill19 starsChanged 2 months agoMITView on GitHub

WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on Best

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 2

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

    Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.

    line 10
  2. Distinctive:

    Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them.

    line 15
  3. Very specific:

    If a work item is being created or refined, pair this with work-item and the relevant atomic skill.

    line 16

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

Planning and Estimation (WHAT)

Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.

Default guardrails

  1. Apply output-handshake before producing any final planning artifact: ask where it should live and confirm human review.
  2. Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them. Otherwise use this default.
  3. If a work item is being created or refined, pair this with work-item and the relevant atomic skill.

What to check

  • Scope and goal are clear.
  • Work is broken down into manageable items; anything estimated at 5+ points should be considered for splitting.
  • Acceptance criteria and dependencies are known enough for estimation.
  • Estimation technique is explicit: planning poker, T-shirt sizing, Fibonacci, or the team override.
  • Capacity considers availability, holidays, meetings, focus factor, dependencies, and historical velocity.

References

  • references/default-template.md - default planning and capacity template
  • references/example-sprint-planning.md — example sprint planning with work item breakdown, capacity, and risk assessment
  • work-item - work item hierarchy and creation
  • clickup-cli - task updates after user approval

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.

Reviews can't be read right now.

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