agentleFS
vokakovokako/AIDLC-skills/skills/aidlc-requirements/SKILL.md

aidlc-requirements

Skill4 starsChanged 6 months agoNo licenceView on GitHub

AI-DLC Requirements Analysis only — produce a structured requirements document with intent analysis, functional and non-functional requirements, and clarifying-question gates. Use when the user wants a requirements document on its own without the full AIDLC workflow. Trigger on phrases like "gather requirements for X", "I need a requirements doc", "what are the requirements for this feature?", "let's do requirements before anything else", "write functional and non-functional requirements", "produce a requirements.md". For requirements + user stories + design + code, use `aidlc-inception` or full `aidlc`. For just user stories on top of existing requirements, use `aidlc-user-stories`.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.