How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

advanced-elicitation - Prompt

Name: advanced-elicitation
Author: alezmad

Prompt file imported from alezmad/claudemesh (.windsurf/workflows/bmad/core/tasks/advanced-elicitation.md). Fill in {{methods}} before use. Copyright stays with the author.

MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER DO NOT skip steps or change the sequence HALT immediately when halt-conditions are met Each action xml tag within step xml tag is a REQUIRED action to complete that step Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution

  <csv-structure>
    <i>category: Method grouping (core, structural, risk, etc.)</i>
    <i>method_name: Display name for the method</i>
    <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
    <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
  </csv-structure>

  <context-analysis>
    <i>Use conversation history</i>
    <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
  </context-analysis>

  <smart-selection>
    <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
    <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
    <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
    <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
  </smart-selection>
</step>

<step n="2" title="Present Options and Handle Responses">

  <format>
    **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
    Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:

    1. [Method Name]
    2. [Method Name]
    3. [Method Name]
    4. [Method Name]
    5. [Method Name]
    r. Reshuffle the list with 5 new options
    a. List all methods with descriptions
    x. Proceed / No Further Actions
  </format>

  <response-handling>
    <case n="1-5">
      <i>Execute the selected method using its description from the CSV</i>
      <i>Adapt the method's complexity and output format based on the current context</i>
      <i>Apply the method creatively to the current section content being enhanced</i>
      <i>Display the enhanced version showing what the method revealed or improved</i>
      <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
      <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
        follow the instructions given by the user.</i>
      <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
    </case>
    <case n="r">
      <i>Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
      <i>When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
        potentially the most useful for the document or section being discovered</i>
    </case>
    <case n="x">
      <i>Complete elicitation and proceed</i>
      <i>Return the fully enhanced content back to create-doc.md</i>
      <i>The enhanced content becomes the final version for that section</i>
      <i>Signal completion back to create-doc.md to continue with next section</i>
    </case>
    <case n="a">
      <i>List all methods with their descriptions from the CSV in a compact table</i>
      <i>Allow user to select any method by name or number from the full list</i>
      <i>After selection, execute the method as described in the n="1-5" case above</i>
    </case>
    <case n="direct-feedback">
      <i>Apply changes to current section content and re-present choices</i>
    </case>
    <case n="multiple-numbers">
      <i>Execute methods in sequence on the content, then re-offer choices</i>
    </case>
  </response-handling>
</step>

<step n="3" title="Execution Guidelines">
  <i>Method execution: Use the description from CSV to understand and apply each method</i>
  <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
  <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
  <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
  <i>Focus on actionable insights</i>
  <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
    indicates otherwise)</i>
  <i>Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
    already</i>
  <i>Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution</i>
  <i>Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session</i>
  <i>Each method application builds upon previous enhancements</i>
  <i>Content preservation: Track all enhancements made during elicitation</i>
  <i>Iterative enhancement: Each selected method (1-5) should:</i>
  <i> 1. Apply to the current enhanced version of the content</i>
  <i> 2. Show the improvements made</i>
  <i> 3. Return to the prompt for additional elicitations or completion</i>
</step>

Install advanced-elicitation and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true" methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv" agent-party="{project-root}/_bmad/_config/agent-manifest.csv"> <llm critical="true"> MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER DO NOT skip steps or change the sequence HALT immediately when halt-conditions are met Each action xml tag within step xml tag is a REQUIRED action to complete that step Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution </llm> <integration description="When called from workflow"> <desc>When called during template workflow processing:</desc> 1. Receive or review the current section content that was just generated or 2. Apply elicitation methods iteratively to enhance that specific content 3. Return the enhanced version back when user selects 'x' to proceed and return back 4. The enhanced content replaces the original section content in the output document </integration> <flow> <step n="1" title="Method Registry Loading"> <action>Load and read {{methods}} and {{agent-party}}</action> <csv-structure> category: Method grouping (core, structural, risk, etc.) method_name: Display name for the method description: Rich explanation of what the method does, when to use it, and why it's valuable output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action") </csv-structure> <context-analysis> Use conversation history Analyze: content type, complexity, stakeholder needs, risk level, and creative potential </context-analysis> <smart-selection> 1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential 2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV 3. Select 5 methods: Choose methods that best match the context based on their descriptions 4. Balance approach: Include mix of foundational and specialized techniques as appropriate </smart-selection> </step> <step n="2" title="Present Options and Handle Responses"> <format> **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)** Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed: 1. [Method Name] 2. [Method Name] 3. [Method Name] 4. [Method Name] 5. [Method Name] r. Reshuffle the list with 5 new options a. List all methods with descriptions x. Proceed / No Further Actions </format> <response-handling> <case n="1-5"> Execute the selected method using its description from the CSV Adapt the method's complexity and output format based on the current context Apply the method creatively to the current section content being enhanced Display the enhanced version showing what the method revealed or improved CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response. CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to follow the instructions given by the user. CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations </case> <case n="r"> Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being potentially the most useful for the document or section being discovered </case> <case n="x"> Complete elicitation and proceed Return the fully enhanced content back to create-doc.md The enhanced content becomes the final version for that section Signal completion back to create-doc.md to continue with next section </case> <case n="a"> List all methods with their descriptions from the CSV in a compact table Allow user to select any method by name or number from the full list After selection, execute the method as described in the n="1-5" case above </case> <case n="direct-feedback"> Apply changes to current section content and re-present choices </case> <case n="multiple-numbers"> Execute methods in sequence on the content, then re-offer choices </case> </response-handling> </step> <step n="3" title="Execution Guidelines"> Method execution: Use the description from CSV to understand and apply each method Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection") Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated) Creative application: Interpret methods flexibly based on context while maintaining pattern consistency Focus on actionable insights Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user indicates otherwise) Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory already Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session Each method application builds upon previous enhancements Content preservation: Track all enhancements made during elicitation Iterative enhancement: Each selected method (1-5) should: 1. Apply to the current enhanced version of the content 2. Show the improvements made 3. Return to the prompt for additional elicitations or completion </step> </flow> </task>

{ "prompt": "<task id=\"_bmad/core/tasks/advanced-elicitation.xml\" name=\"Advanced Elicitation\" standalone=\"true\"\n methods=\"{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv\"\n agent-party=\"{project-root}/_bmad/_config/agent-manifest.csv\">\n <llm critical=\"true\">\n MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER\n DO NOT skip steps or change the sequence\n HALT immediately when halt-conditions are met\n Each action xml tag within step xml tag is a REQUIRED action to complete that step\n Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution\n </llm>\n\n <integration description=\"When called from workflow\">\n <desc>When called during template workflow processing:</desc>\n 1. Receive or review the current section content that was just generated or\n 2. Apply elicitation methods iteratively to enhance that specific content\n 3. Return the enhanced version back when user selects 'x' to proceed and return back\n 4. The enhanced content replaces the original section content in the output document\n </integration>\n\n <flow>\n <step n=\"1\" title=\"Method Registry Loading\">\n <action>Load and read {{methods}} and {{agent-party}}</action>\n\n <csv-structure>\n category: Method grouping (core, structural, risk, etc.)\n method_name: Display name for the method\n description: Rich explanation of what the method does, when to use it, and why it's valuable\n output_pattern: Flexible flow guide using → arrows (e.g., \"analysis → insights → action\")\n </csv-structure>\n\n <context-analysis>\n Use conversation history\n Analyze: content type, complexity, stakeholder needs, risk level, and creative potential\n </context-analysis>\n\n <smart-selection>\n 1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential\n 2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV\n 3. Select 5 methods: Choose methods that best match the context based on their descriptions\n 4. Balance approach: Include mix of foundational and specialized techniques as appropriate\n </smart-selection>\n </step>\n\n <step n=\"2\" title=\"Present Options and Handle Responses\">\n\n <format>\n **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**\n Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:\n\n 1. [Method Name]\n 2. [Method Name]\n 3. [Method Name]\n 4. [Method Name]\n 5. [Method Name]\n r. Reshuffle the list with 5 new options\n a. List all methods with descriptions\n x. Proceed / No Further Actions\n </format>\n\n <response-handling>\n <case n=\"1-5\">\n Execute the selected method using its description from the CSV\n Adapt the method's complexity and output format based on the current context\n Apply the method creatively to the current section content being enhanced\n Display the enhanced version showing what the method revealed or improved\n CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.\n CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to\n follow the instructions given by the user.\n CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations\n </case>\n <case n=\"r\">\n Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format\n When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being\n potentially the most useful for the document or section being discovered\n </case>\n <case n=\"x\">\n Complete elicitation and proceed\n Return the fully enhanced content back to create-doc.md\n The enhanced content becomes the final version for that section\n Signal completion back to create-doc.md to continue with next section\n </case>\n <case n=\"a\">\n List all methods with their descriptions from the CSV in a compact table\n Allow user to select any method by name or number from the full list\n After selection, execute the method as described in the n=\"1-5\" case above\n </case>\n <case n=\"direct-feedback\">\n Apply changes to current section content and re-present choices\n </case>\n <case n=\"multiple-numbers\">\n Execute methods in sequence on the content, then re-offer choices\n </case>\n </response-handling>\n </step>\n\n <step n=\"3\" title=\"Execution Guidelines\">\n Method execution: Use the description from CSV to understand and apply each method\n Output pattern: Use the pattern as a flexible guide (e.g., \"paths → evaluation → selection\")\n Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)\n Creative application: Interpret methods flexibly based on context while maintaining pattern consistency\n Focus on actionable insights\n Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user\n indicates otherwise)\n Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory\n already\n Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution\n Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session\n Each method application builds upon previous enhancements\n Content preservation: Track all enhancements made during elicitation\n Iterative enhancement: Each selected method (1-5) should:\n 1. Apply to the current enhanced version of the content\n 2. Show the improvements made\n 3. Return to the prompt for additional elicitations or completion\n </step>\n </flow>\n</task>", "variables": [ "methods" ], "notes": "task-advanced-elicitation", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/alezmad/claudemesh", "path": ".windsurf/workflows/bmad/core/tasks/advanced-elicitation.md", "ref": "138d9aeaf62ac6df7d004e1d6fdfc5f86dcd2b04", "url": "https://github.com/alezmad/claudemesh/blob/138d9aeaf62ac6df7d004e1d6fdfc5f86dcd2b04/.windsurf/workflows/bmad/core/tasks/advanced-elicitation.md", "key": "alezmad/claudemesh/.windsurf/workflows/bmad/core/tasks/advanced-elicitation.md" } } }

advanced-elicitation

About

Install advanced-elicitation and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews