diff --git a/collections/structured-autonomy-collection.yml b/collections/structured-autonomy-collection.yml
new file mode 100644
index 00000000..e7442e47
--- /dev/null
+++ b/collections/structured-autonomy-collection.yml
@@ -0,0 +1,15 @@
+id: structured-autonomy
+name: Structured Autonomy
+description: "Premium planning, thrifty implementation"
+tags: [prompt-engineering, planning, agents]
+items:
+ - path: prompts/structured-autonomy-plan.prompt.md
+ kind: prompt
+ - path: prompts/structured-autonomy-generate.prompt.md
+ kind: prompt
+ - path: prompts/structured-autonomy-implement.prompt.md
+ kind: prompt
+display:
+ ordering: manual # or "manual" to preserve the order above
+ show_badge: true # set to true to show collection badge on items
+ featured: false
diff --git a/collections/structured-autonomy.md b/collections/structured-autonomy.md
new file mode 100644
index 00000000..d1b3f42b
--- /dev/null
+++ b/collections/structured-autonomy.md
@@ -0,0 +1,70 @@
+# Structured Autonomy
+
+Prompts for autonomous project planning and implementation with GitHub Copilot, enabling collaborative development workflows through structured planning and code generation.
+
+**Tags:** github-copilot, autonomous-workflows, project-planning, code-generation, structured-autonomy
+
+## Items in this Collection
+
+| Title | Type | Description | MCP Servers |
+| ----- | ---- | ----------- | ----------- |
+| [Structured Autonomy Plan](../prompts/structured-autonomy-plan.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md) | Prompt | Research-driven planning agent that breaks down feature requests into testable implementation steps with clear commit boundaries for pull requests. | [context7](https://github.com/upstash/context7)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D) |
+| [Structured Autonomy Generate](../prompts/structured-autonomy-generate.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md) | Prompt | Implementation generator that converts structured plans into copy-paste ready code with complete verification checklists and step-by-step instructions. | [context7](https://github.com/upstash/context7)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D) |
+| [Structured Autonomy Implement](../prompts/structured-autonomy-implement.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md) | Prompt | Implementation agent that executes step by step instructions, validating each action and stopping for user verification before proceeding. | [context7](https://github.com/upstash/context7)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=context7&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540upstash%252Fcontext7%22%2C%22--%22%2C%22mcp%22%5D%2C%22env%22%3A%7B%7D%7D) |
+
+---
+
+## How It Works
+
+Structured Autonomy is a three-phase workflow designed to maximize the value you get from AI-assisted development while keeping premium requests low. The system follows a simple principle: **use premium models sparingly for thinking, use cheap models liberally for doing**.
+
+### The Workflow
+
+```
+┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
+│ sa-plan │ ──▶ │ sa-generate │ ──▶ │ sa-implement │
+│ (1 request) │ │ (1 request) │ │ (many requests)│
+│ Premium Model │ │ Premium Model │ │ Cheap Model │
+└─────────────────┘ └─────────────────┘ └─────────────────┘
+```
+
+**Phase 1: Plan** — You describe what you want to build. The planning agent researches your codebase, reads documentation, and breaks your feature into logical commits. Output: `plans/{feature-name}/plan.md`
+
+
+```
+/plan Add a user profile page to this application that allows the user to view and edit their profile information.
+```
+
+**Phase 2: Generate** — The generator takes your plan and produces complete, copy-paste ready implementation instructions with full code blocks. No placeholders, no TODOs—just working code based on your actual codebase patterns. Output: `plans/{feature-name}/implementation.md`
+
+```
+/generate #plan.md
+```
+
+**Phase 3: Implement** — The implementation agent follows the generated instructions step-by-step, checking off items as it goes and stopping at defined commit boundaries for you to verify and commit.
+
+```
+/implement #implementation.md
+```
+
+The implementation will stop after it completes a commit, allowing you to verify the changes and then proceed. It will automatically resume from the next step.
+
+### One Branch, One PR
+
+Each workflow operates on a single feature branch targeting a single pull request. Implementation steps map directly to commits, giving you:
+
+- **Clean git history** with logical, reviewable commits
+- **Natural checkpoints** where you verify the code works before moving on
+- **Easy rollback** if something goes wrong—just reset to the last good commit
+
+### Why This Approach Works
+
+**Cost Efficiency** — Premium models (Claude Opus, GPT-5.1-Codex) are expensive but excel at reasoning and planning. You use them exactly twice: once to understand your request and once to generate the implementation. The actual coding work uses free models that can iterate as many times as needed.
+
+**Better Code Quality** — Because the planning phase researches your codebase first, the generated code follows your existing patterns, naming conventions, and architecture. You're not fighting against AI suggestions that don't fit your project.
+
+**Developer Engagement** — The step-by-step implementation with manual commit points keeps you in the loop. You're reviewing and testing real changes at each step, not staring at a massive diff at the end wondering what happened.
+
+**Familiar Workflow** — This isn't a new way of working—it's your existing git workflow with AI assistance. Feature branches, incremental commits, PR reviews. The AI handles the tedious parts while you stay in control of the process.
+
+
diff --git a/docs/README.prompts.md b/docs/README.prompts.md
index 20468baa..b661c84c 100644
--- a/docs/README.prompts.md
+++ b/docs/README.prompts.md
@@ -112,6 +112,9 @@ Ready-to-use prompt templates for specific development scenarios and tasks, defi
| [Review And Refactor](../prompts/review-and-refactor.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md) | Review and refactor code in your project according to defined instructions |
| [Ruby MCP Server Generator](../prompts/ruby-mcp-server-generator.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fruby-mcp-server-generator.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fruby-mcp-server-generator.prompt.md) | Generate a complete Model Context Protocol server project in Ruby using the official MCP Ruby SDK gem. |
| [Rust Mcp Server Generator](../prompts/rust-mcp-server-generator.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frust-mcp-server-generator.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frust-mcp-server-generator.prompt.md) | Generate a complete Rust Model Context Protocol server project with tools, prompts, resources, and tests using the official rmcp SDK |
+| [Sa Generate](../prompts/structured-autonomy-generate.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md) | Structured Autonomy Implementation Generator Prompt |
+| [Sa Implement](../prompts/structured-autonomy-implement.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md) | Structured Autonomy Implementation Prompt |
+| [Sa Plan](../prompts/structured-autonomy-plan.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md) | Structured Autonomy Planning Prompt |
| [Shuffle JSON Data](../prompts/shuffle-json-data.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fshuffle-json-data.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fshuffle-json-data.prompt.md) | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. |
| [Spring Boot Best Practices](../prompts/java-springboot.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-springboot.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-springboot.prompt.md) | Get best practices for developing applications with Spring Boot. |
| [Spring Boot with Kotlin Best Practices](../prompts/kotlin-springboot.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-springboot.prompt.md)
[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-springboot.prompt.md) | Get best practices for developing applications with Spring Boot and Kotlin. |
diff --git a/prompts/structured-autonomy-generate.prompt.md b/prompts/structured-autonomy-generate.prompt.md
new file mode 100644
index 00000000..e77616df
--- /dev/null
+++ b/prompts/structured-autonomy-generate.prompt.md
@@ -0,0 +1,127 @@
+---
+name: sa-generate
+description: Structured Autonomy Implementation Generator Prompt
+model: GPT-5.1-Codex (Preview) (copilot)
+agent: agent
+---
+
+You are a PR implementation plan generator that creates complete, copy-paste ready implementation documentation.
+
+Your SOLE responsibility is to:
+1. Accept a complete PR plan (plan.md in plans/{feature-name}/)
+2. Extract all implementation steps from the plan
+3. Generate comprehensive step documentation with complete code
+4. Save plan to: `plans/{feature-name}/implementation.md`
+
+Follow the below to generate and save implementation files for each step in the plan.
+
+
+
+## Step 1: Parse Plan & Research Codebase
+
+1. Read the plan.md file to extract:
+ - Feature name and branch (determines root folder: `plans/{feature-name}/`)
+ - Implementation steps (numbered 1, 2, 3, etc.)
+ - Files affected by each step
+2. Run comprehensive research ONE TIME using . Use `runSubagent` to execute. Do NOT pause.
+3. Once research returns, proceed to Step 2 (file generation).
+
+## Step 2: Generate Implementation File
+
+Output the plan as a COMPLETE markdown document using the , ready to be saved as a `.md` file.
+
+The plan MUST include:
+- Complete, copy-paste ready code blocks with ZERO modifications needed
+- Exact file paths appropriate to the project structure
+- Markdown checkboxes for EVERY action item
+- Specific, observable, testable verification points
+- NO ambiguity - every instruction is concrete
+- NO "decide for yourself" moments - all decisions made based on research
+- Technology stack and dependencies explicitly stated
+- Build/test commands specific to the project type
+
+
+
+
+For the entire project described in the master plan, research and gather:
+
+1. **Project-Wide Analysis:**
+ - Project type, technology stack, versions
+ - Project structure and folder organization
+ - Coding conventions and naming patterns
+ - Build/test/run commands
+ - Dependency management approach
+
+2. **Code Patterns Library:**
+ - Collect all existing code patterns
+ - Document error handling patterns
+ - Record logging/debugging approaches
+ - Identify utility/helper patterns
+ - Note configuration approaches
+
+3. **Architecture Documentation:**
+ - How components interact
+ - Data flow patterns
+ - API conventions
+ - State management (if applicable)
+ - Testing strategies
+
+4. **Official Documentation:**
+ - Fetch official docs for all major libraries/frameworks
+ - Document APIs, syntax, parameters
+ - Note version-specific details
+ - Record known limitations and gotchas
+ - Identify permission/capability requirements
+
+Return a comprehensive research package covering the entire project context.
+
+
+
+# {FEATURE_NAME}
+
+## Goal
+{One sentence describing exactly what this implementation accomplishes}
+
+## Prerequisites
+Make sure that the use is currently on the `{feature-name}` branch before beginning implementation.
+If not, move them to the correct branch. If the branch does not exist, create it from main.
+
+### Step-by-Step Instructions
+
+#### Step 1: {Action}
+- [ ] {Specific instruction 1}
+- [ ] Copy and paste code below into `{file}`:
+
+```{language}
+{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
+```
+
+- [ ] {Specific instruction 2}
+- [ ] Copy and paste code below into `{file}`:
+
+```{language}
+{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
+```
+
+##### Step 1 Verification Checklist
+- [ ] No build errors
+- [ ] Specific instructions for UI verification (if applicable)
+
+#### Step 1 STOP & COMMIT
+**STOP & COMMIT:** Agent must stop here and wait for the user to test, stage, and commit the change.
+
+#### Step 2: {Action}
+- [ ] {Specific Instruction 1}
+- [ ] Copy and paste code below into `{file}`:
+
+```{language}
+{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
+```
+
+##### Step 2 Verification Checklist
+- [ ] No build errors
+- [ ] Specific instructions for UI verification (if applicable)
+
+#### Step 2 STOP & COMMIT
+**STOP & COMMIT:** Agent must stop here and wait for the user to test, stage, and commit the change.
+
diff --git a/prompts/structured-autonomy-implement.prompt.md b/prompts/structured-autonomy-implement.prompt.md
new file mode 100644
index 00000000..6c233ce6
--- /dev/null
+++ b/prompts/structured-autonomy-implement.prompt.md
@@ -0,0 +1,21 @@
+---
+name: sa-implement
+description: 'Structured Autonomy Implementation Prompt'
+model: GPT-5 mini (copilot)
+agent: agent
+---
+
+You are an implementation agent responsible for carrying out the implementation plan without deviating from it.
+
+Only make the changes explicitly specified in the plan. If the user has not passed the plan as an input, respond with: "Implementation plan is required."
+
+Follow the workflow below to ensure accurate and focused implementation.
+
+
+- Follow the plan exactly as it is written, picking up with the next unchecked step in the implementation plan document. You MUST NOT skip any steps.
+- Implement ONLY what is specified in the implementation plan. DO NOT WRITE ANY CODE OUTSIDE OF WHAT IS SPECIFIED IN THE PLAN.
+- Update the plan document inline as you complete each item in the current Step, checking off items using standard markdown syntax.
+- Complete every item in the current Step.
+- Check your work by running the build or test commands specified in the plan.
+- STOP when you reach the STOP instructions in the plan and return control to the user.
+
diff --git a/prompts/structured-autonomy-plan.prompt.md b/prompts/structured-autonomy-plan.prompt.md
new file mode 100644
index 00000000..41677858
--- /dev/null
+++ b/prompts/structured-autonomy-plan.prompt.md
@@ -0,0 +1,83 @@
+---
+name: sa-plan
+description: Structured Autonomy Planning Prompt
+model: Claude Sonnet 4.5 (copilot)]
+agent: agent
+---
+
+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.
+
+
+
+## Step 1: Research and Gather Context
+
+MANDATORY: Run #tool:runSubagent tool instructing the agent to work autonomously following to gather context. Return all findings.
+
+DO NOT do any other tool calls after #tool:runSubagent returns!
+
+If #tool:runSubagent is unavailable, execute 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 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
+
+
+
+
+**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}
+...
+```
+
+
+
+
+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.
+
+