executing

name	executing
description	Execute implementation plan task-by-task inline.

Executing

Load a plan, review it critically, run every task in sequence, then hand off to arsyn:finalizing.

Announce at start: "Running plan inline using arsyn:executing."

If subagents are available, arsyn:orchestrating produces higher-quality results. Prefer it when the platform supports subagent dispatch.

Process

1. Load and Review

1. Read the plan file.
2. Identify questions, gaps, or risks.
3. If concerns exist, raise them with the user before starting.
4. If clear, begin execution.

2. Task Loop

For each task in the plan:

1. Mark task in-progress.
2. Follow each step exactly as written — the plan contains bite-sized steps for a reason.
3. Run every verification command and confirm the expected output.
4. Mark task completed.

3. Completion

After all tasks pass verification:

• Announce: "All tasks complete. Switching to arsyn:finalizing."
• Invoke arsyn:finalizing to run final checks, present options, and close the branch.

When to Stop

Halt execution immediately when:

• A dependency is missing or unavailable.
• A test fails and the cause is not obvious from the plan.
• An instruction is ambiguous or contradictory.
• Verification fails after two attempts.

Ask the user for guidance rather than guessing. Do not force through blockers.

When to Re-Review

Return to step 1 (Load and Review) when:

• The user updates the plan mid-execution.
• A fundamental approach change is needed.

Gotchas

• Skipping verification steps — Every verification in the plan exists to catch drift early. Do not skip them even when the implementation "obviously" works.
• Guessing past blockers — When stuck, stop and ask. Guessing compounds errors across subsequent tasks.
• Executing on main branch — Never start implementation on main/master without explicit user consent. Use arsyn:isolating first.
• Ignoring plan order — Tasks are sequenced for dependency reasons. Do not reorder unless you are certain there is no dependency.
• Forgetting to commit — Each task in the plan ends with a commit step. Skipping commits makes rollback impossible.
• Drifting from the plan — If you spot an improvement, note it but follow the plan as written. Propose changes to the user between tasks.

Integration

• arsyn:isolating — Set up workspace before starting.
• arsyn:planning — Produces the plan this skill consumes.
• arsyn:finalizing — Closes the branch after all tasks complete.