AgentSkillsCN

implement-plan

当用户已从 thoughts/shared/plans/ 目录中获取经批准的方案，并请求付诸实施时，可使用此技能。全面阅读方案内容，按既定阶段依次推进，每完成一个阶段即实施并验证，同时更新方案中的复选框；除非另有指示，否则在各阶段之间应暂停并进行人工核查。在用户确认之前，切勿将人工核查事项标记为已完成。

SKILL.md
--- frontmatter
name: implement-plan
description: Use when the user provides an approved plan from thoughts/shared/plans and asks to implement it. Read the plan fully, follow phases in order, implement + verify each phase, update checkboxes in the plan, and pause for manual verification between phases unless instructed otherwise. Do not mark manual verification items as done until the user confirms.

Implement Plan

You are tasked with implementing an approved technical plan from thoughts/shared/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

When given a plan path:

  • •Read the plan completely and check for any existing checkmarks (- [x]).
  • •Read the original ticket and all files mentioned in the plan.
  • •Read files fully (no truncation) whenever feasible; you need complete context.
  • •Think through how the pieces fit together.
  • •Create a todo list to track progress.
  • •Start implementing once you understand what needs to be done.

If no plan path is provided, ask for one.

Implementation Philosophy

Plans are carefully designed, but reality can be messy. Your job is to:

  • •Follow the plan's intent while adapting to what you find.
  • •Implement each phase fully before moving to the next.
  • •Verify the work makes sense in the broader codebase context.
  • •Update checkboxes in the plan as you complete sections.

When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.

If you encounter a mismatch:

  • •STOP and think about why the plan can't be followed.
  • •Present the issue clearly:

Issue in Phase [N]: Expected: [what the plan says] Found: [actual situation] Why this matters: [explanation]

How should I proceed?

Verification Approach

After implementing a phase:

  • •Run the success criteria checks for that phase (often make check test or repo-specific commands).
  • •Fix any issues before proceeding.
  • •Update progress in both the plan and your todos.
  • •Check off completed items in the plan file itself.

Pause for human verification:

  • •After completing all automated verification for a phase, pause and inform the user that the phase is ready for manual testing.
  • •Use this format:

Phase [N] Complete - Ready for Manual Verification

Automated verification passed:

  • •[List automated checks that passed]

Please perform the manual verification steps listed in the plan:

  • •[List manual verification items from the plan]

Let me know when manual testing is complete so I can proceed to Phase [N+1].

If instructed to execute multiple phases consecutively, skip the pause until the last phase. Otherwise, assume you are doing one phase at a time.

Do not check off items in the manual testing steps until confirmed by the user.

If You Get Stuck

When something isn't working as expected:

  • •First, make sure you've read and understood all relevant code.
  • •Consider if the codebase has evolved since the plan was written.
  • •Present the mismatch clearly and ask for guidance.

Use sub-tasks sparingly — mainly for targeted debugging or exploring unfamiliar territory.

Resuming Work

If the plan has existing checkmarks:

  • •Trust completed work is done.
  • •Pick up from the first unchecked item.
  • •Re-verify previous work only if something seems off.

Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.