Aklman
中文

— Demo / June 6, 2026

Codex App: From Task to Verified Change

A product demo script for showing how goal, context, execution, and verification fit into one development flow.

DemoWeb Demo18 minCodex · AI Native Development · Developer Experience
Open slides Print

— Outline

Outline

  1. 01

    State the task clearly

    Begin with goal, constraints, and acceptance criteria before asking for code.

  2. 02

    Make context traceable

    Files, terminals, browsers, and tests become evidence in one workflow.

  3. 03

    Close with verification

    Every handoff should say what changed, what was tested, and what risk remains.

— Notes

Notes

This demo explains how an agentic development product should present its value.

The point is not to perform AI writes code quickly. The point is engineering flow: task input, context reading, change execution, verification feedback, and a clear handoff.

— Slides

Slides

  1. 01

    01 / Goal

    A task is not one prompt

    A good development task names the goal, boundaries, acceptance checks, and places the agent should not touch.

  2. 02

    02 / Context

    Context should be replayable

    When an agent reads code, runs tests, and inspects the browser, it should leave understandable evidence.

  3. 03

    03 / Verification

    Delivery ends with proof

    Not 'I changed it', but 'I changed these parts, tested these paths, and this risk remains'.

— Resources

Resources

Works index

— Discussion

Manage on GitHub

Comments

Join the conversation through GitHub Discussions. Replies follow your GitHub notification settings.

Comments are powered by GitHub Discussions. Please keep the conversation focused and respectful.

← Back to sessions