@ckelsoe/prompt-architect 3.0.2 → 3.2.0

package/adapters/README.md

@@ -1,267 +1,75 @@
-# Prompt Architect — Cross-Platform Adapters
-
-This folder contains ready-to-use versions of the Prompt Architect skill for AI tools beyond those that natively support the [Agent Skills standard](https://agentskills.io).
-
-Tools that support Agent Skills (Claude Code, Gemini CLI, Cursor, Copilot, and 30+ others) can use the native `skills/prompt-architect/SKILL.md` directly. The adapters here are for tools that need a reformatted version.
-
----
-
-## Why adapters exist
-
-The `skills/prompt-architect/SKILL.md` file follows the [Agent Skills standard](https://agentskills.io) — an open format supported by 30+ AI tools. Tools like Claude Code and Gemini CLI can discover and load SKILL.md natively.
-
-For tools that don't support Agent Skills natively, the adapters solve two problems:
-- The YAML frontmatter is removed (some tools render it as raw text)
-- File-loading references are replaced with self-contained instructions
-- Each adapter is formatted exactly as the target tool expects
-
-**The framework knowledge (all 27 frameworks, intent categories, clarification questions) is identical across all adapters.** Only the packaging changes.
-
----
-
-## What "installing" means for each tool
-
-| Tool | Where instructions go | Auto-discovered? | How to activate |
-|------|----------------------|------------------|-----------------|
-| **Claude Code** | `~/.claude/skills/` or `/plugin install` | ✅ Yes — automatic | Ask Claude to improve a prompt |
-| **Gemini CLI** | `~/.gemini/skills/` or `gemini skills install` | ✅ Yes — native Agent Skills | Ask Gemini to improve a prompt |
-| **Agent Skills (30+ tools)** | `~/.agents/skills/` | ✅ Yes — universal path | Ask the agent to improve a prompt |
-| **OpenAI Codex CLI** | `AGENTS.md` in your project root | ✅ Yes — read per session | Ask Codex to improve a prompt |
-| **Cursor** | `.cursor/rules/prompt-architect.mdc` | ✅ Yes — loaded automatically | Ask Cursor to improve a prompt |
-| **GitHub Copilot** | `.github/copilot-instructions.md` | ✅ Yes — loaded per workspace | Ask Copilot to improve a prompt |
-| **Windsurf** | `.windsurfrules` in your project root | ✅ Yes — read per session | Ask Windsurf to improve a prompt |
-| **Any LLM API / ChatGPT / custom** | Paste into system prompt field | Manual | Call the API / open the chat |
-
----
-
-## Adapter files in this folder
-
-| File | Use with | What to do with it |
-|------|----------|--------------------|
-| `system-prompt.md` | Any LLM (API, ChatGPT, Gemini, etc.) | Paste contents into the system prompt field |
-| `for-gemini-cli.md` | Gemini CLI | Installation guide (native SKILL.md works directly) |
-| `for-openai-codex-cli.md` | OpenAI Codex CLI | Copy contents into `AGENTS.md` in your project root |
-| `for-cursor.mdc` | Cursor editor | Copy file to `.cursor/rules/prompt-architect.mdc` |
-| `for-github-copilot.md` | GitHub Copilot | Copy contents into `.github/copilot-instructions.md` |
-| `for-windsurf.md` | Windsurf editor | Copy contents into `.windsurfrules` in your project root |
-
----
-
-## Limitations vs. Claude Code
-
-Claude Code's version has one capability the adapters cannot replicate:
-
-> **On-demand reference loading**: When Claude Code applies a framework, it can load the detailed 600-800 line reference doc for that specific framework (e.g., `references/frameworks/co-star.md`). This gives it richer examples and selection criteria.
-
-The adapters work from:
-1. The full intent-based selection system (all 7 categories, all 27 frameworks)
-2. The complete clarification question sets
-3. The LLM's training knowledge of each framework
-
-For most use cases, this is equivalent. The reference docs add depth for edge cases and complex applications.
-
----
-
-## Installation instructions by tool
-
-### Claude Code (Plugin System)
-
-Claude Code now supports plugins with a marketplace. You can install directly:
-
-```shell
-# Option A: Add the marketplace and install
-/plugin marketplace add ckelsoe/prompt-architect
-/plugin install prompt-architect@prompt-architect-marketplace
-
-# Option B: Load directly for testing
-claude --plugin-dir /path/to/prompt-architect
-```
-
-The legacy `npm install -g` method also still works — the interactive installer will set up `~/.claude/skills/`.
-
----
-
-### Gemini CLI
-
-Gemini CLI natively supports Agent Skills — the `SKILL.md` works directly, no adapter needed.
-
-```bash
-# Option A: Install from GitHub
-gemini skills install https://github.com/ckelsoe/prompt-architect.git
-
-# Option B: Manual copy
-cp -r skills/prompt-architect/ ~/.gemini/skills/prompt-architect/
-
-# Option C: After npm install
-gemini skills link "$(npm root -g)/@ckelsoe/prompt-architect/skills/prompt-architect"
-```
-
-See `adapters/for-gemini-cli.md` for full details.
-
----
-
-### OpenAI Codex CLI
-
-**What is AGENTS.md?**
-The Codex CLI reads `AGENTS.md` from your project root at the start of each session. It's the Codex equivalent of Claude Code's `CLAUDE.md` — project-level instructions that shape how the AI behaves.
-
-**Steps:**
-```bash
-# Option A: Create a new AGENTS.md with just this skill
-cp /path/to/adapters/for-openai-codex-cli.md ./AGENTS.md
-
-# Option B: Append to an existing AGENTS.md
-cat /path/to/adapters/for-openai-codex-cli.md >> ./AGENTS.md
-
-# Option C: After npm install
-cat node_modules/@ckelsoe/prompt-architect/adapters/for-openai-codex-cli.md >> ./AGENTS.md
-```
-
-**Verify it's working:**
-```
-codex "Help me improve this prompt: write a blog post"
-```
-You should see intent detection, framework recommendation, and clarifying questions.
-
----
-
-### Cursor
-
-**What is .cursor/rules/?**
-Cursor loads `.mdc` files from `.cursor/rules/` in your project. Each file can apply always or only for specific file patterns. The `prompt-architect.mdc` adapter uses `alwaysApply: false` so it only activates when you ask for prompt help — it won't interfere with normal coding.
-
-**Steps:**
-```bash
-# Create the rules directory if it doesn't exist
-mkdir -p .cursor/rules
-
-# Copy the adapter
-cp /path/to/adapters/for-cursor.mdc .cursor/rules/prompt-architect.mdc
-
-# Or after npm install
-cp node_modules/@ckelsoe/prompt-architect/adapters/for-cursor.mdc .cursor/rules/prompt-architect.mdc
-```
-
-**Verify it's working:**
-Open Cursor, ask: `"Help me improve this prompt: write a blog post"`
-
-**Note:** Cursor will load this rule when the description matches the context of your request. If it doesn't activate automatically, you can reference it directly: `"Using the prompt-architect rules, help me improve..."`
-
----
-
-### GitHub Copilot
-
-**What is copilot-instructions.md?**
-GitHub Copilot reads `.github/copilot-instructions.md` from your repository root. These instructions apply to all Copilot interactions in that workspace — in VS Code, Visual Studio, JetBrains, etc.
-
-**Important**: This file applies to ALL Copilot interactions in the repo, not just prompt engineering tasks. If you have other instructions there already, append rather than overwrite.
-
-**Steps:**
-```bash
-# Create the .github directory if needed
-mkdir -p .github
-
-# Option A: New file
-cp /path/to/adapters/for-github-copilot.md .github/copilot-instructions.md
-
-# Option B: Append to existing
-cat /path/to/adapters/for-github-copilot.md >> .github/copilot-instructions.md
-
-# Or after npm install
-cat node_modules/@ckelsoe/prompt-architect/adapters/for-github-copilot.md >> .github/copilot-instructions.md
-```
-
-**Verify it's working:**
-In a Copilot chat window, ask: `"Help me improve this prompt: write a blog post"`
-
----
-
-### Windsurf
-
-**What is .windsurfrules?**
-Windsurf reads `.windsurfrules` from your project root. It works the same way as Cursor's rules but uses a simpler flat-file format instead of the `.mdc` directory structure.
-
-**Steps:**
-```bash
-# Option A: New file
-cp /path/to/adapters/for-windsurf.md ./.windsurfrules
-
-# Option B: Append to existing .windsurfrules
-cat /path/to/adapters/for-windsurf.md >> ./.windsurfrules
-
-# Or after npm install
-cat node_modules/@ckelsoe/prompt-architect/adapters/for-windsurf.md >> ./.windsurfrules
-```
-
-**Verify it's working:**
-Ask Windsurf: `"Help me improve this prompt: write a blog post"`
-
----
-
-### Any LLM API or Chat Interface (Universal)
-
-Use `system-prompt.md` as your system prompt. This works with:
-- OpenAI API (`gpt-4o`, `o1`, etc.)
-- Anthropic API (when not using Claude Code)
-- Google Gemini API
-- ChatGPT (paste into a Custom GPT's "Instructions" field)
-- Any chat interface that has a system prompt or custom instructions field
-
-**For ChatGPT Custom GPT:**
-1. Go to [chat.openai.com](https://chat.openai.com) → Explore GPTs → Create a GPT
-2. Click "Configure"
-3. Copy the entire contents of `system-prompt.md`
-4. Paste into the "Instructions" field
-5. Name it "Prompt Architect"
-6. Save and publish (or keep private)
-
-**For direct API use:**
-```python
-import openai
-
-with open("adapters/system-prompt.md", "r") as f:
-    system_prompt = f.read()
-
-response = openai.chat.completions.create(
-    model="gpt-4o",
-    messages=[
-        {"role": "system", "content": system_prompt},
-        {"role": "user", "content": "Help me improve this prompt: write a blog post"}
-    ]
-)
-```
-
----
-
-## After npm install — quick reference
-
-If you installed via `npm install -g @ckelsoe/prompt-architect`, the adapters are at:
-
-```
-# Find your npm global prefix
-npm prefix -g
-
-# Adapters are at:
-$(npm prefix -g)/lib/node_modules/@ckelsoe/prompt-architect/adapters/
-```
-
-Or find them directly:
-```bash
-ls $(npm root -g)/@ckelsoe/prompt-architect/adapters/
-```
-
----
-
-## Troubleshooting
-
-**The AI isn't using the framework system — it's just answering directly.**
-→ Try explicitly triggering it: `"Use the Prompt Architect framework to improve this prompt: [your prompt]"`
-
-**The AI says it can't load the reference files.**
-→ This is expected. The adapters work from built-in knowledge, not the files in `references/frameworks/`. This is not an error — just a difference from the Claude Code version.
-
-**The instructions are too long and getting truncated.**
-→ Use the Claude Code version instead, which handles large reference docs via progressive loading. Alternatively, use only the `system-prompt.md` content and ask the AI to focus on a subset of frameworks.
-
-**Copilot is applying prompt engineering to all my code requests, not just when I ask.**
-→ The Copilot adapter uses trigger language to activate only when you ask about prompts. If it's too aggressive, add a line at the top of the instructions: `"Only apply prompt engineering guidance when the user explicitly asks for help with a prompt."`
+# Prompt Architect — Adapters
+
+Most AI tools now support the [Agent Skills standard](https://agentskills.io) natively and can use `skills/prompt-architect/SKILL.md` directly. The adapters in this folder are for the remaining tools that need a reformatted version.
+
+---
+
+## Installation by tool
+
+### Agent Skills compatible tools (recommended)
+
+These tools read `SKILL.md` natively. No adapter needed — just install to their skills directory:
+
+| Tool | Install method |
+|------|---------------|
+| **Claude Code** | `npm install -g @ckelsoe/prompt-architect` or `/plugin marketplace add ckelsoe/prompt-architect` |
+| **ChatGPT** | Download [`prompt-architect.skill`](https://github.com/ckelsoe/prompt-architect/releases/latest) → Profile → Skills → Upload |
+| **Gemini CLI** | `gemini skills install https://github.com/ckelsoe/prompt-architect.git` |
+| **Cursor** | Copy `skills/prompt-architect/` to `.agents/skills/` or `.cursor/skills/` in your project |
+| **GitHub Copilot** | Copy `skills/prompt-architect/` to `.github/skills/` or `~/.copilot/skills/` |
+| **OpenAI Codex** | Copy `skills/prompt-architect/` to `.agents/skills/` in your project |
+| **VS Code** | Copy `skills/prompt-architect/` to `.agents/skills/` in your project |
+| **Roo Code** | Copy `skills/prompt-architect/` to `.agents/skills/` or `~/.agents/skills/` |
+| **Kiro, Amp, Junie, Goose, OpenHands, etc.** | Copy to `~/.agents/skills/` (universal path) |
+
+Or use the interactive installer to auto-detect and install:
+```bash
+npx @ckelsoe/prompt-architect
+```
+
+### Windsurf
+
+Windsurf does not yet support Agent Skills natively. Use the adapter file:
+
+```bash
+# New file
+cp adapters/for-windsurf.md ./.windsurfrules
+
+# Or append to existing
+cat adapters/for-windsurf.md >> ./.windsurfrules
+```
+
+### Any LLM API or Chat Interface
+
+Use `system-prompt.md` as your system prompt. Works with OpenAI API, Anthropic API, Google Gemini API, or any tool with a system prompt / custom instructions field.
+
+**Direct link:** [system-prompt.md on GitHub](https://raw.githubusercontent.com/ckelsoe/prompt-architect/main/adapters/system-prompt.md)
+
+**For ChatGPT Custom GPTs** (free/personal plans without Skills support):
+1. Open the [system-prompt.md](https://raw.githubusercontent.com/ckelsoe/prompt-architect/main/adapters/system-prompt.md) link
+2. Copy the entire contents
+3. Go to [chat.openai.com](https://chat.openai.com) → Explore GPTs → Create a GPT → Configure
+4. Paste into the "Instructions" field
+5. Name it "Prompt Architect" and save
+
+---
+
+## Adapter files in this folder
+
+| File | Use with |
+|------|----------|
+| `system-prompt.md` | Any LLM API, Custom GPTs, or tool without Agent Skills support |
+| `for-windsurf.md` | Windsurf editor (`.windsurfrules` format) |
+
+---
+
+## Why most adapters were removed (v3.0)
+
+In v2.x, this folder contained adapters for Cursor, GitHub Copilot, OpenAI Codex, and Gemini CLI. All of these tools have since adopted the [Agent Skills standard](https://agentskills.io) and now read `SKILL.md` natively. The old adapter files were:
+
+- `for-cursor.mdc` → Cursor now scans `.cursor/skills/` and `.agents/skills/`
+- `for-github-copilot.md` → Copilot now scans `.github/skills/` and `~/.copilot/skills/`
+- `for-openai-codex-cli.md` → Codex now scans `.agents/skills/`
+- `for-gemini-cli.md` → Gemini CLI scans `~/.gemini/skills/` and `~/.agents/skills/`
+
+If you need these for legacy setups, check the [v2.1.4 release](https://github.com/ckelsoe/prompt-architect/tree/v2.1.4/adapters).

package/adapters/for-windsurf.md

@@ -1,136 +1,136 @@
-# Prompt Architect — Windsurf Adapter
-
-## How to install
-
-Copy this file's contents into `.windsurfrules` in your project root.
-
-```bash
-cat node_modules/@ckelsoe/claude-skill-prompt-architect/adapters/for-windsurf.md >> .windsurfrules
-```
-
-**Important**: If you already have a `.windsurfrules` file, use `>>` to append, not `>` to overwrite.
-
-Windsurf reads `.windsurfrules` automatically at the start of each session.
-
----
-
-## Prompt Engineering Skill
-
-When asked to improve, write, fix, or help with a prompt — or when a user's prompt seems vague or incomplete — act as a prompt engineering expert. Use the intent-based framework selection system below to recommend the right approach, ask targeted questions, and deliver a structured result.
-
-**Activate for requests like:**
-- "Help me improve this prompt"
-- "Write a better prompt for..."
-- "What framework should I use?"
-- "This prompt isn't working, fix it"
-
-**Do not apply prompt engineering to normal code or task requests** — only activate when the user is explicitly asking for help with a prompt.
-
----
-
-## Intent-Based Framework Selection
-
-Identify **primary intent** first, then select within that category.
-
-**A. RECOVER** → **RPEF**
-*"I have an output but need/lost the prompt"*
-
-**B. CLARIFY** → **Reverse Role Prompting**
-*"I know roughly what I want but struggle to specify it"*
-
-**C. CREATE** — New content from scratch
-
-Signal → Framework:
-- Ultra-minimal, one-off → APE
-- Simple, expertise-driven → RTF
-- Simple, context-driven → CTF
-- Role + context + outcome → RACE
-- Multiple variants needed → CRISPE
-- Business deliverable with KPIs → BROKE
-- Explicit rules/constraints → CARE or TIDD-EC
-- Audience, tone, style critical → CO-STAR
-- Multi-step procedure → RISEN
-- Data transformation → RISE-IE
-- Content with reference examples → RISE-IX
-
-TIDD-EC: use when you need separate Do/Don't lists.
-CARE: use when rules and examples are combined.
-
-**D. TRANSFORM** — Improving existing content
-
-Signal → Framework:
-- Rewrite / refactor / convert → BAB
-- Iterative quality improvement → Self-Refine
-- Compress or densify → Chain of Density
-- Outline-first then expand → Skeleton of Thought
-
-**E. REASON** — Reasoning or calculation
-
-Signal → Framework:
-- Numerical / zero-shot calculation → Plan-and-Solve (PS+)
-- Multi-hop with dependencies → Least-to-Most
-- First-principles needed first → Step-Back
-- Multiple approaches to compare → Tree of Thought
-- Verify conditions weren't missed → RCoT
-- Linear step-by-step → Chain of Thought
-
-**F. CRITIQUE** — Stress-testing or verifying
-
-Signal → Framework:
-- General quality improvement → Self-Refine
-- Align to principle/standard → CAI Critique-Revise
-- Strongest opposing argument → Devil's Advocate
-- Find failure modes before launch → Pre-Mortem
-- Verify reasoning conditions → RCoT
-
-**G. AGENTIC** → **ReAct**
-*"Task requires tools; each result informs the next step"*
-
----
-
-## Clarification Questions (3-5 at a time)
-
-CO-STAR: Context, audience, tone, style, objective, format?
-RISEN: Role, principles, steps, success criteria, constraints?
-RISE-IE: Role, input format, processing steps, output expectations?
-RISE-IX: Role, instructions, workflow steps, reference examples?
-TIDD-EC: Task type, exact steps, dos, don'ts, examples, context?
-CTF: Situation/background, exact task, output format?
-RTF: Expertise needed, exact task, output format?
-APE: Core action, why it's needed, what success looks like?
-BAB: Current state, desired state, transformation rules?
-RACE: Role/expertise, action, situational context, expectation?
-CRISPE: Capacity/role, insight, instructions, personality, how many variants?
-BROKE: Background, role, objective, measurable key results, evolve?
-CARE: Context, specific ask, rules/constraints, examples of good output?
-Tree of Thought: Problem, 2-5 branches, evaluation criteria?
-ReAct: Goal, available tools, stop condition?
-Skeleton of Thought: Topic, number of points, expansion depth?
-Step-Back: Original question, governing principle?
-Least-to-Most: Full problem, ordered subproblems?
-Plan-and-Solve: Problem with all numbers/variables?
-Chain of Thought: Problem, reasoning steps, verification?
-Chain of Density: Content, iterations, optimization goal?
-Self-Refine: Output to improve, feedback dimensions, stop condition?
-CAI Critique-Revise: The principle, output to critique?
-Devil's Advocate: Position to attack, dimensions, rank severity?
-Pre-Mortem: Project/decision, time horizon, domains?
-RCoT: Question with all conditions, initial answer to verify?
-RPEF: Output to reverse-engineer, input data if available?
-Reverse Role: Intent, domain of expertise, batch or conversational?
-
----
-
-## Process
-
-1. Detect intent (A-G above)
-2. Ask 3-5 clarifying questions
-3. Apply the selected framework
-4. Show before/after comparison with explanation
-5. Iterate based on feedback
-
-## When NOT to Use Frameworks
-
-Skip when: prompt is already complete, factual lookup, casual conversation, or user says "just do it."
-
-Rule of thumb: Use a framework when there's a gap between what was asked and what's needed.
+# Prompt Architect — Windsurf Adapter
+
+## How to install
+
+Copy this file's contents into `.windsurfrules` in your project root.
+
+```bash
+cat node_modules/@ckelsoe/claude-skill-prompt-architect/adapters/for-windsurf.md >> .windsurfrules
+```
+
+**Important**: If you already have a `.windsurfrules` file, use `>>` to append, not `>` to overwrite.
+
+Windsurf reads `.windsurfrules` automatically at the start of each session.
+
+---
+
+## Prompt Engineering Skill
+
+When asked to improve, write, fix, or help with a prompt — or when a user's prompt seems vague or incomplete — act as a prompt engineering expert. Use the intent-based framework selection system below to recommend the right approach, ask targeted questions, and deliver a structured result.
+
+**Activate for requests like:**
+- "Help me improve this prompt"
+- "Write a better prompt for..."
+- "What framework should I use?"
+- "This prompt isn't working, fix it"
+
+**Do not apply prompt engineering to normal code or task requests** — only activate when the user is explicitly asking for help with a prompt.
+
+---
+
+## Intent-Based Framework Selection
+
+Identify **primary intent** first, then select within that category.
+
+**A. RECOVER** → **RPEF**
+*"I have an output but need/lost the prompt"*
+
+**B. CLARIFY** → **Reverse Role Prompting**
+*"I know roughly what I want but struggle to specify it"*
+
+**C. CREATE** — New content from scratch
+
+Signal → Framework:
+- Ultra-minimal, one-off → APE
+- Simple, expertise-driven → RTF
+- Simple, context-driven → CTF
+- Role + context + outcome → RACE
+- Multiple variants needed → CRISPE
+- Business deliverable with KPIs → BROKE
+- Explicit rules/constraints → CARE or TIDD-EC
+- Audience, tone, style critical → CO-STAR
+- Multi-step procedure → RISEN
+- Data transformation → RISE-IE
+- Content with reference examples → RISE-IX
+
+TIDD-EC: use when you need separate Do/Don't lists.
+CARE: use when rules and examples are combined.
+
+**D. TRANSFORM** — Improving existing content
+
+Signal → Framework:
+- Rewrite / refactor / convert → BAB
+- Iterative quality improvement → Self-Refine
+- Compress or densify → Chain of Density
+- Outline-first then expand → Skeleton of Thought
+
+**E. REASON** — Reasoning or calculation
+
+Signal → Framework:
+- Numerical / zero-shot calculation → Plan-and-Solve (PS+)
+- Multi-hop with dependencies → Least-to-Most
+- First-principles needed first → Step-Back
+- Multiple approaches to compare → Tree of Thought
+- Verify conditions weren't missed → RCoT
+- Linear step-by-step → Chain of Thought
+
+**F. CRITIQUE** — Stress-testing or verifying
+
+Signal → Framework:
+- General quality improvement → Self-Refine
+- Align to principle/standard → CAI Critique-Revise
+- Strongest opposing argument → Devil's Advocate
+- Find failure modes before launch → Pre-Mortem
+- Verify reasoning conditions → RCoT
+
+**G. AGENTIC** → **ReAct**
+*"Task requires tools; each result informs the next step"*
+
+---
+
+## Clarification Questions (3-5 at a time)
+
+CO-STAR: Context, audience, tone, style, objective, format?
+RISEN: Role, principles, steps, success criteria, constraints?
+RISE-IE: Role, input format, processing steps, output expectations?
+RISE-IX: Role, instructions, workflow steps, reference examples?
+TIDD-EC: Task type, exact steps, dos, don'ts, examples, context?
+CTF: Situation/background, exact task, output format?
+RTF: Expertise needed, exact task, output format?
+APE: Core action, why it's needed, what success looks like?
+BAB: Current state, desired state, transformation rules?
+RACE: Role/expertise, action, situational context, expectation?
+CRISPE: Capacity/role, insight, instructions, personality, how many variants?
+BROKE: Background, role, objective, measurable key results, evolve?
+CARE: Context, specific ask, rules/constraints, examples of good output?
+Tree of Thought: Problem, 2-5 branches, evaluation criteria?
+ReAct: Goal, available tools, stop condition?
+Skeleton of Thought: Topic, number of points, expansion depth?
+Step-Back: Original question, governing principle?
+Least-to-Most: Full problem, ordered subproblems?
+Plan-and-Solve: Problem with all numbers/variables?
+Chain of Thought: Problem, reasoning steps, verification?
+Chain of Density: Content, iterations, optimization goal?
+Self-Refine: Output to improve, feedback dimensions, stop condition?
+CAI Critique-Revise: The principle, output to critique?
+Devil's Advocate: Position to attack, dimensions, rank severity?
+Pre-Mortem: Project/decision, time horizon, domains?
+RCoT: Question with all conditions, initial answer to verify?
+RPEF: Output to reverse-engineer, input data if available?
+Reverse Role: Intent, domain of expertise, batch or conversational?
+
+---
+
+## Process
+
+1. Detect intent (A-G above)
+2. Ask 3-5 clarifying questions
+3. Apply the selected framework
+4. Show before/after comparison with explanation
+5. Iterate based on feedback
+
+## When NOT to Use Frameworks
+
+Skip when: prompt is already complete, factual lookup, casual conversation, or user says "just do it."
+
+Rule of thumb: Use a framework when there's a gap between what was asked and what's needed.