AgentSkillsCN

lazy-planner

将对话情境转化为可执行的计划文档（PLAN-*.md），细化任务分解、附上代码引用，并明确实施顺序。在被要求制定计划、撰写计划文档、将讨论转化为可执行步骤、规划功能实现、进行任务分解，或起草实施路线图时使用。此技能仅负责撰写计划，绝不直接实施——只专注于将想法转化为清晰的行动方案。

SKILL.md
--- frontmatter
name: lazy-planner
description: Transform conversation context into an actionable plan document (PLAN-*.md) with task breakdowns, code references, and implementation order. Use when asked to create a plan, write a plan document, turn a discussion into actionable steps, plan out a feature, create a task breakdown, or draft an implementation roadmap. Does NOT implement — only writes the plan.

Lazy Planner

Transform the current conversation history into a comprehensive, actionable plan document.

DO NOT IMPLEMENT THE PLAN — ONLY WRITE THE PLAN DOCUMENT

Requirements

  • •Capture all context: Distill decisions, technical approaches, rationale, and constraints from the conversation history
  • •Actionable task breakdown: Step-by-step implementation tasks with checkbox to-do lists for tracking progress
  • •Code references:
    • •Internal: Full relative file paths for all relevant files in the codebase
    • •External: Complete Git URLs for any third-party code, libraries, or examples needed
  • •Technical specifications: API endpoints, data models, configuration requirements, and integration points as applicable
  • •Implementation order: Tasks sequenced by dependencies with clear milestones
  • •Validation criteria: How to verify each step is complete and working correctly
  • •Research integration: If external research was done, include relevant findings and source links

Structure

Use clear markdown formatting with:

  • •H2/H3 headers for major sections and subsections
  • •- [ ] checkbox syntax for all actionable items
  • •Code blocks with language tags for any snippets or commands
  • •Tables for comparing options or listing configuration values where appropriate

File Location

Save to project root: PLAN-[descriptive-name].md

If working from a GitHub issue, prepend the issue number: PLAN-[issue-num]-[descriptive-name].md

Make the plan detailed enough that it can be executed step-by-step without needing to re-establish context from this conversation.

REMINDER: DO NOT IMPLEMENT THE PLAN — ONLY WRITE THE PLAN DOCUMENT

Clarifying Questions

Use the ask_questions tool when facing:

  • •Ambiguous scope or priorities
  • •Multiple valid technical approaches
  • •Unclear constraints or dependencies
  • •Tradeoffs that need user decision (speed vs completeness, etc.)