Seqimpl

Overview

Use this skill when the user wants batch implementation through fresh worker runs instead of one long interactive context. The interactive Codex session acts as the orchestrator, launches one fresh codex exec worker per task, waits for it to finish, appends a summary entry, then starts the next task against the updated codebase.

When To Use It

• The user says to use $seqimpl.
• The user wants several coding tasks handled sequentially with no overlap.
• The user wants each task to start with fresh worker context while still building on the latest code changes from prior tasks.
• The user wants an audit trail containing the prompt, timing, token usage, and final worker response for every task.

Do not use this skill for parallel execution. This skill guarantees exactly one worker at a time.

Workflow

1. Parse the user's task list into discrete tasks in the order given.
2. Write those tasks to a temporary JSON file when needed.
3. Run .