Engineering Flow
中文
← Back to workflows

WORKFLOW 01 / 05

Develop

Align, approve, implement, and verify one change.

GATED · STATEFUL

Core idea

Understand the task well enough to implement safely before writing any code. Approval is a separate, explicit human act — never implied.

How it runs

Human approval required
  1. 01
    Discover

    Read project rules, authoritative docs, the relevant code, tests, and callers. Evidence is gathered once and reused.

  2. 02
    Clarify

    Ask only about undecided behavior that changes the result. Independent questions are batched and asked together.

  3. 03
    Checkpoint

    Present the goal, acceptance behavior, out of scope, assumptions, and solution boundary — then stop.

  4. 04
    ApprovalHuman approval required

    Only explicit action language sent after the checkpoint ("implement this") authorizes coding. Answers and acknowledgements do not.

  5. 05
    Implement

    Make the smallest clear change inside the module that owns the rule.

  6. 06
    Harden

    Add targeted coverage only for real risks — no ceremonial tests.

  7. 07
    Complete

    Reconcile every accepted behavior against fresh verification, and make the docs match the facts.

Key mechanisms

Approval gate

Coding starts only after explicit post-checkpoint action language. The initial request, clarification answers, and "looks good" never count as approval.

Batched clarification

Independent questions are asked in one batch; only questions raised by those answers get follow-ups. No drip-feed interviewing.

Task-level continuity

Corrections, omissions, and same-task follow-ups continue inside the same flow — no need to invoke the workflow again.