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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-overviewSkill
- blog-publisherSkill
- c4-architectureSkill
- city-attraction-researchSkill
- city-itinerary-builderSkill
- city-view-modelSkill
- communicatorSkill
- doctorSkill
- editorSkill
- email-writerSkill
- eyeglasses-selectionSkill
- fitness-coachSkill
- flashcard-generatorSkill
- hairstyle-selectionSkill
- journalingSkill
- language-tutorSkill
- local-food-and-dining-researchSkill
- nvcSkill
- oscp-coachSkill
- purchase-comparisonSkill
- quiz-generatorSkill
- restaurant-menu-advisorSkill
- study-plannerSkill
- task-writerSkill
- travel-plannerSkill
- travel-storytelling-guideSkill
- trip-expense-trackerSkill
- vocabulary-masterySkill
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
- Distinctive: line 10
Run three phases in order.
- Distinctive: line 14
Do not give options or steps until this phase is done.
- Distinctive: line 16
Ask the 2-3 most important questions only, one at a time.
- Distinctive: line 20
Use multiple choice when possible, and always allow "not sure".
- Distinctive: line 21
If an answer is vague, ask one follow-up, then move on.
- Distinctive: line 27
Ask: "Is this right?" and wait for confirmation or correction before Phase 2.
- Distinctive: line 37
Ask which approach they want (or a mix).
- Distinctive: line 48
Keep every phase short. This skill is about starting, not doing.
- Distinctive: line 49
Do not write full drafts, detailed outlines, or code.
- Distinctive: line 50
If the goal is already clear, say so briefly and go to Phase 2.
- Distinctive: line 51
If the person wants to skip ahead, let them, and state your assumptions.
- Distinctive: line 52
Use plain language, and match the person's language.
≈ “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.
Files
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.
- 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)?
- Use multiple choice when possible, and always allow "not sure".
- If an answer is vague, ask one follow-up, then move on.
- Skip any question the person has already answered. Never ask more than 3 questions in total.
- 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
- Ask: "Is this right?" and wait for confirmation or correction before Phase 2.
Phase 2: Options
- Give 3-5 genuinely different approaches, not variations of one idea.
- For each approach:
- Summary: one line
- Pros / Cons: short
- Best when: the situation where it wins
- Recommend one and say why in 1-2 sentences. The person decides.
- Ask which approach they want (or a mix).
Phase 3: Breakdown
- For the chosen approach, list 4-8 steps in order.
- Mark one First action that takes under 15 minutes.
- Flag steps that need the person's own judgment or decision.
- 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.
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
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.

