scenario-alignment

To generate a non-technical PRD from a feature idea, align business understanding with user scenarios and existing code. This process clarifies decision branches affecting product scope and outputs a concise document focusing on user goals and product decisions.

The best way to align business requirements with existing code and harness is through interview-based alignment. This method iteratively clarifies business intent from bugs or plans, matching decision trees against current project constraints to produce refined business documentation.

Yes, you can use bug descriptions and business materials as input for product documentation generation. The alignment process handles various user inputs, extracting core business intent and aligning it with current code to produce a clear, non-technical PRD.

Yes, you need project constraints and codebase access to clarify user requirements effectively. Accessing the codebase allows the alignment process to accurately map user requirements against existing harness capabilities, ensuring the generated PRD reflects actual product scope decisions.

To clarify complex feature ideas into concise business documents, iteratively align the core business intent with decision trees affecting product scope. This extracts user goals and generates a refined, non-technical business PRD document without technical implementation details.

You should use an interview-based approach for user requirement analysis when presented with complex feature ideas or plans. It iteratively clarifies business understanding by identifying decision branches, ensuring the final PRD accurately reflects user scenarios and product scope.