represent-section

To define product section specifications, you can use a guided conversational process to outline user actions, displayed information, and user flows. This approach ensures clarity and generates a structured spec.md file for each section before implementation begins.

The best way to gather requirements for a product section is through iterative conversational refinement. This process focuses on detailing what users can do, what data they see, and navigation paths, producing a structured specification document for development.

Yes, you can iteratively refine user stories and section requirements. The specification process facilitates a conversational approach to gather and adjust requirements, allowing you to progressively clarify user actions and flows before finalizing the spec.md file.

No specific dependencies are required to generate a section spec.md file. The specification process operates independently to guide you through defining user interactions and information displays, outputting the structured document without needing external tools.

A product section specification should include user actions, key displayed information, and user flows. Defining these elements ensures a focused development process by clarifying exactly what users can do and see within that specific section.