create-plan
Create and maintain repository-aware technical plans, implementation plans, refactor proposals, design drafts, and migration plans. Use when Codex is asked to investigate a codebase and propose a solution before implementation; write or update a durable plan file; produce a 方案、实施计划或重构计划; split engineering work into phases or pull requests; document scope, non-goals, API and behavior decisions, breaking changes, migrations, risks, testing, or validation; or transition a plan through draft, planned, in-progress, blocked, and completed states.
FLC · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add flc1125/skills --skill create-plan技能说明
name: create-plan description: Create and maintain repository-aware technical plans, implementation plans, refactor proposals, design drafts, and migration plans. Use when Codex is asked to investigate a codebase and propose a solution before implementation; write or update a durable plan file; produce a 方案、实施计划或重构计划; split engineering work into phases or pull requests; document scope, non-goals, API and behavior decisions, breaking changes, migrations, risks, testing, or validation; or transition a plan through draft, planned, in-progress, blocked, and completed states. metadata: name: Create Plan description: Create and maintain repository-aware technical plans, design proposals, and migration guides. author: FLC created: "2026-07-13T16:14:03Z"
Create Plan
Create evidence-backed engineering plans that another agent can execute without reconstructing the design from conversation history.
Operating Mode
Act as a repository-aware technical planner.
Prioritize:
- verified repository facts over recalled conversation details
- explicit scope and non-goals over broad aspirations
- decisions and executable steps over generic advice
- validation tied to repository commands and risks
- adaptive structure over one mandatory large template
Do not implement runtime changes while the user is still asking for evaluation or a plan. Do not create a branch, commit, pull request, or plan file unless the user requested that action or repository instructions explicitly require the artifact.
Workflow
1. Determine the deliverable
Distinguish between:
- Conversational proposal: The user asks to assess, compare, or "先给方案". Return the proposal in chat and do not create a file.
- Durable plan: The user explicitly asks to create, write, record, or update a plan document. Locate the repository plan directory and write the artifact.
- Lifecycle update: The user asks to start, block, resume, or complete an existing plan. Update both its contents and status-bearing filename.
Ask a question only when a missing decision would materially change scope or architecture. Otherwise make a bounded assumption and label it.
2. Discover repository conventions
Before drafting:
-
Read applicable
AGENTS.mdfiles and repository instructions. -
Locate existing plan and memory directories.
-
Include hidden and ignored plans in discovery. Prefer:
rg --files --hidden --no-ignore | rg '(^|/)(plans|plan)/|plan.*\.md$' -
Inspect representative plans with the same task shape and status.
-
Read the relevant source, tests, dependency files, and build commands.
-
Check repository history or issues only when they affect the plan.
Treat current code and tests as primary evidence. Treat prior plans and conversation as secondary context because they may be stale.
When writing or updating a plan file, read references/plan-conventions.md completely before editing.
3. Frame the problem
Establish:
- current behavior and evidence
- concrete objective and completion criteria
- affected modules, public surfaces, and users
- constraints and dependencies
- explicit non-goals
- unresolved decisions and bounded assumptions
Separate facts, decisions, assumptions, and open questions. Do not present a preferred design as an existing repository fact.
4. Choose the plan shape
Use the smallest structure that makes the work executable:
- Compact plan for a bounded removal, migration, fix, or configuration change.
- Implementation plan for a new component, refactor, API change, or multi-phase task whose direction is decided.
- Design draft when alternatives, compatibility strategy, package boundaries, or architecture remain unresolved.
Read references/plan-templates.md completely, then select and adapt one template. Do not emit empty or irrelevant sections.
5. Write the plan
Make each step actionable and verifiable. Name concrete packages, APIs, files, commands, or contracts when repository evidence supports them.
Add conditional sections when material:
- breaking changes and affected downstream users
- before-and-after API or behavior comparisons
- ordered migration steps
- context, cancellation, errors, panic, ordering, concurrency, persistence, timeout, retry, or lifecycle semantics
- rollout, rollback, data migration, or deployment requirements
- independent pull request boundaries and dependency order
- risks, rejected alternatives, and decision gates
For incompatible changes, give every removed or changed public surface a replacement, migration action, or explicit statement that no direct replacement exists.
Use the user's language for prose unless repository convention requires otherwise. Keep code identifiers, status tokens, commands, and filename slugs in their native form.
6. Create and validate the artifact
When the repository uses numbered status-bearing filenames:
- List every plan file, including hidden and ignored files.
- Read the numeric prefix only from filenames that follow the repository convention.
- Identify existing duplicate numbers instead of assuming the directory is clean.
- Use the highest existing number plus one unless repository instructions define another allocation rule. Do not reuse gaps merely because a lower number is available.
- Format the number, current date, status, and short topic according to repository convention.
- Confirm that the complete target path does not already exist before writing.
After writing or renaming a plan, inspect the final file and check:
- filename, metadata status, and metadata date agree
- exactly one title, status field, and date field are present
- the sequence number does not collide with another plan
- checklist items describe observable work
- validation commands exist and match the affected scope
- completed checks have evidence
- no absolute local paths, credentials, temporary files, or