@cregis-dev/cckit 0.4.0 → 0.5.0

package/templates/bmad/core/tasks/review-adversarial-general.xml

@@ -1,49 +0,0 @@
-<!-- if possible, run this in a separate subagent or process with read access to the project, 
-  but no context except the content to review -->
-
-<task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)"
-  description="Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something">
-  <objective>Cynically review content and produce findings</objective>
-
-  <inputs>
-    <input name="content" desc="Content to review - diff, spec, story, doc, or any artifact" />
-    <input name="also_consider" required="false"
-      desc="Optional areas to keep in mind during review alongside normal adversarial analysis" />
-  </inputs>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-
-    <i>You are a cynical, jaded reviewer with zero patience for sloppy work</i>
-    <i>The content was submitted by a clueless weasel and you expect to find problems</i>
-    <i>Be skeptical of everything</i>
-    <i>Look for what's missing, not just what's wrong</i>
-    <i>Use a precise, professional tone - no profanity or personal attacks</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Receive Content">
-      <action>Load the content to review from provided input or context</action>
-      <action>If content to review is empty, ask for clarification and abort task</action>
-      <action>Identify content type (diff, branch, uncommitted changes, document, etc.)</action>
-    </step>
-
-    <step n="2" title="Adversarial Analysis" critical="true">
-      <mandate>Review with extreme skepticism - assume problems exist</mandate>
-      <action>Find at least ten issues to fix or improve in the provided content</action>
-    </step>
-
-    <step n="3" title="Present Findings">
-      <action>Output findings as a Markdown list (descriptions only)</action>
-    </step>
-  </flow>
-
-  <halt-conditions>
-    <condition>HALT if zero findings - this is suspicious, re-analyze or ask for guidance</condition>
-    <condition>HALT if content is empty or unreadable</condition>
-  </halt-conditions>
-
-</task>

package/templates/bmad/core/tasks/review-edge-case-hunter.xml

@@ -1,63 +0,0 @@
-<!-- if possible, run this in a separate subagent or process with read access to the project,
-  but no context except the content to review -->
-
-<task id="_bmad/core/tasks/review-edge-case-hunter.xml" name="Edge Case Hunter Review"
-  description="Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.">
-  <objective>You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
-When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
-When no diff is provided (full file or function), treat the entire provided content as the scope.
-Ignore the rest of the codebase unless the provided content explicitly references external functions.</objective>
-
-  <inputs>
-    <input name="content" desc="Content to review - diff, full file, or function" />
-    <input name="also_consider" required="false"
-      desc="Optional areas to keep in mind during review alongside normal edge-case analysis" />
-  </inputs>
-
-  <output-format>Return ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else:
-{
-  "location": "file:line",
-  "trigger_condition": "one-line description (max 15 words)",
-  "guard_snippet": "minimal code sketch that closes the gap",
-  "potential_consequence": "what could actually go wrong (max 15 words)"
-}
-No extra text, no explanations, no markdown wrapping.</output-format>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-
-    <i>Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition</i>
-    <i>Trace each branching path: conditionals, switches, early returns, guard clauses, loops, error handlers</i>
-    <i>Trace each boundary condition: null, undefined, empty, zero, negative, overflow, max-length, type coercion, concurrency, timing</i>
-    <i>Report ONLY paths and conditions that lack handling — discard handled ones silently</i>
-    <i>Do NOT editorialize or add filler — findings only</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Receive Content">
-      <action>Load the content to review from provided input or context</action>
-      <action>If content to review is empty, ask for clarification and abort task</action>
-      <action>Identify content type (diff, full file, or function) to determine scope rules</action>
-    </step>
-
-    <step n="2" title="Exhaustive Path Analysis" critical="true">
-      <mandate>Walk every branching path and boundary condition within scope - report only unhandled ones</mandate>
-      <action>If also_consider input was provided, incorporate those areas into the analysis</action>
-      <action>Enumerate all branching paths and boundary conditions within scope: conditionals, switches, early returns, guard clauses, loops, error handlers, null/empty states, overflow, type edges, concurrency, timing</action>
-      <action>For each path: determine whether the content handles it</action>
-      <action>Collect only the unhandled paths as findings - discard handled ones silently</action>
-    </step>
-
-    <step n="3" title="Present Findings">
-      <action>Output findings as a JSON array following the output-format specification exactly</action>
-    </step>
-  </flow>
-
-  <halt-conditions>
-    <condition>HALT if content is empty or unreadable</condition>
-  </halt-conditions>
-
-</task>

package/templates/bmad/core/tasks/shard-doc.xml

@@ -1,108 +0,0 @@
-<task id="_bmad/core/tasks/shard-doc" name="Shard Document"
-  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document">
-  <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <critical-context>
-    <i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
-  </critical-context>
-
-  <flow>
-    <step n="1" title="Get Source Document">
-      <action>Ask user for the source document path if not provided already</action>
-      <action>Verify file exists and is accessible</action>
-      <action>Verify file is markdown format (.md extension)</action>
-      <action if="file not found or not markdown">HALT with error message</action>
-    </step>
-
-    <step n="2" title="Get Destination Folder">
-      <action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
-      <action>Example: /path/to/architecture.md → /path/to/architecture/</action>
-      <action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
-      <action if="user accepts default">Use the suggested destination path</action>
-      <action if="user provides custom path">Use the custom destination path</action>
-      <action>Verify destination folder exists or can be created</action>
-      <action>Check write permissions for destination</action>
-      <action if="permission denied">HALT with error message</action>
-    </step>
-
-    <step n="3" title="Execute Sharding">
-      <action>Inform user that sharding is beginning</action>
-      <action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
-      <action>Capture command output and any errors</action>
-      <action if="command fails">HALT and display error to user</action>
-    </step>
-
-    <step n="4" title="Verify Output">
-      <action>Check that destination folder contains sharded files</action>
-      <action>Verify index.md was created in destination folder</action>
-      <action>Count the number of files created</action>
-      <action if="no files created">HALT with error message</action>
-    </step>
-
-    <step n="5" title="Report Completion">
-      <action>Display completion report to user including:</action>
-      <i>- Source document path and name</i>
-      <i>- Destination folder path</i>
-      <i>- Number of section files created</i>
-      <i>- Confirmation that index.md was created</i>
-      <i>- Any tool output or warnings</i>
-      <action>Inform user that sharding completed successfully</action>
-    </step>
-
-    <step n="6" title="Handle Original Document">
-      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
-      <action>Present user with options for the original document:</action>
-
-      <ask>What would you like to do with the original document `[source-document-name]`?
-
-        Options:
-        [d] Delete - Remove the original (recommended - shards can always be recombined)
-        [m] Move to archive - Move original to a backup/archive location
-        [k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
-
-        Your choice (d/m/k):</ask>
-
-      <check if="user selects 'd' (delete)">
-        <action>Delete the original source document file</action>
-        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
-        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
-      </check>
-
-      <check if="user selects 'm' (move)">
-        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
-        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
-        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
-        <action if="user accepts default">Use default archive path</action>
-        <action if="user provides custom path">Use custom archive path</action>
-        <action>Create archive directory if it doesn't exist</action>
-        <action>Move original document to archive location</action>
-        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
-      </check>
-
-      <check if="user selects 'k' (keep)">
-        <action>Display warning to user:</action>
-        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
-
-          This creates confusion because:
-          - The discover_inputs protocol may load the wrong version
-          - Updates to one won't reflect in the other
-          - You'll have duplicate content taking up space
-
-          Consider deleting or archiving the original document.</output>
-        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
-      </check>
-    </step>
-  </flow>
-
-  <halt-conditions critical="true">
-    <i>HALT if npx command fails or produces no output files</i>
-  </halt-conditions>
-</task>

package/templates/bmad/core/tasks/workflow.xml

@@ -1,235 +0,0 @@
-<task id="_bmad/core/tasks/workflow.xml" name="Execute Workflow" internal="true">
-  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
-
-  <llm critical="true">
-    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
-    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
-    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
-    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
-    <mandate>NEVER skip a step - YOU are responsible for every steps execution without fail or excuse</mandate>
-  </llm>
-
-  <WORKFLOW-RULES critical="true">
-    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
-    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
-    <rule n="3">Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates
-      to proceed (unless YOLO mode has been activated)</rule>
-  </WORKFLOW-RULES>
-
-  <flow>
-    <step n="1" title="Load and Initialize Workflow">
-      <substep n="1a" title="Load Configuration and Resolve Variables">
-        <action>Read workflow.yaml from provided path</action>
-        <mandate>Load config_source (REQUIRED for all modules)</mandate>
-        <phase n="1">Load external config from config_source path</phase>
-        <phase n="2">Resolve all {config_source}: references with values from config</phase>
-        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
-        <phase n="4">Ask user for input of any variables that are still unknown</phase>
-      </substep>
-
-      <substep n="1b" title="Load Required Components">
-        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
-        <check>If template path → Read COMPLETE template file</check>
-        <check>If validation path → Note path for later loading when needed</check>
-        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
-        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
-      </substep>
-
-      <substep n="1c" title="Initialize Output" if="template-workflow">
-        <action>Resolve default_output_file path with all variables and {{date}}</action>
-        <action>Create output directory if doesn't exist</action>
-        <action>If template-workflow → Write template to output file with placeholders</action>
-        <action>If action-workflow → Skip file creation</action>
-      </substep>
-    </step>
-
-    <step n="2" title="Process Each Instruction Step in Order">
-      <iterate>For each step in instructions:</iterate>
-
-      <substep n="2a" title="Handle Step Attributes">
-        <check>If optional="true" and NOT #yolo → Ask user to include</check>
-        <check>If if="condition" → Evaluate condition</check>
-        <check>If for-each="item" → Repeat step for each item</check>
-        <check>If repeat="n" → Repeat step n times</check>
-      </substep>
-
-      <substep n="2b" title="Execute Step Content">
-        <action>Process step instructions (markdown or XML tags)</action>
-        <action>Replace {{variables}} with values (ask user if unknown)</action>
-        <execute-tags>
-          <tag>action xml tag → Perform the action</tag>
-          <tag>check if="condition" xml tag → Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
-          <tag>ask xml tag → Prompt user and WAIT for response</tag>
-          <tag>invoke-workflow xml tag → Execute another workflow with given inputs and the workflow.xml runner</tag>
-          <tag>invoke-task xml tag → Execute specified task</tag>
-          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
-          <tag>goto step="x" → Jump to specified step</tag>
-        </execute-tags>
-      </substep>
-
-      <substep n="2c" title="Handle template-output Tags">
-        <if tag="template-output">
-          <mandate>Generate content for this section</mandate>
-          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
-          <action>Display generated content</action>
-          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
-              response="a">
-              <action>Start the advanced elicitation workflow {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml</action>
-            </if>
-            <if
-              response="c">
-              <action>Continue to next step</action>
-            </if>
-            <if response="p">
-              <action>Start the party-mode workflow {project-root}/_bmad/core/workflows/party-mode/workflow.md</action>
-            </if>
-            <if
-              response="y">
-              <action>Enter #yolo mode for the rest of the workflow</action>
-            </if>
-          </ask>
-        </if>
-      </substep>
-
-      <substep n="2d" title="Step Completion">
-        <check>If no special tags and NOT #yolo:</check>
-        <ask>Continue to next step? (y/n/edit)</ask>
-      </substep>
-    </step>
-
-    <step n="3" title="Completion">
-      <check>Confirm document saved to output path</check>
-      <action>Report workflow completion</action>
-    </step>
-  </flow>
-
-  <execution-modes>
-    <mode name="normal">Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except yolo MODE</mode>
-    <mode name="yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
-      simulating the remaining discussions with an simulated expert user</mode>
-  </execution-modes>
-
-  <supported-tags desc="Instructions can use these tags">
-    <structural>
-      <tag>step n="X" goal="..." - Define step with number and goal</tag>
-      <tag>optional="true" - Step can be skipped</tag>
-      <tag>if="condition" - Conditional execution</tag>
-      <tag>for-each="collection" - Iterate over items</tag>
-      <tag>repeat="n" - Repeat n times</tag>
-    </structural>
-    <execution>
-      <tag>action - Required action to perform</tag>
-      <tag>action if="condition" - Single conditional action (inline, no closing tag needed)</tag>
-      <tag>check if="condition"&gt;...&lt;/check&gt; - Conditional block wrapping multiple items (closing tag required)</tag>
-      <tag>ask - Get user input (ALWAYS wait for response before continuing)</tag>
-      <tag>goto - Jump to another step</tag>
-      <tag>invoke-workflow - Call another workflow</tag>
-      <tag>invoke-task - Call a task</tag>
-      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
-    </execution>
-    <output>
-      <tag>template-output - Save content checkpoint</tag>
-      <tag>critical - Cannot be skipped</tag>
-      <tag>example - Show example output</tag>
-    </output>
-  </supported-tags>
-
-  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
-    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
-      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
-
-      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
-
-      <flow>
-        <step n="1" title="Parse Input File Patterns">
-          <action>Read input_file_patterns from loaded workflow.yaml</action>
-          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
-        </step>
-
-        <step n="2" title="Load Files Using Smart Strategies">
-          <iterate>For each pattern in input_file_patterns:</iterate>
-
-          <substep n="2a" title="Try Sharded Documents First">
-            <check if="sharded pattern exists">
-              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
-
-              <strategy name="FULL_LOAD">
-                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
-                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
-                <action>Load EVERY matching file completely</action>
-                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="SELECTIVE_LOAD">
-                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
-                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
-                <action>If variable undefined, ask user for value OR infer from context</action>
-                <action>Resolve template to specific file path</action>
-                <action>Load that specific file</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="INDEX_GUIDED">
-                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
-                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
-                <action>Load index.md from sharded directory</action>
-                <action>Parse table of contents, links, section headers</action>
-                <action>Analyze workflow's purpose and objective</action>
-                <action>Identify which linked/referenced documents are likely relevant</action>
-                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
-                  docs, consider deployment docs, skip payment</example>
-                <action>Load all identified relevant documents</action>
-                <action>Store combined content in variable: {pattern_name_content}</action>
-                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
-              </strategy>
-              <action>Mark pattern as RESOLVED, skip to next pattern</action>
-            </check>
-          </substep>
-
-          <substep n="2b" title="Try Whole Document if No Sharded Found">
-            <check if="no sharded matches found OR no sharded pattern exists">
-              <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
-              <check if="matches found">
-                <action>Load ALL matching files completely (no offset/limit)</action>
-                <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
-                <action>Mark pattern as RESOLVED, skip to next pattern</action>
-              </check>
-            </check>
-          </substep>
-
-          <substep n="2c" title="Handle Not Found">
-            <check if="no matches for sharded OR whole">
-              <action>Set {pattern_name_content} to empty string</action>
-              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
-            </check>
-          </substep>
-        </step>
-
-        <step n="3" title="Report Discovery Results">
-          <action>List all loaded content variables with file counts</action>
-          <example>
-            ✓ Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ...
-            ✓ Loaded {architecture_content} from 1 file: Architecture.md
-            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
-            ○ No ux_design files found
-          </example>
-          <note>This gives workflow transparency into what context is available</note>
-        </step>
-      </flow>
-
-    </protocol>
-  </protocols>
-
-  <llm final="true">
-    <critical-rules>
-      • This is the complete workflow execution engine
-      • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml
-      • You MUST have already loaded and processed: {installed_path}/workflow.yaml
-      • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
-      • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be
-      collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section.
-    </critical-rules>
-  </llm>
-</task> 

package/templates/bmad/core/workflows/advanced-elicitation/methods.csv

@@ -1,51 +0,0 @@
-num,category,method_name,description,output_pattern
-1,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
-2,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
-3,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis
-4,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities
-5,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact
-6,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution
-7,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding
-8,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view
-9,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result
-10,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention
-11,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection
-12,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns
-13,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis
-14,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus
-15,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization
-16,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy
-17,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening
-18,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement
-19,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards
-20,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale
-21,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha
-22,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner
-23,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance
-24,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations
-25,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R
-26,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward
-27,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights
-28,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas
-29,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise
-30,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights
-31,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis
-32,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements
-33,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation
-34,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
-35,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
-36,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening
-37,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
-38,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden
-39,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach
-40,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution
-41,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding
-42,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined
-43,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion
-44,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content
-45,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery
-46,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement
-47,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection
-48,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision
-49,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application
-50,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions

package/templates/bmad/core/workflows/advanced-elicitation/workflow.xml

@@ -1,118 +0,0 @@
-<task id="_bmad/core/workflows/advanced-elicitation/workflow.xml" name="Advanced Elicitation"
-  description="Push the LLM to reconsider refine and improve its recent output. Use when the user asks for advanced elicitation"
-  methods="{project-root}/_bmad/core/workflows/advanced-elicitation/methods.csv"
-  agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-    <i>YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`</i>
-  </llm>
-
-  <integration description="When called from workflow">
-    <desc>When called during template workflow processing:</desc>
-    <i>1. Receive or review the current section content that was just generated or</i>
-    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
-    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
-    <i>4. The enhanced content replaces the original section content in the output document</i>
-  </integration>
-
-  <flow>
-    <step n="1" title="Method Registry Loading">
-      <action>Load and read {{methods}} and {{agent-party}}</action>
-
-      <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>
-  </flow>
-</task>