draft-requirements

To convert project ideas into structured requirements documentation, provide your project concept and discussion notes. The system drafts a formal master requirements document using a GOAL/GUARD framework to ensure testability and traceability.

The GOAL and GUARD framework structures requirements by defining specific feature-level objectives (GOALs) and cross-cutting design constraints (GUARDs). It transforms scattered concepts into verifiable specifications with source traceability.

Yes, you can extract requirements from existing discussion notes and documents. The system processes provided concepts and text to generate feature-level GOALs and master requirements, referencing original sources for traceability.

To define cross-cutting constraints for design handoffs, the system generates GUARDs from your project concepts. These GUARDs establish testable dependencies and limitations, facilitating structured transitions to design documentation.

The best way to structure feature-level goals in a master requirements doc is using a hierarchical GOAL system (e.g., GOAL-1.1, GOAL-1.2). This creates a verifiable specification linked to overarching GUARD constraints.