analyze-requirements
Skill16 starsChanged 38 days agoMITView on GitHub
Read the spec/SRS and produce a structured requirement analysis — the analysis stage of the standard pipeline (workflow.yaml).
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- be-fe-security-auditSkill
- commit-deploy-logSkill
- deep-researchSkill
- deploy-to-testSkill
- evidence-bundleSkill
- fanSkill
- fix-and-verifySkill
- impact-reviewSkill
- implement-changeSkill
- qa-gateSkill
- run-affected-testsSkill
- verify-implementationSkill
- verify-requestSkill
The file
Files
analyze-requirements
The analysis node of the DAG (contracts/workflow.yaml). Run by the
analyst (planning profile), optionally with architect for design-heavy
changes. Its output artifacts/analysis/{pipeline_id}-analysis.md is the sole
hand-off to implement-change.
Discipline: ground every claim in the real repo (read the files); mark
assumptions explicitly rather than guessing; numbered acceptance criteria here
become the checklist the verify-implementation stage scores against.
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.