agentleFS
Gaurav890Gaurav890/everything-agentic-engineering/.claude/skills/user-needs/SKILL.md

user-needs

Skill1 starsChanged 2 months agoMITView on GitHub

Identify and layer functional, emotional, social, and underlying user needs. Use after discovery or whenever a requirement is feature-led, a problem statement embeds a solution, or the team needs to distinguish user outcomes from requested functionality.

The file

Files
SKILL.md

User needs

For each relevant user/context, separate:

  • functional need: progress the user must make;
  • emotional need: how the user needs to feel;
  • social need: how the user wants to be perceived or coordinate;
  • underlying motivation: why the outcome matters;
  • evidence, current workaround, constraint, and failure consequence.

Rewrite solution-shaped statements as outcome-oriented needs. Rank by importance and confidence. Map proposed features to needs and flag features with no supported need. Preserve uncertainty rather than inventing research.

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.