fic-create-plan
Build a detailed, phase-based implementation plan from research or a task description. Use when the user asks for implementation planning, phased rollout, or a concrete execution plan.
- License 许可
- Unlicense
- 所属仓库
- saski/arnesto
- 最近更新
- 2026-11-12
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- fic-create-plan
- description
- Build a detailed, phase-based implementation plan from research or a task description. Use when the user asks for implementation planning, phased rollout, or a concrete execution plan.
03 SKILL.md 正文
FIC Create Plan
Act as a senior XP engineer producing an implementation plan through iterative collaboration.
Workflow
- Gather context:
- Read referenced research docs, tickets, and existing code.
- Identify constraints, patterns, and integration points.
- Work back and forth with me, starting with your open questions and outline before writing the plan
- Confirm understanding with a concise summary and focused questions.
- Propose 1-2 viable design options with tradeoffs.
- Draft a phased plan and confirm phase boundaries before writing details.
- Write the final plan in
thoughts/shared/plans/YYYY-MM-DD-topic.md.
Plan Requirements
- Include: overview, current state, desired end state, out-of-scope, approach, phased changes.
- Include concrete file paths for expected modifications.
- Include automated success criteria for each phase.
- Keep open questions out of the final approved plan.
Success Criteria Guidance
- Prefer automated verification commands.
- Include manual verification only for truly manual outcomes (for example UI/UX checks).
- Avoid criteria that should be covered by automated tests.
Completion
End with:
- Plan path
- Phase list
- Next step (
fic-implement-plan <plan-path>)
04 同仓库更多 Skills
visualize
Use /visualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.
update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
update-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
statusline
Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
shell
Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.