AgentSkillsCN

implementation-plan

根据现有规格说明或深度分析结果，制定结构化的实施计划（无需编写代码）。在完成规格说明撰写后使用，用于梳理实施步骤、文件触点、执行顺序以及测试策略，而无需实际编写代码。

SKILL.md
--- frontmatter
name: implementation-plan
description: Produce a structured implementation plan (no code) from an existing specification or deep analysis. Use after a spec is written to outline steps, file touch points, sequencing, and test strategy without writing code.

Implementation Plan

Overview

Transform an existing specification into a clear, ordered implementation plan with concrete steps, affected areas, and test execution sequence. Do not write code.

Workflow

  1. •Confirm inputs
  • •Ensure a specification already exists in the current context.
  • •If missing, ask for the spec or a link to it.
  1. •Identify workstreams
  • •Break the spec into discrete steps: core logic, validation, UI, persistence, integration, tests, tooling.
  • •Map each step to files/areas referenced in the spec.
  1. •Order the steps
  • •Prefer foundational utilities first, then integrations, then UI, then tests.
  • •Highlight prerequisites and dependencies between steps.
  1. •Define test strategy
  • •List the test layers to update (unit/integration/e2e).
  • •Specify the target projects and key scenarios.
  • •Include build/test command order when relevant.
  1. •Call out risks and checkpoints
  • •Note migration or compatibility concerns.
  • •Identify risky changes that warrant extra verification.

Output Format

  • •Title
  • •Assumptions
  • •Step-by-step plan (numbered)
  • •Files/Areas to touch (bulleted)
  • •Test plan (bulleted)
  • •Risks/Checkpoints

Constraints

  • •Do not generate code.
  • •Ask questions only if the specification is missing or ambiguous.
  • •Keep plan concise but actionable.