run-execution-packetlisted

Execute an already-planned execution packet's sessions in strict sequential order, as one agent, from its start file through closeout. Use when handed a prepared packet to run - not for planning one.
mike-arbuzov365/engineering-intelligence-framework · ★ 3 · AI & Automation · score 72

Install: claude install-skill mike-arbuzov365/engineering-intelligence-framework

# Skill: Run Execution Packet  Full workflow: [`playbooks/execution-packet-execution.md`](../../playbooks/execution-packet-execution.md). ## Process 1. Read the packet's start file (`06-START-HERE-*.md` or equivalent) - not a paraphrase, not prior chat history. 2. For each session, in the roadmap's exact order: - Read its launch file. - Execute against its declared scope, no-touch zone, and verification commands (see [`playbooks/session-execution.md`](../../playbooks/session-execution.md)). - Confirm its exit criteria before starting the next session. - Keep its checkpoint - this is what makes an interrupted session resumable and the whole packet independently reviewable. - For iterative work, run the session's bounded evidence loop. Do not exceed its iteration or remote-run budget, and do not treat a completion phrase as proof. 3. Respect any resource/budget guard from the packet's decisions file (e.g. avoiding hosted/paid CI) for every session, not just the one that states it. 4. One agent, sequential, no delegation/spawn/team tools. 5. On the final session: run [`playbooks/session-closeout.md`](../../playbooks/session-closeout.md), then fill `templates/packet-closeout.md` from the actual accumulated session results. ## If blocked Recor