{
 "schema": "aiblocks-page/1",
 "id": "agency-specialized-master-plan-architect",
 "type": "agent",
 "name": "Implementation brief writer",
 "summary": "Turn a software change into a written implementation plan with risks, files to change, test steps and a rollback path. No code is written.",
 "headline": "Implementation brief writer",
 "subhead": "Describe the change you want and share how your project is laid out. It explains the problem, attacks its own plan to find what could break, and lists every file to add, change or delete. You get one Markdown plan to review before anyone writes code.",
 "job": {
  "id": "build-software",
  "name": "Build and ship software"
 },
 "level": "intermediate",
 "thinking": "high",
 "tested": true,
 "updated": "2026-11-03",
 "first_published": "2026-10-26",
 "inputs": [
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  },
  {
   "type": "codebase",
   "required": false,
   "label": "Codebase",
   "what": "a project's code, in a folder or repo the AI can open"
  },
  {
   "type": "product_spec",
   "required": false,
   "label": "Product spec",
   "what": "what to build and how to tell it's done: a product requirements doc, feature spec or user stories with acceptance criteria"
  }
 ],
 "outputs": [
  {
   "type": "plan",
   "required": true,
   "label": "Plan",
   "what": "a dated plan: what to do, in what order, with a decision rule for each step"
  },
  {
   "type": "audit_report",
   "required": true,
   "label": "Audit report",
   "what": "findings with evidence, severity, missing inputs and next actions"
  }
 ],
 "you_give": [
  "The change you want, in a few plain sentences, and why",
  "How your project is built, such as a file tree and its package or config files",
  "What must not change in this work (optional)",
  "Known problems, past outages or risky areas (optional)",
  "Who will do the work, such as a person or an AI coding tool (optional)"
 ],
 "you_get": [
  "A short explanation of the problem and the main design ideas behind the fix",
  "A risk review with at least three ways the plan could fail",
  "A list of what is out of scope for this change",
  "A file list marked new, change or delete, each with one reason",
  "A test list and a rollback path"
 ],
 "use_when": [
  "You are about to change a database, an API or a core module and want the risks written down first.",
  "A teammate or an AI coding tool will do the work, and you want a plan to hand over that sets the limits.",
  "You inherited a codebase and want to understand why it works as it does before you change it.",
  "You want a second view that challenges your plan, not one that agrees with it."
 ],
 "skip_when": [
  "You want the code written. Use the Full stack developer.",
  "You are choosing between designs and want decision records. Use the Software architect.",
  "You want a quick prototype with a small scope. Use the Software prototype designer.",
  "You have no project files or goal to share. The plan would be guesses."
 ],
 "output_sample": {
  "input": [
   "The change you want and why",
   "Your file tree and package or config files",
   "What must not change (optional)",
   "Past problems or risky areas (optional)"
  ],
  "prerequisites": [
   "Access to your project's file list, so the plan is based on real files"
  ],
  "output": [
   {
    "name": "Concept primer",
    "contains": "The core problem, the design ideas that apply and how well-known systems handle the same thing."
   },
   {
    "name": "Risk review",
    "contains": "At least three ways the plan could fail, what else it could break and what is out of scope."
   },
   {
    "name": "Blueprint",
    "contains": "A diagram of the main parts and a file list marked new, change or delete, each with a reason."
   },
   {
    "name": "Validation",
    "contains": "Tests to run, edge cases and the manual checks a person does before accepting the work."
   },
   {
    "name": "Rollback",
    "contains": "The steps to undo the change and how the system behaves if a dependency fails."
   },
   {
    "name": "Assumptions and gaps",
    "contains": "Everything the agent could not verify, so you can check it before work starts."
   }
  ]
 },
 "output_shape": "1. CONCEPT PRIMER\n  Core problem | Design ideas that apply | How similar systems solve it | How the design stays lean\n\n2. RISK REVIEW\n  Fragile assumptions | What else could break | Not allowed in this change | Permission and safety limits\n  (at least three failure risks)\n\n3. BLUEPRINT\n  <diagram of the main parts>\n  [NEW] <file> | <one reason>\n  [CHANGE] <file> | <one reason>\n  [DELETE] <file> | <one reason>\n\n4. VALIDATION\n  Automated tests | Edge cases | Manual checks\n\n5. ROLLBACK\n  Steps to undo | What happens if a dependency fails\n\nASSUMPTIONS AND GAPS\n  <what could not be verified>",
 "how_to_use": [
  "Download the pack and add it to your AI as a skill. If you cannot, paste SKILL.md and then references/source-agent.md into a new chat.",
  "Paste your goal and your project details. A file tree and the package or config files are the minimum. Say MISSING for anything you cannot share.",
  "Say \"Write the plan. Do not write code.\" Your AI asks once for anything it needs.",
  "Read the risk review first. Check each risk against what you know about your project, and correct any wrong assumption.",
  "Ask for a revised plan, then give the final plan to the person or tool doing the work. Ask them to stick to the file list."
 ],
 "checks": [
  "The result addresses your actual task and cites the evidence used.",
  "Examples, role-play experience and targets are kept separate from verified results.",
  "Claims of tests, memory, tool access or completed actions match what actually happened."
 ],
 "next": [
  {
   "name": "Software developer from specifications",
   "url": "https://useaiblocks.com/skills/spec-builder",
   "why": "Build it"
  },
  {
   "name": "RAG pipeline implementation planner",
   "url": "https://useaiblocks.com/skills/agency-engineering-rag-pipeline-engineer",
   "why": "Build it"
  }
 ],
 "source": {
  "by": "Michael Sitarzewski and Agency Agents contributors",
  "repo": "msitarzewski/agency-agents",
  "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/specialized/specialized-master-plan-architect.md",
  "licence": "MIT",
  "original_name": "Master Plan Architect",
  "commit": "b37b5bb33b78f2c1d6567d98e25ca818e3259219"
 },
 "credits": [
  {
   "title": "Master Plan Architect",
   "by": "Michael Sitarzewski and Agency Agents contributors",
   "url": "https://github.com/msitarzewski/agency-agents/blob/b37b5bb33b78f2c1d6567d98e25ca818e3259219/specialized/specialized-master-plan-architect.md",
   "used": "Original agent profile, preserved in references/source-agent.md; AI Blocks adds setup and review instructions."
  }
 ],
 "files": [
  "LICENSE",
  "references/source-agent.md",
  "SETUP.md",
  "source.json"
 ],
 "links": {
  "page": "https://useaiblocks.com/agents/agency-specialized-master-plan-architect",
  "markdown": "https://useaiblocks.com/agents/agency-specialized-master-plan-architect.md",
  "json": "https://useaiblocks.com/agents/agency-specialized-master-plan-architect.json",
  "instructions": "https://useaiblocks.com/skills/agency-specialized-master-plan-architect/SKILL.md",
  "download": "https://useaiblocks.com/skills/agency-specialized-master-plan-architect.zip",
  "api_item": "https://useaiblocks.com/api/v1/items/agency-specialized-master-plan-architect",
  "api_document": "https://useaiblocks.com/api/v1/documents/agent/agency-specialized-master-plan-architect",
  "mcp": "https://useaiblocks.com/mcp"
 }
}
