Agent Skills › freestylefly/wesight › create-plan

create-plan

GitHub

将用户提示转化为单一、可执行的编码计划。通过只读模式扫描上下文，识别约束与范围，生成包含目标、行动清单及开放问题的结构化Markdown计划，不执行代码写入。

SKILLs/create-plan/SKILL.md freestylefly/wesight

Trigger Scenarios

用户明确要求制定开发或编码计划需要为特定任务拆解实施步骤和验证流程

Install

npx skills add freestylefly/wesight --skill create-plan -g -y

More Options

Non-standard path

npx skills add https://github.com/freestylefly/wesight/tree/main/SKILLs/create-plan -g -y

Use without installing

npx skills use freestylefly/wesight@create-plan

指定 Agent (Claude Code)

npx skills add freestylefly/wesight --skill create-plan -a claude-code -g -y

安装 repo 全部 skill

npx skills add freestylefly/wesight --all -g -y

预览 repo 内 skill

npx skills add freestylefly/wesight --list

SKILL.md

Frontmatter

{
    "name": "create-plan",
    "metadata": {
        "short-description": "Create a plan"
    },
    "official": true,
    "description": "Create a concise plan. Use when a user explicitly asks for a plan related to a coding task."
}

Create Plan

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

Scan context quickly
- Read README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
- Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
  - Each checklist item should be a concrete action and, when helpful, mention files/commands.
  - Make items atomic and ordered: discovery → changes → tests → rollout.
  - Verb-first: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
Do not preface the plan with meta explanations; output only the plan as per template

Plan template (follow exactly)

# Plan

<1–3 sentences: what we’re doing, why, and the high-level approach.>

## Scope
- In:
- Out:

## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>

## Open questions
- <Question 1>
- <Question 2>
- <Question 3>