技能 create-plan
📋

create-plan

安全 🌐 網路存取⚙️ 外部命令

Create structured coding plans

也可從以下取得: Cygnusfear

Creating detailed implementation plans for coding tasks takes time and often results in missed steps. This skill transforms any coding request into a clear, actionable plan with scope boundaries, ordered checklist items, and identified open questions.

支援: Claude Codex Code(CC)
📊 71 充足
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「create-plan」。 Create a plan to add user authentication to our API

預期結果:

  • Plan intent: Implement secure authentication for API endpoints
  • Scope in: Auth routes, middleware, user model
  • Scope out: OAuth integration, password reset
  • Action items: Add User model, Create auth routes, Implement middleware, Add tests, Update docs

正在使用「create-plan」。 Create a refactoring plan for the legacy payment module

預期結果:

  • Goal: Improve maintainability and test coverage
  • Scope in: Core payment logic, unit tests
  • Scope out: API changes, UI components
  • Action items: Analyze current structure, Extract interfaces, Add tests, Modernize syntax, Verify all tests pass

正在使用「create-plan」。 Create a migration plan from Express to FastAPI

預期結果:

  • Intent: Modernize API framework for better performance
  • Scope in: Route handlers, middleware, configuration
  • Scope out: Database schema changes, client applications
  • Action items: Set up FastAPI project, Migrate routes one-by-one, Add async support, Test endpoints, Update deployment

安全審計

安全
v5 • 1/17/2026

This skill contains only markdown documentation. No executable code, scripts, network calls, or file modifications exist. Static findings are false positives triggered by metadata fields (GitHub URLs, 'command' substring in content_hash, 'md' substrings in documentation). Pure read-only prompt template.

2
已掃描檔案
256
分析行數
2
發現項
5
審計總數
審計者: claude 查看審計歷史 →

品質評分

38
架構
100
可維護性
85
內容
30
社群
100
安全
91
規範符合性

你能建構什麼

Break down feature requests

Transforms feature requests into ordered implementation steps with test and rollout considerations.

Estimate work scope

Creates clear scope boundaries and identifies unknowns before committing to project timelines.

Review implementation approaches

Provides structured review of technical approaches with edge cases and validation checkpoints.

試試這些提示

Basic plan request
Create a plan for [describe your task] in [project name]. Focus on [specific area].
Refactoring plan
Create a refactoring plan for [file/module]. Goal: [improve performance/readability/test coverage].
Bug fix plan
Investigate and create a fix plan for [bug description]. Error: [paste error message].
Complex migration
Create a migration plan from [current tech] to [new tech] for [scope]. Include rollback strategy.

最佳實務

  • Provide project context like README and architecture docs for better plans
  • Ask clarifying questions early if requirements are unclear
  • Review scope boundaries before starting implementation

避免

  • Asking for plans without providing project context
  • Requesting plans for vague or ambiguous tasks
  • Skipping the scope section and creating unbounded plans

常見問題

Does this skill modify my codebase?
No. This skill operates strictly in read-only mode. It only reads project files for context.
How detailed are the generated plans?
Plans include 6-10 action items with file paths and validation steps. Each item is atomic and ordered.
Can I use this with any programming language?
Yes. The skill is language-agnostic and works with any codebase structure.
Is my data safe?
Yes. No data is transmitted externally. All context scanning happens locally.
Why does it ask follow-up questions?
It asks at most 1-2 questions only when absolutely necessary to create a responsible plan.
How is this different from asking Claude directly?
This skill enforces a consistent structure with scope boundaries, ordered checklists, and explicit out-of-scope items.