agentleFS
Sign inStart free
saitarrunsaitarrun/Devforge-ai/skills/requirements/SKILL.md

requirements

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story estimation".

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-browser.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    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:

    Always ask these questions before starting work:

    line 65

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

Skill: Requirements & User Stories (INVEST)

INVEST Criteria — Making Stories Actionable

A well-written user story is INVEST-compliant:

  • Independent: Story doesn't depend on another story (can be built in any order)
  • Negotiable: Details can be discussed and refined (not cast in stone)
  • Valuable: Delivers value to the end user (not just internal plumbing)
  • Estimable: Engineer can estimate size (2-13 story points)
  • Small: Fits in a single sprint (1-2 weeks max)
  • Testable: Acceptance criteria are clear and provable

Story Format

## User Story: [Feature Name]

As a [role/persona]
I want to [action/capability]
So that [business value/outcome]

### Acceptance Criteria
- Given [precondition]
  When [action]
  Then [observable result]

### Edge Cases & Questions
- Q: What happens if [scenario]?
- Q: Should we support [case]?

### Definition of Done
- [ ] Code written and reviewed
- [ ] Acceptance criteria tests pass
- [ ] Documentation updated
- [ ] Performance tested (if relevant)
- [ ] Security review passed (if relevant)

Story Estimation

  • Small (2-3 pts): Can be done in a day, low complexity, well-understood
  • Medium (5 pts): Takes 2-3 days, some unknowns, requires design
  • Large (8 pts): Takes full sprint, many unknowns, high risk
  • Too Large (13+ pts): Break into smaller stories

Common Pitfalls

PitfallBad ExampleGood Example
Not independent"Add payment form" depends on "Add payment backend""Add payment form UI" + "Add payment API" (can be mocked)
Not valuable"Refactor database layer""Enable payments via Stripe"
Not testable"Code should be fast""Page load <2 seconds on 3G"
Too large"Build entire user profile system""User can upload profile photo"
Unclear"Handle edge cases""Given missing email, show validation error"

Ambiguity Detection

Always ask these questions before starting work:

  1. Scope: Are there other features needed first? Any dependencies?
  2. Success: How do we know this is done? What's the test?
  3. Users: Who specifically benefits? All users or subset?
  4. Edge Cases: What happens if user has no data? Empty input? Slow connection?
  5. Performance: Are there speed requirements?
  6. Integration: Does this affect other features? APIs? Databases?

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.

Check your setup, free