workflow-architect-lite

To turn a project idea into code with automated task execution, you need a two-phase workflow that generates a sequential task plan, verifies each task upon completion, and commits the changes to git automatically. This ensures fast alignment and structured implementation.

A two-phase workflow for greenfield project planning involves an Understand phase to gather requirements and propose architecture, followed by an Execute phase to implement tasks sequentially. It writes a flat plan to disk for checkpoint-friendly execution and explicit user approval.

Yes, you can resume task execution after an interruption if the workflow persists progress in a state file on disk. By saving the current execution state, the system can reload the flat plan and continue from the exact task where it left off.

Lightweight project planning for small builds does not require deep multi-phase brainstorming or large task graphs. It uses a focused Understand→Execute state machine to collect requirements, generate a flat plan, and start implementation quickly.

To handle verification failures during guided project execution, the workflow uses a simple one-strike recovery path. When a task fails verification, it triggers a recovery attempt before proceeding to the next task or creating a git commit.

The best way to plan and build fast from a new software idea is using a workflow that enforces early alignment through a brief architecture proposal, writes sequential task files to disk, and executes them with per-task verification and git commits.