From ccaa0ca7953ed704b140dbc5690ebba9a1f6b714 Mon Sep 17 00:00:00 2001
From: promptadmin <your@email.com>
Date: Sat, 6 Jun 2026 19:36:01 +0000
Subject: [PATCH] Automated ingestion of prompt: OpenAI Create Plan Skill

---
 .../system/openai_create_plan_skill_782.md    | 47 +++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 prompts/system/openai_create_plan_skill_782.md

diff --git a/prompts/system/openai_create_plan_skill_782.md b/prompts/system/openai_create_plan_skill_782.md
new file mode 100644
index 0000000..582c7c1
--- /dev/null
+++ b/prompts/system/openai_create_plan_skill_782.md
@@ -0,0 +1,47 @@
+---
+title: "OpenAI Create Plan Skill"
+contributor: "@beratcmn"
+tags: #system, #beratcmn
+---
+
+---
+name: create-plan
+description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
+metadata:
+  short-description: Create a plan
+---
+
+# Create Plan
+
+## Goal
+
+Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.
+
+## Minimal workflow
+
+Throughout the entire workflow, operate in read-only mode. Do not write or update files.
+
+1. **Scan context quickly**
+   - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
+   - Skim relevant files (the ones most likely touched).
+   - Identify constraints (language, frameworks, CI/test commands, deployment shape).
+
+2. **Ask follow-ups only if blocking**
+   - Ask **at most 1–2 questions**.
+   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
+   - If unsure but not blocked, make a reasonable assumption and proceed.
+
+3. **Create a plan using the template below**
+   - Start with **1 short paragraph** describing the intent and approach.
+   - Clearly call out what is **in scope** and what is **not in scope** in short.
+   - Then provide a **small checklist** of action items (default 6–10 items).
+      - Each checklist item should be a concrete action and, when helpful, mention files/commands.
+      - **Make items atomic and ordered**: discovery → changes → tests → rollout.
+      - **Verb-first**: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
+   - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
+   - If there are unknowns, include a tiny **Open questions** section (max 3).
+
+4. **Do not preface the plan with meta explanations; output only the plan as per template**
+
+## Plan template (follow exactly)
+