requirements-refiner

To refine vague ideas into clear requirements, provide your rough concept to the workflow, which detects context across learning, personal, internal, B2B, and B2C, then outputs structured MUST and SHOULD requirements along with a domain brief.

The best way to start a DDD workshop pipeline is using an entrance refinement process that evaluates your rough prompt with an 8-question agent self-diagnosis, identifying unknown domain areas for optional web research or user interviews before generating a unified context document.

Yes, you can use requirements refinement for both B2B and B2C product contexts. The process explicitly detects and categorizes inputs across learning, personal, internal, B2B, and B2C environments to ensure the generated domain briefs match your specific business context.

To identify missing requirements and edge cases in a PRD, the refinement process resolves ambiguities, edge cases, implicit assumptions, and contradictions through a one-to-one question queue, leaving a list of remaining undefined items for subsequent stages.

Agent self-diagnosis handles unfamiliar domains during requirements gathering by publicly performing an 8-question core domain understanding check, then filling identified knowledge gaps with optional web research or user interviews to solidify the domain brief.