Plan I

启动一个新的规划流程，创建新的规划文件。

Security Scan

The skill's purpose (create a new planning file and write an initial draft) aligns with its files, but there are notable safety/usability inconsistencies — chiefly lack of input sanitization for the plan name (file path risks) and an ambiguous model-invocation setting versus the requirement to generate content before responding.

Purpose & Capability

Name and description (start a planning process and create a planning file) match the included script and instructions. No unrelated credentials, binaries, or installs are requested.

Instruction Scope

SKILL.md instructs the agent to (1) run the included pl-init.sh to create a new file and (2) immediately write a generated initial planning draft to that file before outputting to the user. The script creates a template file but does not implement the agent's 'write the draft' step — the agent will need to perform the write itself. The instructions also enforce 'do not read existing planning files,' which is fine, but the requirement to write user-generated content to disk immediately (without an explicit confirmation step) is a privacy/consent consideration. Additionally, SKILL.md includes disable-model-invocation: true which is ambiguous relative to the requirement to analyze input and produce text to be written — if this flag prevents the model from being used in the way the author expects, execution may fail or be inconsistent.

Install Mechanism

No install spec; the skill is instruction-only with one included shell script. No remote downloads or external installs are performed.

Credentials

No environment variables, credentials, or external config paths are requested. The script operates on a local 'plans' directory and does not contact external services.

Persistence & Privilege

The skill is not 'always' enabled and does not request elevated platform privileges. It does create files under a 'plans' directory relative to the working directory; this is expected for the stated purpose but still grants the skill the ability to write persistent files to disk.

What to consider before installing

This skill mostly does what it says: it creates a new planning markdown and expects the agent to write an initial draft into that file. Before installing or using it, consider the following: - Input sanitization risk: pl-init.sh uses the raw plan name to construct the filename. A malicious or malformed plan name (containing ../ or other special characters) could cause unexpected file paths; the script does not sanitize or validate names. Prefer rejecting names with slashes, dots, or shell metacharacters or update the script to sanitize/normalize the name. - Immediate write behavior: the skill mandates writing the user's draft to disk before responding. Ensure you are comfortable with the agent persisting the user's input and any derived content without an additional confirmation step. - Ambiguous disable-model-invocation flag: SKILL.md includes disable-model-invocation: true while the instructions require generating content from user input. Verify how your platform treats this flag — it might block the model-based generation the skill expects. - Safe scope: the script does not contact the network and checks for existing files before creating a new one (it aborts on conflict), which is good. Still, review the script and run it in a safe environment first (or patch it to sanitize names) if you plan to use it on sensitive systems. If you need to proceed: (a) patch pl-init.sh to validate/sanitize plan names (e.g., allow only [a-z0-9-]), (b) confirm platform behavior for disable-model-invocation, and (c) optionally add an explicit consent/confirmation step before persisting sensitive content.

启动一个新的规划。

输入：用户的请求应当包含变更名称或对想要构建内容的描述。

步骤

1. 如果没有提供明确的输入，询问用户想要构建什么 使用 AskUserQuestion Tool（开放式，无预设选项）询问：

   "您想要进行什么规划？请描述您想要构建或修复的内容。"

   逻辑处理：

   • 根据描述，提炼出简洁的中文规划主题。
   • 命名规则：主题不允许出现空格，必须使用 "-" 字符连接（例如："检索 列表页" -> "检索-列表页"）。
   • 润色主题：对主题进行润色，使其更简洁、更具体。

2. 创建新规划

   • 确认规划名称后，调用 bash ~/.claude/skills/plan-i/scripts/pl-init.sh 脚本，传入规划名称以创建新的规划文件。
   • 注意：严禁检查或读取现有的规划文件，确保是全新创建。

3. 提取想法、生成初步规划并写入文档（关键步骤）

   • 分析用户原始输入：提取核心意图、潜在痛点和期望目标。
   • 构思初步规划草案：基于提取的信息，基于创建的规划文件格式，生成一段结构化的初步规划描述。
   • 执行写入操作：将上述初步规划草案立即写入到刚才创建的规划文件中。
     • 注意：此步骤必须在输出任何提示给用户之前完成，确保文件状态与当前对话同步。

4. 输出引导并移交控制权

• 向用户输出以下固定格式的响应，明确指示下一步操作：

> "✅ 规划 **[<规划名称>]** 已创建，初步想法已整理写入文档！

>
> **📋 初步分析摘要**：
> [此处简述用户核心意图及已写入的关键点]
>
> **🚀 建议深入方向**：
> 为了细化规划，我们需要结合代码库进行深入探索。建议从以下哪个方向开始？
> 1. [方向一：例如 - 核心业务流程梳理]
> 2. [方向二：例如 - 数据模型与存储设计]
> 3. [方向三：例如 - 现有代码库兼容性分析]
> 4. [其他自定义方向]
>
> 💡 **下一步操作**：
> **收到回复后，请运行 `/plan-c` **，我将立即读取该文件，针对您的选择深入代码库并完成详细规划迭代。"

约束与要求

• 唯一职责：仅负责初始化和首次写入。禁止在此技能中进行深入的代码库扫描或多轮迭代。
• 文件安全：严禁覆盖已存在的规划文件。若文件名冲突，需提示用户更换名称。
• 顺序严格：必须先执行 bash ~/.claude/skills/plan-i/scripts/pl-init.sh 并写入内容，最后才能输出提示。
• 安全红线: 除非用户明确指令开始编码且规划已完全就绪，否则仅输出规划逻辑和文档更新。
• 交接清晰：必须明确告知用户下一步需要触发 plan-c 技能
• 不允许探讨开发步骤：不允许探讨开发步骤/实施步骤。
• 不允许列出代码：不允许列出代码或提供具体实现, 只描述“数据结构是什么”，绝不展示“代码怎么写”。