unioss-executing-planslisted

# Executing Plans ## Overview Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the executing-plans skill to implement this plan." **Note:** this skill is the fallback for harnesses without subagents. Where subagents are available, `unioss-pipeline:unioss-subagent-driven-development` produces better work — say so once and let your human partner choose. ## The Process ### Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create todos for the plan items and proceed ### Step 2: Execute Tasks For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed ### Step 3: Complete Development After all tasks complete and verified: - Announce: "All tasks complete — running /unioss-ship to open the merge request(s)." - **REQUIRED:** ask user to select target mode (`staging` or `customer`), then run `/unioss-ship <mode>` - Follow that command's prompts to confirm the MR(s) ## When to Stop and Ask for Help **STOP executing immediately when:** - Hit a blocker (missing dependency, test fails, instruction unclear) - Plan has critical gaps preventing starting - You don't understand an instruction - Verification fails repeatedly **Ask for clarification rather than guessing.** ## When to Re