frd-write

Generate a feature requirements document using a structured three-section format: Overview, Terminology, and Requirements. This standardizes product specifications and ensures engineering handoffs are clear, testable, and ready for implementation.

Create testable acceptance criteria by guiding the generation of atomic, verifiable ACs using a standardized ID convention (REQ/AC). This bridges product intent and technical validation, ensuring every requirement has a specific, checkable condition.

The best way to align new feature requirements is context-aware discovery, which integrates with existing project documentation like personas and technical constraints. This ensures new features match the established product surface and technical boundaries.

Yes, you can maintain consistency across feature hierarchies and sub-features. The system operates within existing project directories to automatically standardize requirement IDs, ensuring structured documentation across the entire project.

Yes, it operates without external dependencies. The system uses internal assets to validate user stories and acceptance criteria against project-specific personas and technical constraints, ensuring testability and alignment entirely within your project directory.