Skip to main content

Execute a technical ticket

Implement the current phase, verify it locally, and leave the ticket as a useful record of what changed. Automated tests belong here; published-branch tests, human testing, and production release come later.

Pathway 2 already assumed a ready plan. Coding starts only after the Planning Phase owner has split that plan into phases.

When agents are used to inspect or implement framework code, follow the LogicBee AI coding guide. This page defines the execution method and expected result, not how the agents themselves are operated. See Responsible AI use.

Prerequisites​

  • The ticket meets the Definition of Ready.
  • The Planning Phase owner has recorded the phased approach.
  • The current phase is named, unblocked, and has observable verification.
  • You own implementation of this phase and have access to the source-code repository and, when required, Builder.

If the plan is not ready, return it to planning. If the phases are missing or not executable, return to split the plan into phases. Do not start coding to discover the plan or the phase sequence.

Implement and keep the ticket current​

  1. Confirm that the current phase is still unblocked and that the ticket still meets the Definition of Ready.
  2. Implement only this phase.
  3. Complete planned source-code and Builder work for the phase in the required order.
  4. Add or update automated tests for the changed behavior.
  5. Record material findings and decisions in the ticket.
  6. Update the plan or phases when evidence changes the scope, risk, sequence, or chosen approach.
  7. Verify this phase's expected behavior and important failure paths locally.
  8. Update durable technical, user, or support documentation where needed.

Local verification is not a substitute for published-branch tests or human acceptance.

Do not continue mechanically when execution reveals an invalid assumption, a new dependency, or a phase sequence that no longer works. Return the ticket to detail, research, planning, or the phased approach, and make the new owner and unblock condition visible.

Expected result​

The current phase is complete locally, and its automated tests and documentation reflect the change.

If the phase is independently releasable, it is ready to publish for branch testing. If it only unblocks the next phase, return to the phased approach and start the next unblocked phase.

Next: Submit the work when this phase will be published.