Dilux Agentic Workflow · DAW
Your agent writes code fast. The process is what is missing.
DAW is a development pipeline your coding agent has to walk through: phases in order, gates it cannot talk its way past, auditors that did not write the code they review, and state that survives closing the terminal. No product code is written with no ticket open.
The pipeline
Six phases, one at a time
You ask in plain language and the pipeline starts on its own. Every arrow waits for your approval, unless you asked for minimal autonomy when the work was classified. Each phase commits what it produced as it closes.
CLASSIFY
Works out what you are asking for, reads your stack, opens a ticket and a branch. You confirm the classification.
DEFINE
The what and the why: the PRD, taken from the one you already have and validated against the codebase.
PLAN
The how and what could go wrong: spec and threat model. No approved spec, no code, and a hook enforces it.
CODE
Implemented block by block, each with its tests. Gate: suite green, SAST clean.
VERIFY
An agent that did not write the code checks it against the PRD and the spec, and writes a report. If it fails, back to CODE.
CLOSEOUT
Changelog, pull request, ticket and closeout. Then back to rest, ready for the next request.
Tiers
The ceremony matches the size of the request
Fixing a typo cannot cost you a PRD. CLASSIFY assigns a tier, and the tier picks the pipeline.
QUERY
A question gets an answer. Read-only, and the state is not touched.
QUICK-FIX
Up to ten lines with no attack surface: a short lane with no PLAN and no VERIFY. A hook stops it the moment it grows or reaches a sensitive path.
FIX
A defect, including a live production bug: the full pipeline, with root cause, a regression test and a rollback plan.
FEATURE
New functionality: the full pipeline, with a PRD, a spec in blocks and scope control.
DISCOVERY
Thinking an idea through: a concept and validated PRDs, without touching your source.
FREE
For when you genuinely want none of this: no gates, no artifacts, and every session says out loud that you are working without the workflow.
Promise versus guarantee
A rule in a prompt is a promise. A rule in a hook is a guarantee.
Before every write, code outside the model reads the state and refuses what the current phase forbids. And no gate can be passed by saying so: document gates need a receipt from a validation run with zero failures, the commit gate asks git and the PR gate asks the forge.
Security
A phase, not a footnote
Threat model, in PLAN
Looks at the design before it exists. Blind to implementation bugs, which is why it is not alone.
SAST, in CODE
Looks at the code without running it. Blind to business logic and authorization, which the threat model covers.
Six tools, one method
Claude Code, Codex CLI, Copilot CLI, Cursor, Gemini CLI and OpenCode. Where it installs as a plugin, nothing of the method lands in your repository.