@ckelsoe/prompt-architect 3.1.1 → 3.2.1

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "prompt-architect",
       "source": "./",
       "description": "Analyzes and improves prompts using 27 research-backed frameworks. Intent-based selection routes to the right framework — from ultra-minimal (APE) to agentic (ReAct).",
-      "version": "3.1.1",
+      "version": "3.2.1",
       "keywords": ["prompt-engineering", "prompt-frameworks", "agent-skills"],
       "category": "productivity"
     }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "prompt-architect",
   "description": "27-framework prompt engineering skill for analyzing and improving prompts across 7 intent categories",
-  "version": "3.1.1",
+  "version": "3.2.1",
   "author": {
     "name": "Charles Kelsoe",
     "email": "charles@kelsoe.com"

package/README.md

@@ -568,7 +568,7 @@ Detects all installed AI agents and lets you choose where to install.
 
 ChatGPT natively supports [Agent Skills](https://agentskills.io). Available on Business, Enterprise, Edu, Teachers, and Healthcare plans.
 
-1. Download [`prompt-architect.skill`](https://github.com/ckelsoe/prompt-architect/releases/latest) from GitHub Releases
+1. Download [`prompt-architect.skill`](https://github.com/ckelsoe/prompt-architect/releases/latest/download/prompt-architect.skill) (direct download, always latest version)
 2. In ChatGPT, click your profile icon → **Skills**
 3. Click **New skill** → **Upload from your computer**
 4. Upload the `.skill` file

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ckelsoe/prompt-architect",
-  "version": "3.1.1",
+  "version": "3.2.1",
   "description": "Agent skill for analyzing and improving prompts using 27 research-backed frameworks across 7 intent categories. Works with Claude Code, Gemini CLI, Cursor, Copilot, and 30+ Agent Skills compatible tools.",
   "main": "skills/prompt-architect/SKILL.md",
   "keywords": [
@@ -81,7 +81,7 @@
     "type": "skill",
     "skillName": "prompt-architect",
     "skillPath": "skills/prompt-architect",
-    "version": "3.1.1",
+    "version": "3.2.1",
     "compatibility": {
       "claudeCode": ">=1.0.0"
     },

package/skills/prompt-architect/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 compatibility: Requires no external dependencies. Works with any Agent Skills compatible tool.
 metadata:
   author: ckelsoe
-  version: "3.0.0"
+  version: "3.2.1"
   homepage: https://github.com/ckelsoe/prompt-architect
 ---
 
@@ -163,11 +163,26 @@ Using gathered information:
 
 ### 5. Present Improvements
 
-Show improved prompt with:
-- Clear before/after comparison
-- Explanation of changes made
+Structure your output in this exact order:
+
+**A. Analysis section** (comes first):
+- Framework selected and why
+- Changes made and reasoning
 - Framework components applied
-- Reasoning for improvements
+
+**B. Usage instructions** (transition block, immediately before the prompt):
+
+> **Your revised prompt is ready.**
+> - **New chat**: Copy the prompt below and paste it as your first message in a new conversation.
+> - **Same chat**: Tell the assistant: *"Use the revised prompt you just provided as a new instruction and execute it."*
+
+**C. The revised prompt** (comes last, in a fenced code block):
+- Present as a clean, flat-text block inside triple backticks
+- **No framework section headers** (no "BEFORE:", "BRIDGE:", "CONTEXT:", etc.) — these are scaffolding, not part of the deliverable
+- **No indentation** beyond what the prompt itself genuinely requires
+- **No markdown formatting** inside the block unless the prompt explicitly needs it (e.g., it asks for tables)
+- The user must be able to copy the entire block contents and paste it verbatim with zero editing
+- **Nothing after the code block** — the revised prompt must be the absolute last element in the response. No trailing suggestions, tips, or follow-up text after the closing backticks.
 
 ### 6. Iterate
 
@@ -287,36 +302,32 @@ This example shows the full intent-based flow — detecting intent, using the di
 
 **User**: "Software engineer, early-career devs. Too much corporate-speak. Want it to sound like real humans work there. Requirements must stay. Full rewrite OK."
 
-**Improved Prompt** (BAB):
-
-```
-BEFORE (current state):
-[Paste the current job posting here]
-This posting suffers from: corporate-speak, passive voice, overly formal tone,
-and generic language that doesn't reflect actual team culture.
-
-AFTER (desired state):
-A job posting that sounds like it was written by engineers, for engineers.
-Early-career developers should read it and think "I want to work there."
-It should feel honest, direct, and human — not like legal boilerplate.
-
-BRIDGE (transformation rules):
-1. Replace all passive constructions with active voice
-2. Convert corporate jargon to plain English (e.g., "leverage" → "use")
-3. Add one specific, concrete detail about the team/culture per section
-4. Keep all technical requirements and must-haves verbatim
-5. Target reading level: conversational, not academic
-6. Length: same or shorter than original — cut fluff, don't add it
-```
-
-**Changes Made**:
+**Analysis (BAB framework applied)**:
 1. Locked the current state so the AI understands the starting point
 2. Defined the target state in terms the AI can evaluate against
 3. Made transformation rules explicit and prioritized
 4. Protected non-negotiable elements (requirements) from being changed
 5. Gave a concrete length/tone constraint to prevent over-engineering
 
-Does this match what you need, or should we adjust the tone target or constraints?
+> **Your revised prompt is ready.**
+> - **New chat**: Copy the prompt below and paste it as your first message in a new conversation.
+> - **Same chat**: Tell the assistant: *"Use the revised prompt you just provided as a new instruction and execute it."*
+
+```
+Rewrite the following job posting. The current version suffers from corporate-speak, passive voice, overly formal tone, and generic language that doesn't reflect actual team culture.
+
+[Paste the current job posting here]
+
+The rewritten version should sound like it was written by engineers, for engineers. Early-career developers should read it and think "I want to work there." It should feel honest, direct, and human — not like legal boilerplate.
+
+Follow these rules:
+- Replace all passive constructions with active voice.
+- Convert corporate jargon to plain English (e.g., "leverage" → "use").
+- Add one specific, concrete detail about the team or culture per section.
+- Keep all technical requirements and must-haves verbatim — do not change these.
+- Target reading level: conversational, not academic.
+- Length: same or shorter than the original. Cut fluff, don't add it.
+```
 
 ---