Executing Plans

For each task:

1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. As you write code, cross-check against the best practices — especially when you're writing validators, delete operations, bulk updates, model hooks, or external resource integrations
4. Run verifications as specified
5. Mark as completed

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 Revisit Earlier Steps

Return to Review (Step 1) when:

• Partner updates the plan based on your feedback
• Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

• Review plan critically first
• Follow plan steps exactly
• Don't skip verifications
• Reference skills when plan says to
• Stop when blocked, don't guess
• Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

• using-git-worktrees - REQUIRED: Set up isolated workspace before starting
• writing-plans - Creates the plan this skill executes
• finishing-a-development-branch - Complete development after all tasks

Bundled references:

• references/best-practices.md - 24 code quality patterns from real code reviews. Read at the start of Step 2 and apply throughout implementation.