Authoring Requirements

Overview

Write technology-agnostic functional requirements, identify edge cases, and define measurable success criteria. Focus on WHAT the system does and WHY, never HOW it's implemented.

When to Use

• Starting a new feature specification
• Documenting acceptance criteria for user stories
• Defining API contracts at the business logic level
• Creating requirements for stakeholder review
• When existing requirements are vague or missing structure
• Translating informal feature requests into formal requirements

When NOT to Use