One requirement, from sentence to merged code

1. One requirement from the business. Scroll to watch nTra take this sentence to a merged pull request, with a person signing off at every step.
2. nTra asks what people forget. The sentence becomes a conversation. nTra works through its questions on carry-over caps, approvers, notifications and security, and writes the brief as you answer. It never overwrites what you said.
3. The business approves the brief. Nothing is planned or built before this. From here the thread carries a signed-off requirement.
4. nTra writes the requirements document. From the approved brief nTra writes the business requirements document (the BRD), the design doc and the architecture, each versioned. Every line cites a source, and nTra may not add a requirement nobody asked for. The leave balance sentence is now requirement 4 of 9.
5. nTra draws the screens. The leave balance screen takes shape on the Canvas, drawn from the approved brief. A change after approval shows as “Changed since approval” until someone approves again.
6. A person approves the design. Approval pins version 34. If the design changes after that, it needs approval again before the thread moves on.
7. nTra plans the work. Nothing is missed. The brief and the approved screens become epics. Before it writes a single task, nTra checks that every requirement is planned: 9 of 9 covered.
8. A person approves the epic. Approving the epic writes its thirteen tasks. The thread splits: one strand per task, each tied back to this requirement.
9. Every task says what done means. The camera follows one strand. Its task carries acceptance criteria (given, when, then), what is out of scope and the decisions already made. Vague criteria were rejected before it reached a person, and it still points back to the sentence.
10. Your engineers choose where it runs. From the board, each task runs on an engineer’s own machine through the nTra CLI, or on a cloud machine of its own.
11. Your AI agent builds it. nTra checks it. Claude Code builds the task and every step is logged. nTra re-runs the checks itself and the re-run decides; a second AI provider reviews the change.
12. A pull request, waiting on a person. Fourteen of fifteen steps are green: checks re-run, secrets scanned, PR open. The last step is an engineer on your team.
13. An engineer merges it. The pull request names the task, the task names the BRD requirement, and the requirement is the sentence you started with.
14. From one sentence to merged code. Every gate on the way was a person signing off. That is the trail your auditors, your engineers and your business all read the same way.
15. Bring a real requirement. We’ll take it from conversation to a signed-off, reviewed pull request, live.