agentleFS
Sign inStart free
jezwebjezweb/vite-flare-starter/skills/plan-task/SKILL.md

plan-task

Skill49 starsChanged 3 months agoMITView on GitHub

Break a goal into a clear sequence of actionable steps with dependencies and estimated effort. Use when the user describes something they want to accomplish and asks for a plan, breakdown, or "how do I...".

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 5

    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:

    Start with a verb (Create, Send, Review, Decide, Test)

    line 22
  2. Distinctive:

    Don't generate more than 10 top-level steps — that's a sign you should chunk into phases

    line 46
  3. Distinctive:

    Don't include "research the problem" as a step (that's planning, not the work)

    line 47
  4. Distinctive:

    Don't sequence things that can run in parallel just because they "feel" sequential

    line 48
  5. Distinctive:

    Don't end without a clear first step the user can take right now

    line 49

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

Plan Task

When to use

  • "Help me plan X"
  • "How do I do Y?"
  • "What's the best way to approach Z?"
  • "Break this down for me"

Steps

  1. Clarify the goal — restate it in one sentence. If the goal is fuzzy ("improve my website"), use ask_questions to nail down:
    • What does "done" look like?
    • Hard constraints (deadline, budget, must/must-not)
    • Resources available (time, skills, tools)
  2. Break into steps — produce 5-10 concrete steps. Each step should:
    • Start with a verb (Create, Send, Review, Decide, Test)
    • Be small enough to complete in one session
    • Have a clear "done" state
  3. Identify dependencies — note which steps must happen before others. Don't over-sequence — most steps can run in parallel.
  4. Estimate effort for each step (S/M/L or hours, depending on context).
  5. Display as progress tracker — use show_progress with all steps marked upcoming. The user can update status as they work.
  6. Add a critical path note — one sentence: which 1-2 steps are most likely to delay everything if they slip?
  7. Offer to act via offer_choices:
    • "Start with step 1"
    • "Save this plan to my files"
    • "Add a deadline"
    • "Adjust the steps"

Style

  • Concrete actions, not abstractions ("Draft the brief" not "Think about scope")
  • Right level of detail — for a 1-day task, ~5 steps; for a multi-week project, ~10 with sub-steps
  • Realistic estimates — pad for uncertainty, especially first steps

What not to do

  • Don't generate more than 10 top-level steps — that's a sign you should chunk into phases
  • Don't include "research the problem" as a step (that's planning, not the work)
  • Don't sequence things that can run in parallel just because they "feel" sequential
  • Don't end without a clear first step the user can take right now

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