AfterAgile™
Lens
Get the PDF

Tuesday – Coding Day + Testing

Coding Day step by step, Engineering and testing

MTWThF

Tuesday – Coding Day + Testing

CX, UX, Product and Engineering in one shared IDE, building with AI, each in their own lane. No one starts from a blank page – every prompt is drafted from the decisions, actions and context captured in the week's sessions. The four in the IDE are the testers, and they test as it's built. Engineering keeps it sound – the flag, the model, the guardrails and the gates. It could take 3 minutes, 3 hours or all day. Shown here with the billing scenario – customers paying their bill by credit card.

Coding Day, Step by Step

Load

First 15 minutes. AI loads everything the team knows, so no one starts from memory.

  • The Intent, as aligned
  • The KPIs and each Definer's "done"
  • The Intent Review decision record
  • Monday's actions, with owners
  • Every session from the week
  • Every past session, for history
  • All decision records
  • The Collab Brief behind this Intent
  • The latest KPI Learnings
  • The live queue of customer concerns
  • The context files and house rules
  • The Engineering Guardrails
  • The design system AI project
  • Personas and live device specs
  • Last Coding Day's log and corrections
  • Open actions still in flight

Plan

The 30-minute mark. First, define AI's role for the day. Who should it be for this Intent? For example – a customer marketing specialist with deep UX skills, who knows billing, writes in our voice and builds inside our design system.

Then AI proposes a plan in small steps, and the Definers approve it before any code is written.

Build

The body of the day. Again and again, most of the day, until every Definer says it's right.

  1. PromptOne task at a time, pointing back to the Intent
  2. PreviewSee it live on the preview link
  3. TestPersonas, devices and the gates
  4. JudgeEach Definer, against their own "done"
  5. AdjustFix it in the IDE, in minutes

Harden

End of day. Engineering reviews the diff, sets the alerts and observability, and confirms the flag and the rollback.

Merge

Done. Merged behind the Intent's flag, ready for Wednesday. AI writes the pull request summary, and the session becomes decision records and actions.

Engineer's New Role

Before the first prompt

Set the boundaries

Creates the Intent's feature flag, off by default. Opens one branch for the Intent. Pins the AI model and version for the session. Flags anything touching data, payments or logins. Loads the Engineering Guardrails and context files.

During the build

Stay inside the lines

Reads every diff as AI writes it. Keeps AI inside the architecture boundaries. Verifies every new package exists and is approved. Instruments the KPI, logs, traces and alerts. Keeps preview links working for the Definers.

Before it merges

Sign the merge

Reviews the pull request AI wrote. Confirms the flag is wired and rollback works. Confirms the security, performance and accessibility gates pass. Merges behind the flag.

Testing, Inside Coding Day

Testing isn't a phase or a department anymore. The Definers give AI what it needs to check the work, then judge the result themselves, live.

From UX, approved by CX

Personas

Who the customers are, how they think and what they're trying to do. Always include one customer on their worst day.

Collected live by AI

Device specs

AI collects the devices customers actually use, in real time, with the manufacturer specs – screen sizes, operating systems and accessibility settings.

From every Definer

"Done" criteria

What "done" looks like, agreed at Intent Review, turned into tests AI can run.

Industry

Standards

Accessibility guidelines, performance budgets and security rules every change must meet.

Who Tests What

The four who work in the IDE are the four who test it.

CX

  • Does it meet the customer need, for every persona – including the worst day?
  • “Rosa won't know what CVV means. Add a hint.”

Product

  • Does it do what the Intent says, and only that? Is the KPI instrumented?
  • “Autopay is out of scope this week. Take it out.”

UX

  • Does it look, feel and flow right on every device, true to the design system?
  • “Use the existing card component, not a new one.”

Engineering

  • Is it inside the guardrails, and does every gate pass?
  • “Never store the card number. Use the payment provider's token.”

Example Prompts

Role
"Today you're a customer marketing specialist with deep UX skills. You know our billing customers, you write in our voice, and you only build with components from our design system."
Plan
"Read the Intent for credit card payments. Propose a plan in small steps. Don't write any code yet."
Build
"Add a pay-by-card option to the bill pay screen, using the saved payment methods component from the design system."
Test
"Walk through paying this month's bill by card as Rosa – 68, paying online for the first time, on a small Android phone with large text turned on. Tell me where she hesitates, what she might misread, and whether she'd trust it."
Goes in
The aligned Intent, the KPIs and every Definer's "done"
Comes out
A working build, merged behind its flag, with test results
Done when
It passes every Definer's tests and every gate, and rollback is ready

Who Touches the IDE

Coding Day has people who work in the IDE and people who watch. The effort is driven from the meetings – the decisions, actions and context already captured – so only four people need their hands on it.

The Intent

CX

Defines the Intent, and keeps every step true to the customer need.

Style guide and usability

UX

The style guide, interaction and usability, through the design system AI project.

Business context

Product

The KPIs, urgency notes and the competitive marketplace features.

Architecture

Engineering

Architecture and technical direction, inside the Engineering Guardrails.

In the IDEWatchingStakeholders
CX, UX, Product and Engineering. They prompt, steer and test.Anyone else in the session. They see every prompt and every change, and don't prompt.See the platform only during the two review cycles – Intent Review and Final Review.

Generated and Iterated Tuesday

ArtifactDrafted fromShaped in the IDE byUsed next
Build promptsThe week's decisions, actions and contextAI, steered by CX, UX, Product and EngineeringCoding Day
Working build, behind a flagThe build promptsCX, UX, Product and Engineering, each in their laneFinal Review, Ship
Test resultsEach tester's checks, the Pipeline and the persona walkthroughsCX, UX, Product and Engineering – the testersFinal Review
Pull request summaryThe code changesEngineeringFinal Review
Decision records and actionsCoding DayAI, with an owner on every actionWednesday
Updated context filesCoding DayEngineeringEvery future session