免费在 GitHub 公开

create-plan

Turn an explicit request for a coding plan into an ordered checklist. Review project documentation and relevant files, define scope, and outline implementation, validation, and risks without changing any files.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

composio-community/awesome-codex-skills

查看安装方法

适用场景

Planning a feature before implementation
Defining the scope of a refactor
Organizing testing and validation steps
Identifying risks and open questions before coding

包含的文件（2）

SKILL.md2.4 KB
LICENSE.txt11.1 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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>

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)

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

-21risk-automation

免费

Automate 21risk operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks the service connection, and uses current input requirements to carry out requested tasks.

中文简介正在准备中。当前显示英语简介。

Find available 21risk actions
Run tasks after checking the service connection
Process multiple operations in bulk