dotfiles/.config/opencode/skills/executing-plans/SKILL.md

name, description, permalink

name	description	permalink
executing-plans	Execute an approved implementation plan from basic-memory with task tracking, verification, and blocker handling	opencode-config/skills/executing-plans/skill

Executing Plans

Overview

Use this skill when a plan already exists in local basic-memory plans/ notes and the goal is to execute it safely and completely.

Core workflow:

• Read the plan
• Critically review before starting
• Create or update the plan note checklist in basic-memory
• Execute tasks one by one
• Run the verifications specified by the plan
• Stop on blockers instead of guessing

Step 1: Load and Review the Plan

1. Read the target note from basic-memory project plans/ (for example, plans/<feature-name>).
2. Review the plan critically before coding.
3. Identify gaps, contradictions, unclear steps, or missing prerequisites.
4. If concerns exist, raise them before implementation.
5. If the plan is sound, create/update the plan note checklist in basic-memory to mirror executable tasks.

Step 2: Execute Tasks Sequentially

For each task in order:

1. Mark one task as in_progress.
2. Follow the plan steps exactly for that task.
3. Run the verifications specified for that task (tests/checks/manual verification).
4. If verification passes, mark task completed and continue.
5. Keep only one active task at a time unless the plan explicitly allows parallel work.

Step 3: Complete the Branch Workflow

After all tasks are completed and verified:

• Use git-workflow for branch finish options (merge, PR, keep for later, or discard with confirmation).
• Record implementation outcomes back to the relevant basic-memory plans/ note when requested.

Blocker Rules (Stop Conditions)

Stop execution immediately and ask for clarification when:

• A blocker prevents progress (missing dependency, failing prerequisite, unavailable environment)
• A plan instruction is unclear or conflicts with other instructions
• Plan gaps prevent safe implementation
• Required verification repeatedly fails

Do not guess through blockers.

Worktree and Branch Safety

• Follow worktree-first conventions: execute implementation from the feature worktree, not the primary tree on a base branch.
• Never start implementation directly on main/master (or the repository's active base branch) without explicit user consent.

Related Skills

• subagent-driven-development — use when the work should be split across specialized agents
• writing-plans — use when the plan must be created or rewritten before execution
• git-workflow — use to complete branch/PR flow after implementation