Agent Skills
› foryourhealth111-pixel/Vibe-Skills
› create-plan
create-plan
GitHub将用户提示转化为单一、可执行的编程任务计划。通过只读模式扫描上下文，仅在最必要时提问，并严格遵循模板输出包含目标、范围、原子化行动项及待办问题的计划，不生成代码或元解释。
Trigger Scenarios
用户明确要求创建计划
涉及编码任务的规划需求
Install
npx skills add foryourhealth111-pixel/Vibe-Skills --skill create-plan -g -y
SKILL.md
Frontmatter
{
"name": "create-plan",
"metadata": {
"short-description": "Create a plan"
},
"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.mdand 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).
- Read
-
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>
Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: "Run npm test", "Add unit tests for X"
- Include safe rollout when relevant: feature flag, migration plan, rollback note
Avoid:
- Vague steps ("handle backend", "do auth")
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)
Version History
- f627ab5 Current 2026-07-25 04:40
