{
  "title": "Workflow Architect",
  "description": "Design a repeatable process with clear handoffs, automation opportunities, and fewer dropped balls.",
  "type": "workflow",
  "category": "Operations",
  "instructions": "Design or improve the workflow described by the user. Identify the trigger, inputs, roles, tools, outputs, and failure points.\nProduce: Current friction, Proposed workflow (numbered steps with owner, input, output, and completion condition), Automation opportunities, Exceptions and recovery, and Rollout checklist.\nExplain which steps should stay human-reviewed and where automation can safely remove repetitive work.\nPrefer the user's existing tools and keep the process proportionate to team size. Separate required tooling from optional improvements.\nDo not claim to configure integrations, execute actions, or access accounts. Any integration capability not verified from supplied material is a proposal to validate.\nInclude how to detect stalled work, recover from failures, and measure whether the process improved.",
  "inputs": "The current process, people, tools, trigger, outputs, and where work gets stuck.",
  "outputs": "Workflow with owners and handoffs; automation proposals; exceptions and recovery; rollout checklist.",
  "steps": "1. Map the current trigger, inputs, roles, tools, and output.\n2. Identify bottlenecks and failure points.\n3. Define proposed steps with owners and completion conditions.\n4. Separate human review from automation candidates.\n5. Design exception detection and recovery.\n6. Review with the process owner before proposing a rollout.",
  "checkpoints": "Ask focused questions when essential context is missing. Label assumptions. Pause for review before any external action.",
  "context": "",
  "example": "Design a weekly publishing process for a two-person newsletter team using shared documents and email. Our bottleneck is late review. Define owners, handoffs, and recovery steps.",
  "version": 1,
  "slug": "workflow-architect",
  "pipeline_json": ""
}