Engineering Flow docs

What this is

Strong coding models already know these engineering techniques; the problem is that they apply them inconsistently, and the occasions they skip are usually the expensive ones. Engineering Flow targets a small number of those high-value failure modes. It does not take control away from you and it does not replace your project’s own instruction files. Each session automatically loads a compact set of engineering, completion, and safety rules. Anything heavier than that must be invoked by name.

How a session runs

1. 01

   New session

   The minimal Engineering Core loads automatically. No planning, TDD, worktree, or release ceremony.

2. 02

   Ordinary request

   Core only. A clear, routine task is handled directly at full speed.

3. 03

   Named workflow

   The full workflow loads and owns the whole task, not just the message that named it.

4. 04

   Same-task follow-up

   Ordinary replies continue the current phase — no need to repeat the token.

Choose a workflow

Choose by the situation you are in, not by how large the task looks.

Boundaries that always hold

• Your current request, the project’s AGENTS.md / CLAUDE.md, and its authoritative documents always win.
• A full workflow is never loaded unless you name it. An unknown token triggers nothing.
• Explicit cancellation, switching workflows, or starting an unrelated task ends the inheritance.
• No workflow gains permission to commit, push, publish, open issues, install dependencies, or change global configuration.

Start here