agentleFS
xiongxianfeixiongxianfei/skillsmith/skills/start-of-work/SKILL.md

start-of-work

Skill2 starsChanged 14 days agoMITView on GitHub

Helps the person start any task, project, or decision well, before doing the work. Asks the most important questions first, lists assumptions and unknowns, offers 3-5 approaches with trade-offs, then breaks the chosen approach into steps with one clear first action. Use this skill whenever the user says "help me start", "help me plan", "where do I begin", "how should I approach", "I have a vague idea", or brings a new task, project, or decision with an unclear goal, even if they don't ask for a plan. Do NOT use it to write the final deliverable itself.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    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:

    Run three phases in order.

    line 10
  2. Distinctive:

    Do not give options or steps until this phase is done.

    line 14
  3. Distinctive:

    Ask the 2-3 most important questions only, one at a time.

    line 16
  4. Distinctive:

    Use multiple choice when possible, and always allow "not sure".

    line 20
  5. Distinctive:

    If an answer is vague, ask one follow-up, then move on.

    line 21
  6. Distinctive:

    Ask: "Is this right?" and wait for confirmation or correction before Phase 2.

    line 27
  7. Distinctive:

    Ask which approach they want (or a mix).

    line 37
  8. Distinctive:

    Keep every phase short. This skill is about starting, not doing.

    line 48
  9. Distinctive:

    Do not write full drafts, detailed outlines, or code.

    line 49
  10. Distinctive:

    If the goal is already clear, say so briefly and go to Phase 2.

    line 50
  11. Distinctive:

    If the person wants to skip ahead, let them, and state your assumptions.

    line 51
  12. Distinctive:

    Use plain language, and match the person's language.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Start of Work

Help the person begin well. The person does the real work; this skill clarifies, offers options, and plans. Never write the final deliverable (full draft, full outline, finished code).

Run three phases in order. Skip a phase only if the person has clearly already done it.

Phase 1: Clarify (always first)

Do not give options or steps until this phase is done.

  1. Ask the 2-3 most important questions only, one at a time. Priority order:
    • What is the goal, and what does "done" look like?
    • Who is it for?
    • What constraints exist (time, tools, budget, must-avoid)?
  2. Use multiple choice when possible, and always allow "not sure".
  3. If an answer is vague, ask one follow-up, then move on.
  4. Skip any question the person has already answered. Never ask more than 3 questions in total.
  5. Summarize in this format:
    • Goal: 1-2 sentences
    • Assumptions: what you are taking as true
    • Unknowns: what is still unclear; mark the ones that could change the plan
  6. Ask: "Is this right?" and wait for confirmation or correction before Phase 2.

Phase 2: Options

  1. Give 3-5 genuinely different approaches, not variations of one idea.
  2. For each approach:
    • Summary: one line
    • Pros / Cons: short
    • Best when: the situation where it wins
  3. Recommend one and say why in 1-2 sentences. The person decides.
  4. Ask which approach they want (or a mix).

Phase 3: Breakdown

  1. For the chosen approach, list 4-8 steps in order.
  2. Mark one First action that takes under 15 minutes.
  3. Flag steps that need the person's own judgment or decision.
  4. Note any step that depends on an Unknown from Phase 1.

Rules

  • Keep every phase short. This skill is about starting, not doing.
  • Do not write full drafts, detailed outlines, or code.
  • If the goal is already clear, say so briefly and go to Phase 2.
  • If the person wants to skip ahead, let them, and state your assumptions.
  • Use plain language, and match the person's language.
  • End with the first action, not a summary.

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.