How do I install the Requirements Definition skill?

Run npx skillmds@latest add tomevault-io/requirements-definition in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Requirements Definition safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Requirements Definition?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Requirements Definition free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Requirements Definition?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Requirements Definition by tomevault-io

Name: Requirements Definition
Author: tomevault-io

Requirements Definition

This skill should be used when the user asks to "define requirements", "create specification", "clarify requirements", "write requirements document", or mentions requirement analysis. Provides comprehensive requirements definition methodology. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Security:

All data encrypted at rest using AES-256
JWT tokens for authentication

Maintainability:

Test coverage >= 80%
Documentation for all public APIs

Impact Scope:

All components making API calls
Testing utilities need to mock React Query

Objectivity (0-100): Evidence-based vs. assumption-based

90-100: All requirements verified through investigation
70-89: Most requirements verified, some assumptions documented
50-69: Mix of verification and assumptions
Below 50: Mostly assumptions, needs more investigation

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: requirements-definitiondescription: This skill should be used when the user asks to "define requirements", "create specification", "clarify requirements", "write requirements document", or mentions requirement analysis. Provides comprehensive requirements definition methodology. Use when this capability is needed.---<purpose>Provide structured methodology for requirements definition, ensuring comprehensive specification before implementation.</purpose><tools><tool name="Glob">Directory structure analysis</tool><tool name="get_symbols_overview">Symbol analysis via Serena</tool><tool name="Grep">Keyword search</tool><tool name="find_symbol">Symbol search via Serena</tool><tool name="find_referencing_symbols">Dependency mapping via Serena</tool><tool name="Read">Specific content details</tool><tool name="Context7">Latest API documentation and best practices</tool></tools><patterns><pattern name="investigation_workflow"><description>Sequential investigation process for gathering requirements context</description><steps><step>Directory structure analysis using Glob</step><step>Symbol analysis using get_symbols_overview</step><step>Keyword search using Grep or find_symbol</step><step>Dependency mapping using find_referencing_symbols</step><step>Specific content details using Read</step><step>Latest API documentation using Context7</step></steps></pattern><pattern name="question_scoring"><description>Score each question by these criteria (1-5 each) to prioritize requirement clarification</description><criteria><criterion name="design_branching">How much does the answer affect design direction?</criterion><criterion name="irreversibility">How difficult to change after implementation?</criterion><criterion name="investigation_impossibility">Cannot be determined through code investigation alone?</criterion><criterion name="effort_impact">How much does it affect implementation effort?</criterion></criteria><note>Present high-score questions first. Do not proceed without clear answers to critical questions (score >= 15)</note><example>Question: "Should we use TypeScript's strict mode?"- Design Branching: 5 (affects all type decisions)- Irreversibility: 4 (hard to change later)- Investigation Impossibility: 3 (requires policy decision)- Effort Impact: 4 (affects development effort)Total: 16 (critical - must answer before proceeding)</example></pattern><pattern name="question_classification"><description>Categories of questions that arise during requirements definition</description><types><type name="spec_confirmation">Confirming existing behavior or constraints</type><type name="design_choice">Choosing between valid alternatives</type><type name="constraint">Technical or business limitations</type><type name="scope">Boundaries of implementation</type><type name="priority">Order and importance of features</type></types><example>- Spec Confirmation: "Does the API return null or empty array for no results?"- Design Choice: "Should we use REST or GraphQL?"- Constraint: "Must support IE11 browsers?"- Scope: "Should admin features be included in v1?"- Priority: "Which feature should be implemented first?"</example></pattern><pattern name="functional_requirements"><description>Format functional requirements with clear identifiers and acceptance criteria</description><example>FR-001: User AuthenticationPriority: mandatory- Users must be able to log in with email and password- Session must expire after 24 hours of inactivity- Failed login attempts must be rate-limited (max 5 per hour)</example></pattern><pattern name="non_functional_requirements"><description>Specify measurable non-functional requirements across key dimensions</description><example>Performance:- API response time < 200ms for 95th percentile- Support 1000 concurrent usersSecurity:- All data encrypted at rest using AES-256- JWT tokens for authenticationMaintainability:- Test coverage >= 80%- Documentation for all public APIs </example> </pattern><pattern name="technical_specifications"><description>Document design policies, patterns, and key decisions with rationale</description><example>Design Decision: Use React Query for data fetchingRationale:- Built-in caching reduces API calls- Automatic background refetching- TypeScript support- Widely adopted in existing codebaseImpact Scope:- All components making API calls- Testing utilities need to mock React Query </example> </pattern><pattern name="requirement_quality_metrics"><description>Quantitative measures of requirement quality</description><example>Feasibility (0-100): Technical achievability given constraints- 90-100: Straightforward with existing tools- 70-89: Requires some research or new libraries- 50-69: Significant technical challenges- Below 50: May need architecture changesObjectivity (0-100): Evidence-based vs. assumption-based- 90-100: All requirements verified through investigation- 70-89: Most requirements verified, some assumptions documented- 50-69: Mix of verification and assumptions- Below 50: Mostly assumptions, needs more investigation </example> </pattern> </patterns><output><format><summary>- One-sentence request description- Background and context- Expected outcomes</summary><current_state>- Existing system description- Technology stack- Relevant patterns and conventions</current_state><functional_requirements>Format: FR-XXX (FR-001, FR-002, ...)- Priority: mandatory or optional- Clear acceptance criteria</functional_requirements><non_functional_requirements>- Performance: response time, throughput- Security: authentication, authorization, data protection- Maintainability: code quality, documentation</non_functional_requirements><technical_specifications>- Design policies and patterns- Impact scope analysis- Key design decisions with rationale</technical_specifications><metrics>- Feasibility (0-100): Technical achievability- Objectivity (0-100): Evidence-based specification</metrics><constraints>- Technical constraints: platform, language, framework- Operational constraints: deployment, maintenance</constraints><test_requirements>- Unit test coverage expectations- Integration test scenarios- Acceptance criteria verification</test_requirements><task_breakdown>- Dependency graph: task dependencies and execution order- Phased tasks: files to modify/create, overview of changes, dependencies- Execute handoff: key decisions, reference implementations, constraints</task_breakdown></format></output><rules priority="critical"><rule>Never proceed without clear answers to critical questions (score >= 15)</rule><rule>All requirements must be verifiable and measurable</rule><rule>Distinguish mandatory from optional requirements</rule></rules><rules priority="standard"><rule>Present high-score questions first in requirement discussions</rule><rule>Document assumptions explicitly when requirements are unclear</rule><rule>Include rationale for key design decisions</rule><rule>Map requirements to test scenarios</rule></rules><best_practices><practice priority="critical">Always investigate current state before defining requirements using Serena's symbol-level operations</practice><practice priority="critical">Score questions using the 4-criteria scoring system and prioritize high-score questions (>= 15)</practice><practice priority="critical">Clearly distinguish mandatory from optional requirements with explicit rationale</practice><practice priority="high">Document all assumptions when requirements are unclear or incomplete</practice><practice priority="high">Map each requirement to specific test scenarios for verification</practice><practice priority="high">Include rationale for key design decisions in technical specifications</practice><practice priority="medium">Use Context7 to verify latest library documentation and best practices</practice><practice priority="medium">Create dependency graphs showing task execution order</practice></best_practices><anti_patterns><avoid name="vague_requirements"><description>Requirements that are unclear or unmeasurable</description><instead>Write specific, testable requirements with clear acceptance criteria</instead></avoid><avoid name="implementation_details"><description>Specifying implementation details instead of requirements</description><instead>Describe what needs to be achieved, not how to implement it</instead></avoid><avoid name="skipping_investigation"><description>Writing requirements without investigating existing code</description><instead>Always investigate current state before defining requirements</instead></avoid><avoid name="missing_constraints"><description>Not identifying technical or operational constraints</description><instead>Explicitly document all constraints that affect implementation</instead></avoid><avoid name="undefined_priorities"><description>Treating all requirements as equally important</description><instead>Clearly mark requirements as mandatory or optional with rationale</instead></avoid></anti_patterns>---> Converted and distributed by [TomeVault](https://tomevault.io/claim/mtaku3) — claim your Tome and manage your conversions.

Frequently asked questions