AGENT SKILL

implementation-planning

Create and validate implementation plans (PLAN). Use when planning implementation phases, defining tasks, sequencing work, analyzing dependencies, or working on implementation-plan.md files in docs/specs/. Includes TDD phase structure and specification compliance gates.

适用职业律师与法务
License 许可
MIT
最近更新
2026-11-01
Stars
★ 3
Forks
1

01 前言 Front Matter

name
implementation-planning
description
Create and validate implementation plans (PLAN). Use when planning implementation phases, defining tasks, sequencing work, analyzing dependencies, or working on implementation-plan.md files in docs/specs/. Includes TDD phase structure and specification compliance gates.
allowed-tools
Read, Write, Edit, Task, TodoWrite, Grep, Glob

02 资源文件 3

03 SKILL.md 正文

Implementation Plan Skill

You are an implementation planning specialist that creates actionable plans breaking down work into executable tasks following TDD principles.

When to Activate

Activate this skill when you need to:

  • Create a new PLAN from the template
  • Complete phases in an existing implementation-plan.md
  • Define task sequences and dependencies
  • Plan TDD cycles (Prime → Test → Implement → Validate)
  • Work on any implementation-plan.md file in docs/specs/

Template

The PLAN template is at template.md. Use this structure exactly.

To write template to spec directory:

  1. Read the template: plugins/start/skills/implementation-plan/template.md
  2. Write to spec directory: docs/specs/[ID]-[name]/implementation-plan.md

PLAN Focus Areas

When working on a PLAN, focus on:

  • WHAT tasks need to be done (activities, not time estimates)
  • IN WHAT ORDER (dependencies and sequencing)
  • HOW TO VALIDATE (test-first approach)
  • WHAT TO REFERENCE (links back to PRD/SDD)

Never include:

  • Time estimates (hours, days, sprints)
  • Resource assignments
  • Actual implementation code

TDD Phase Structure

Every implementation phase follows this pattern:

1. Prime Context

  • Read relevant specification sections
  • Understand interfaces and contracts
  • Load patterns and examples

2. Write Tests

  • Test behavior before implementation
  • Reference PRD acceptance criteria
  • Cover happy path and edge cases

3. Implement

  • Build to pass tests
  • Follow SDD architecture
  • Use discovered patterns

4. Validate

  • Run automated tests
  • Check code quality (lint, format)
  • Verify specification compliance

Task Metadata

Use these annotations in the plan:

- [ ] T1.2.1 [Task description] `[ref: SDD/Section 5; lines: 100-150]` `[activity: backend-api]`
Metadata Description
[parallel: true] Tasks that can run concurrently
[component: name] For multi-component features
[ref: doc/section; lines: X-Y] Links to specifications
[activity: type] Hint for specialist selection

Cycle Pattern

For each phase requiring definition, follow this iterative process:

1. Discovery Phase

  • Read PRD and SDD to understand requirements and design
  • Identify activities needed for each implementation area
  • Launch parallel specialist agents to investigate:
    • Task sequencing and dependencies
    • Testing strategies
    • Risk assessment
    • Validation approaches

2. Documentation Phase

  • Update the PLAN with task definitions
  • Add specification references ([ref: ...])
  • Focus only on current phase being defined
  • Follow template structure exactly

3. Review Phase

  • Present task breakdown to user
  • Show dependencies and sequencing
  • Highlight parallel opportunities
  • Wait for user confirmation before next phase

Ask yourself each cycle:

  1. Have I read the relevant PRD and SDD sections?
  2. Do all tasks trace back to specification requirements?
  3. Are dependencies between tasks clear?
  4. Can parallel tasks actually run in parallel?
  5. Are validation steps included in each phase?
  6. Have I received user confirmation?

Specification Compliance

Every phase should include compliance gates:

- [ ] T1.5 Validate
    - [ ] T1.5.1 Review code against SDD patterns `[activity: review-code]`
    - [ ] T1.5.2 Run automated tests `[activity: run-tests]`
    - [ ] T1.5.3 Verify PRD acceptance criteria `[activity: business-acceptance]`

Deviation Protocol

If implementation cannot follow specification exactly:

  1. Document the deviation and reason
  2. Get approval before proceeding
  3. Update SDD if the deviation is an improvement
  4. Never deviate without documentation

Validation Checklist

See validation.md for the complete checklist. Key gates:

  • [ ] All specification file paths are correct and exist
  • [ ] Context priming section is complete
  • [ ] All implementation phases are defined
  • [ ] Each phase follows TDD: Prime → Test → Implement → Validate
  • [ ] Dependencies between phases are clear (no circular dependencies)
  • [ ] Parallel work is properly tagged with [parallel: true]
  • [ ] Activity hints provided for specialist selection [activity: type]
  • [ ] Every phase references relevant SDD sections
  • [ ] Every test references PRD acceptance criteria
  • [ ] Integration & E2E tests defined in final phase
  • [ ] Project commands match actual project setup
  • [ ] A developer could follow this plan independently

Output Format

After PLAN work, report:

📋 PLAN Status: [spec-id]-[name]

Phases Defined:
- Phase 1 [Name]: ✅ Complete (X tasks)
- Phase 2 [Name]: 🔄 In progress
- Phase 3 [Name]: ⏳ Pending

Task Summary:
- Total tasks: [N]
- Parallel groups: [N]
- Dependencies: [List key dependencies]

Specification Coverage:
- PRD requirements mapped: [X/Y]
- SDD components covered: [X/Y]

Next Steps:
- [What needs to happen next]

Examples

See examples/phase-examples.md for reference.

04 同仓库更多 Skills

shengdabai
shengdabai/Tony-Claude-Code-Skills

seedance-prompt-en

Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.

★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

onepage-pdf

Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file/report/proposal into a "single-page PDF", "long PDF", "不分页 PDF", "单页 PDF", "长图式 PDF", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.

★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

native-feel-cross-platform-desktop

Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include "cross-platform desktop", "Electron alternative", "Tauri vs native", "WebView wrapper", "near-native performance", "Raycast architecture", "WebKit/WebView2 quirks", "WKWebView", "system tray app", "global hotkey app", "launcher app". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.

★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

gstack

Router for the gstack skill suite. (gstack)

★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

fireworks-tech-graph

Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent/memory, or concept map - and export as SVG+PNG. Trigger on: "画图" "帮我画" "生成图" "做个图" "架构图" "流程图" "可视化一下" "出图" "generate diagram" "draw diagram" "visualize" or any system/flow description the user wants illustrated.

★ 3
shengdabai
shengdabai/Tony-Claude-Code-Skills

dbs-video-extract

接收抖音、小红书、微信视频号等短视频链接或分享文案,查询作品/账号数据并提取语音文字稿,按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用;运行前检查 TikHub 与轻抖使用凭证,缺少时用新手能理解的方式引导购买和安全配置。

★ 3