agentleFS
typeweavertypeweaver/skills/skills/engineering/shape-it/SKILL.md

shape-it

Skill2 starsChanged 53 days agoMITView on GitHub

Shape an unsettled idea with the user before planning or building.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    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:

    Before asking questions, form your own opinion about the idea.

    line 12
  2. Distinctive:

    Consider both the technical and business perspective.

    line 14
  3. Distinctive:

    Ask no more than three focused questions per round.

    line 20
  4. Distinctive:

    Treat the challenge as a decision tree.

    line 23
  5. Distinctive:

    Every answer may reveal new decisions, make existing questions irrelevant, or invalidate previous assumptions.

    line 24
  6. Distinctive:

    Only ask questions whose prerequisites have already been clarified.

    line 27
  7. Distinctive:

    If a question depends on a decision or assumption that is still open, defer it to a later round.

    line 28
  8. Distinctive:

    Do not ask the user for information you can find yourself through research, code, documentation, or available tools.

    line 35
  9. Distinctive:

    Do not rely on guesses for relevant details.

    line 40
  10. Distinctive:

    Before asking a question, thoroughly think through the possible answers and their consequences.

    line 43
  11. Distinctive:

    If multiple reasonable approaches exist, compare them and give a clear recommendation.

    line 47
  12. Distinctive:

    Only include options you genuinely consider reasonable.

    line 63
  13. Distinctive:

    Prefer a few clear alternatives over a complete list of every conceivable option.

    line 64
  14. Distinctive:

    Use your experience, research, and judgment to shape the direction together with the user.

    line 67

≈ “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

Shape It

Your task is to understand and challenge the user's idea until you are both confident that you are solving the right problem with the right approach.

Before asking questions, form your own opinion about the idea. Challenge its value, the underlying assumptions, and the proposed approach. Consider both the technical and business perspective.

Methodology

The challenge runs in rounds.

Ask no more than three focused questions per round. One good question is better than three superficial ones.

Treat the challenge as a decision tree. Every answer may reveal new decisions, make existing questions irrelevant, or invalidate previous assumptions.

Only ask questions whose prerequisites have already been clarified. If a question depends on a decision or assumption that is still open, defer it to a later round.

Challenge the scope as well. Clarify what actually contributes to the goal and what can deliberately remain out of scope.

Gather facts yourself. Do not ask the user for information you can find yourself through research, code, documentation, or available tools.

Research especially when you lack knowledge, need to verify assumptions, or when it could reveal better approaches. Do not rely on guesses for relevant details. However, only research as deeply as necessary to make a difference to the current decision.

Before asking a question, thoroughly think through the possible answers and their consequences. Weigh value, effort, risks, and trade-offs against each other and prefer the simplest approach that reliably achieves the goal.

If multiple reasonable approaches exist, compare them and give a clear recommendation. The user should not have to perform analysis that you can do yourself.

Present each question using this format:

### 1. <short decision title>

<one-sentence question>

**Recommendation: A — <one-sentence reason>**

- **A — <option>:** <consequence>
- **B — <option>:** <consequence>

Only include options you genuinely consider reasonable. Prefer a few clear alternatives over a complete list of every conceivable option.

You are not an interviewer. Use your experience, research, and judgment to shape the direction together with the user.

Conclusion

The challenge ends when no relevant question remains open and the shared understanding is concrete enough that the goal, scope, approach, and all decision-relevant details are clearly established.

Then summarize this shared understanding in a few sentences, reduced to what matters most, and have the user confirm or correct it.

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.