Kiro.

First agree on the behavior of the function

Specs in Kiro is useful when a task is easy to describe in one sentence but lacks the detail needed for implementation. A request to add order export leaves open questions about fields, file size, and access. In Kiro, draft the requirements, review the design, and divide the work into tasks. Open each document before changing the code. It is easier to fix a missing condition in the spec before it spreads across the project.

The checkable requirement describes the input and the observed result. In the case of unloading, it is more useful to name the limit of the number of lines and behavior with a blank result than to limit yourself to asking for support for large tables.

Exporting orders as a training task

Prepare an order example, a list of acceptable fields and the role to which export is available. Ask for a separate description of the empty sample processing. If the table is going to be opened in the spreadsheet editor, specify the processing of values that the program can take as formulas. Then check if there is a separate task and test for this.

When finished, compare the downloaded file with the specification. The order of the columns, the separator and the absence of unnecessary personal data can be checked on a small sample, without unloading the real base.

Project rules and events

Kiro provides ongoing instructions for the project and Hooks for action on events. General rules should be separated from the requirements of a specific function. For example, the test run command will be useful in the following tasks, and the set of columns applies only to current exports.

Suitable tasks

• Describe the requirements for a new function before changes
• Break up a major edit into tasks to check