Fill gaps

A ticket can be under way and still incomplete: the pull requests so far meet some criteria and miss others. When the story check finds that, the story view offers Fill gaps. It is the same session as Implement story, but the agent is told what the check found and works only on those gaps.

#When it is offered

On the ticket's story view, in place of Implement, when all of these hold:

• the ticket has started (it has a pull request, or its status is past "not started") and is not complete;
• there is no open session for it; and
• its latest story check is current and found gaps: criteria not met or partly met, unsettled ones, or missing pieces.

With no story check, or one that is out of date, nothing is offered: run the story check first. A session never starts a story check itself. See Story checks.

#What it builds

The tab lists the gaps up front. A criterion already met by a pull request is not a gap. A criterion met outside the code, by a person's ticket comment, is not a gap either: the agent is told it is already done and not to build it. See Ticket comments.

#The flow

1. On the story view, press Fill gaps. (Build end to end, from the caret, runs the whole build from one press: see Build end to end.)
2. In the build tab, press Fill gaps. The tab says The agent is reading the gaps, the code and the ticket to make a plan.
3. Settle the plan as for Implement. The plan covers only the gaps; a gap may not be marked already met. See Plan the work.
4. Approve and start. The agent builds only the gaps the plan names.
5. Review and push, or tick After the build: review and fix, then open the pull request at the start. Each new pull request's description names the gaps it covers. See Push the result.