# I built a state-management workflow for long AI-assisted projects (Normal/Quick Check/Lockdown) — looking for people to test it

> Source: <https://dev.to/yongabi_favour_2db36f1923/i-built-a-state-management-workflow-for-long-ai-assisted-projects-normalquick-checklockdown--2m3>
> Published: 2026-07-22 21:48:37+00:00

I kept losing track of where I was in long AI conversations — mid-decision,

half-explored tangents, no clean way to close something out. I built a small

set of rules to fix that. Sharing it because I want people to actually test

it, not just tell me it looks good.

HOW TO USE IT:

Paste the document below into your system prompt / custom instructions /

project instructions (works in Claude, ChatGPT, or similar). Then during

your conversation, just say one of three trigger phrases:

Would genuinely like to know: does it hold up in a real multi-week project,

or does it break somewhere I haven't seen yet?

AI Workflow State Management

I manage long projects using a structured workflow. Whenever I use one of the commands below, follow these rules.

Return point: The next continuation point (only if one has already been defined).

Keep this response short.

"Quick Check"

Treat this as a temporary side exploration.

Keep the Main Workflow unchanged.

Explore only the specific question I ask.

Help me reach a conclusion quickly.

At the end, tell me whether the Quick Check is complete.

Then return me to the Main Workflow.

If the Quick Check starts expanding too much, remind me to either:

conclude it, or

convert it into a separate Main Workflow.

"Lockdown"

When I say "Lockdown", switch into Lockdown Mode.

Stage 1 – Prepare for Lockdown

Help me identify:

Stage 2 – Confirm

Before continuing, always confirm:

Stage 3 – Lockdown Mode

After I confirm:

Stage 4 – Complete

When the lockdown is complete:

General Rule

Always preserve the distinction between:

Feedback, criticism, "this breaks when X" — all welcome.
