Requirements Catalog for TeamFlow

Background

Your team has finished the product discovery phase for TeamFlow, a new web-based task management platform. The product owner has written a vision document capturing the intended users, key features, and quality goals for the system. You can find this document at docs/vision.md.

Before development can begin, the engineering team needs a formal requirements catalog that structures the vision into actionable, verifiable requirements. The catalog will be used by developers to scope individual features, by QA to design test cases, and by the project manager to track delivery status.

A standards document is available in the project's references folder — consult it for the required ID formats, NFR categories, allowed data types, and quality checks to apply before finalizing the catalog.

Your Task

Read docs/vision.md and produce a complete requirements catalog saved at docs/requirements.md.

The catalog should cover:

• Functional requirements derived from the features described in the vision
• Non-functional requirements derived from the quality goals described in the vision
• Constraints derived from the technical and delivery constraints in the vision

Each requirement type must be presented in its own dedicated Markdown table with appropriate columns. Every requirement row must be fully filled in — no empty cells.

Once drafted, review the catalog for quality before saving the final version: check that every requirement is clear, testable, and unambiguous, that all identifiers are unique across the document, and that every row's status is recorded.