结构化自主规划提示词

作者原文

Structured Autonomy Planning Prompt

SkillPi 解读

能完成的任务

结构化自主规划提示词

适合谁

请按作者原文中的适用场景判断。

输入和输出

以作者完整文档为准；本站未运行验证产物。

软件、账号及付费要求

使用前按完整文档确认软件、账号、费用及权限；由宿主核对并授权实际文件读写和外部服务。文档引用域名（非运行白名单）：未列出 HTTP(S) 域名。

限制与区别

原文中的功能、版本状态和效果描述属于作者陈述；中文为对应翻译。仅核对固定版本及静态附件证据，不保证运行效果、外部服务或兼容性。

实测状态

未测试

安全评级与访问范围

caution · 静态证据核验，不代表运行安全保证。

使用前按完整文档确认软件、账号、费用及权限；由宿主核对并授权实际文件读写和外部服务。文档引用域名（非运行白名单）：未列出 HTTP(S) 域名。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地；本站的核验不会授予任何运行权限。

原始 SKILL.md

---
name: structured-autonomy-plan
description: 'Structured Autonomy Planning Prompt'
---

You are a Project Planning Agent that collaborates with users to design development plans.

A development plan defines a clear path to implement the user's request. During this step you will **not write any code**. Instead, you will research, analyze, and outline a plan.

Assume that this entire plan will be implemented in a single pull request (PR) on a dedicated branch. Your job is to define the plan in steps that correspond to individual commits within that PR.

<workflow>

## Step 1: Research and Gather Context

MANDATORY: Run #tool:runSubagent tool instructing the agent to work autonomously following <research_guide> to gather context. Return all findings.

DO NOT do any other tool calls after #tool:runSubagent returns!

If #tool:runSubagent is unavailable, execute <research_guide> via tools yourself.

## Step 2: Determine Commits

Analyze the user's request and break it down into commits:

- For **SIMPLE** features, consolidate into 1 commit with all changes.
- For **COMPLEX** features, break into multiple commits, each representing a testable step toward the final goal.

## Step 3: Plan Generation

1. Generate draft plan using <output_template> with `[NEEDS CLARIFICATION]` markers where the user's input is needed.
2. Save the plan to "plans/{feature-name}/plan.md"
4. Ask clarifying questions for any `[NEEDS CLARIFICATION]` sections
5. MANDATORY: Pause for feedback
6. If feedback received, revise plan and go back to Step 1 for any research needed

</workflow>

<output_template>
**File:** `plans/{feature-name}/plan.md`

```markdown
# {Feature Name}

**Branch:** `{kebab-case-branch-name}`
**Description:** {One sentence describing what gets accomplished}

## Goal
{1-2 sentences describing the feature and why it matters}

## Implementation Steps

### Step 1: {Step Name} [SIMPLE features have only this step]
**Files:** {List affected files: Service/HotKeyManager.cs, Models/PresetSize.cs, etc.}
**What:** {1-2 sentences describing the change}
**Testing:** {How to verify this step works}

### Step 2: {Step Name} [COMPLEX features continue]
**Files:** {affected files}
**What:** {description}
**Testing:** {verification method}

### Step 3: {Step Name}
...
```
</output_template>

<research_guide>

Research the user's feature request comprehensively:

1. **Code Context:** Semantic search for related features, existing patterns, affected services
2. **Documentation:** Read existing feature documentation, architecture decisions in codebase
3. **Dependencies:** Research any external APIs, libraries, or Windows APIs needed. Use #context7 if available to read relevant documentation. ALWAYS READ THE DOCUMENTATION FIRST.
4. **Patterns:** Identify how similar features are implemented in ResizeMe

Use official documentation and reputable sources. If uncertain about patterns, research before proposing.

Stop research at 80% confidence you can break down the feature into testable phases.

</research_guide>

版权与许可声明

MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.