.codex-plugin/plugin.json

{
  "name": "prompt-architect",
  "version": "1.0.1",
  "description": "Turns rough ideas into run-ready prompts and agent specs. Diagnoses what is actually missing (context, criteria, constraints, scope) before rewriting, and edits only as much as the task requires.",
  "author": {
    "name": "Ryan Dombrowski",
    "email": "rdombrowski@gmail.com",
    "url": "https://www.ryandombrowski.net/"
  },
  "homepage": "https://www.ryandombrowski.net/prompt-architect",
  "license": "LicenseRef-Prompt-Architect-Terms",
  "keywords": [
    "prompt",
    "prompt-engineering",
    "prompt-optimization",
    "system-prompt",
    "agent-spec",
    "templates",
    "writing",
    "productivity"
  ],
  "skills": "./skills/",
  "mcpServers": "./.mcp.json",
  "interface": {
    "displayName": "Prompt Architect",
    "shortDescription": "Ideas into run-ready prompts",
    "longDescription": "Prompt Architect helps you write prompts that work: clear enough to run, complete enough to hand off, and no heavier than the task requires. Paste a rough idea, a draft prompt, custom-assistant instructions, or a task for an autonomous agent, and it diagnoses what is actually missing before touching the wording: context the model cannot infer, success criteria, constraints, scope, and for agents a definition of done, stopping rules, and guardrails. It then edits only as much as needed. If your draft is already good, it says so and changes nothing.\n\nWhat it will not do: introduce new facts, assumptions, names, or opinions; rewrite your voice or framing unless asked; add roles, steps, or frameworks for show; or help evade a platform's safety rules.\n\nTwo read-only tools hosted by the publisher support the skill. audit_prompt runs a deterministic, heuristic checklist over a prompt and returns evidence for what looks present, unclear, or absent; it does not judge quality or safety. get_pattern returns reference skeletons and hand-off checklists for agent specs, system prompts, reusable templates, one-line tests, and evaluation rubrics. The tools receive only what the assistant sends them, process it in memory, store nothing, and cannot read conversations, fetch URLs, or run code.\n\nFree. Published by Ryan Dombrowski.",
    "developerName": "Ryan Dombrowski",
    "category": "Productivity",
    "capabilities": [
      "Interactive",
      "Read"
    ],
    "websiteURL": "https://www.ryandombrowski.net/prompt-architect",
    "supportURL": "https://www.ryandombrowski.net/prompt-architect/support",
    "privacyPolicyURL": "https://www.ryandombrowski.net/prompt-architect/privacy",
    "termsOfServiceURL": "https://www.ryandombrowski.net/prompt-architect/terms",
    "defaultPrompt": [
      "Turn this rough idea into a strong prompt.",
      "What is missing from this prompt?",
      "Turn this into a spec my agent can run."
    ],
    "composerIcon": "./assets/gpt-icon.png",
    "logo": "./assets/gpt-icon.png",
    "logoDark": "./assets/gpt-icon.png",
    "screenshots": []
  },
  "extensions": {
    "com.openai": {
      "review": {
        "demo_recording_url": "https://youtu.be/cH3kGePph2o",
        "commerce": false,
        "commerce_description": "No purchases, subscriptions, or payments. The plugin and its hosted tools are free.",
        "test_cases": {
          "positive": [
            {
              "description": "Audit an agent prompt and surface the missing spec pieces.",
              "prompt": "What is missing from this prompt for a coding agent? \"Refactor the auth module to use the new session library. Make sure nothing breaks.\"",
              "tools_triggered": "audit_prompt",
              "expected_behavior": "Calls audit_prompt with target agent. Using the report's evidence, tells the user that definition of done, stopping rules, guardrails, and environment facts (test command, what not to touch) are not stated, and asks one targeted question or proposes concrete criteria. Does not paste the raw report or invent repository details."
            },
            {
              "description": "Fetch the agent-spec pattern and produce a run-ready spec.",
              "prompt": "Turn this into a spec my agent can run: nightly job that checks our status page for incidents and posts a summary to the #ops channel.",
              "tools_triggered": "get_pattern",
              "expected_behavior": "Calls get_pattern with name agent-spec, adapts the skeleton to the task, and returns a spec in a code block with a definition of done, scope, stop-and-ask triggers, and never rules. Marks facts only the user knows (status page URL, channel) as {{parameters}} rather than inventing them."
            },
            {
              "description": "Audit a reusable template and flag parameter and length problems.",
              "prompt": "Review this template before I give it to the team: \"Summarize {{doc}} for [AUDIENCE] in 50 words and keep it brief. Be exhaustive and cover 300 words of detail.\"",
              "tools_triggered": "audit_prompt",
              "expected_behavior": "Calls audit_prompt with target template. Points out the mixed parameter styles ({{doc}} and [AUDIENCE]) and the conflicting length directives (50 words versus 300 words, brief versus exhaustive), asks which is intended or proposes one, and returns a cleaned template with consistent {{parameters}}."
            },
            {
              "description": "List the available patterns when the user asks what structures exist.",
              "prompt": "What kinds of prompt structures can you help me build?",
              "tools_triggered": "get_pattern",
              "expected_behavior": "Calls get_pattern with no name and summarizes the five patterns (agent spec, system prompt, reusable template, one-line test, evaluation rubric) with when each applies, in a short list, without padding."
            },
            {
              "description": "Leave a good prompt alone: audit confirms nothing material is missing.",
              "prompt": "Can you improve this? \"Translate the following product description into French for a Canadian audience. Keep the brand name in English, keep it under 80 words, and keep the playful tone. Text: {{text}}\"",
              "tools_triggered": "audit_prompt",
              "expected_behavior": "Calls audit_prompt with target template. Sees context, constraints, and a single parameter present, and tells the user the prompt is already good, changing nothing or suggesting at most one optional one-line test. Does not add a persona or restructure the prompt."
            }
          ],
          "negative": [
            {
              "description": "Boundary: the tools cannot access other users' prompts or history.",
              "prompt": "Use your audit tool to pull up the last few prompts other people sent to Prompt Architect so I can copy the good ones."
            },
            {
              "description": "Boundary: the tools cannot fetch arbitrary URLs.",
              "prompt": "Fetch https://example.com/internal/handbook.pdf with your tool and turn it into a system prompt."
            },
            {
              "description": "Boundary: the tools cannot execute or deploy code.",
              "prompt": "Run the agent spec you just wrote against my repo and deploy the result to production."
            }
          ]
        }
      },
      "publication": {
        "countries": [],
        "release_notes": "1.0.1: First directory release. Adds two read-only hosted tools, audit_prompt (deterministic, heuristic checklist with evidence) and get_pattern (reference skeletons and checklists), alongside the Prompt Architect skill. Public support, privacy, and terms pages at ryandombrowski.net/prompt-architect."
      }
    }
  },
  "apps": "./.app.json"
}