lightspec-loop

Fresh subagent isolation prevents context bleed by dispatching a new subagent per change proposal. Each subagent starts with a clean context window to implement a single spec before archiving and proceeding sequentially.

Sequential spec execution works by applying each spec via lightspec, archiving the completed work, and reporting completion before the next subagent triggers. This enforces strict order and clears context between independent implementations.

Context mixes when reusing the same subagent across specs. Dispatching a fresh subagent per change proposal ensures clean context isolation, requiring a clear command before applying and archiving each spec sequentially.

Yes, the subagent workflow provides clear per-spec progress tracking and rollback options. If an isolated implementation fails, the sequential workflow halts, allowing you to rollback the current spec before proceeding to the next pending proposal.

The best way to manage multiple independent specs is dispatching a fresh subagent per proposal. This automated workflow isolates implementation by clearing context, applying the spec, archiving it, and reporting completion before moving forward.

Manual context clearing is built into the automated workflow. Each dispatched subagent must start with a clear command to ensure clean context isolation before applying and archiving the current spec implementation.