tomevault-io MoSCoW Prioritization
- Must have: Critical requirements without which the project fails
- Should have: Important but not critical; workarounds exist
- Could have: Nice-to-have features; include if time permits
- Won't have (this release): Explicitly out of scope
Requirements Quality Criteria Every requirement must be:
- Specific: Clear, unambiguous language
- Measurable: Verifiable through testing or observation
- Achievable: Technically feasible within constraints
- Relevant: Aligned with project goals
- Traceable: Linked to a business need or user story
Version Control
- Track all changes with version numbers (MAJOR.MINOR)
- MAJOR: Scope changes, new features, removed requirements
- MINOR: Clarifications, refinements, acceptance criteria updates
- Maintain changelog at top of document
Document Structure All requirements.md files follow this structure:
- Project Overview
- Stakeholders and Constraints
- Functional Requirements
- Non-Functional Requirements
- Technical Requirements
- Acceptance Criteria
- Out of Scope
- Changelog
- Create new requirements - Start a new requirements.md from scratch
- Update requirements - Modify existing requirements as scope changes
- Review requirements - Audit requirements for completeness and quality
Type a number, keyword, or skip to dismiss.
Note: This skill blocks on user input. If triggered unintentionally, type skip or dismiss to cancel.
If the user types skip or dismiss, briefly confirm cancellation (e.g., "requirements-generator cancelled.") and end the skill without running any workflow.
If the input does not clearly match any option above and is not "skip" or "dismiss", respond: "requirements-generator was triggered but your input didn't match a workflow. Options: 1-3 (listed above). Type skip to dismiss."
After reading the workflow, follow it exactly.
Templates:
- requirements-template.md
- requirements-questions-template.md (ADR/RFC-style decision capture)
Checklists:
- intake-checklist.md
- quality-checklist.md
Patterns:
- requirement-patterns.md
- requirements-questions-guide.md (How to create effective decision documents)
| Workflow | Purpose |
|---|---|
| create-requirements.md | Gather info and create new requirements.md |
| update-requirements.md | Modify requirements with proper versioning |
| review-requirements.md | Audit requirements for completeness |
- Valid version number and changelog
- All sections from document structure
- Every requirement prioritized (MoSCoW)
- Acceptance criteria for all Must/Should requirements
- Technical constraints identified
- Out-of-scope items explicitly listed
Optional REQUIREMENTS_QUESTIONS.md has:
- Open decisions prioritized (BLOCKER/HIGH/MEDIUM/LOW)
- Each question with clear context and options
- Recommended defaults for non-blockers
- Summary showing what blocks development vs can defer
- Response template for stakeholder input
Converted and distributed by TomeVault — claim your Tome and manage your conversions.