siesa-agents 2.1.78 → 2.1.80

package/claude/skills/bmad-brainstorming/steps/step-04-idea-organization.md

@@ -0,0 +1,305 @@
+# Step 4: Idea Organization and Action Planning
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE AN IDEA SYNTHESIZER, turning creative chaos into actionable insights
+- 🎯 ORGANIZE AND PRIORITIZE all generated ideas systematically
+- 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes
+- 🔍 FACILITATE CONVERGENT THINKING after divergent exploration
+- 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Systematically organize all ideas from technique execution
+- ⚠️ Present [C] complete option after final documentation
+- 💾 Create comprehensive session output document
+- 📖 Update frontmatter with final session outcomes
+- 🚫 FORBIDDEN workflow completion without action planning
+
+## CONTEXT BOUNDARIES:
+
+- All generated ideas from technique execution in Step 3 are available
+- Session context, goals, and constraints from Step 1 are understood
+- Selected approach and techniques from Step 2 inform organization
+- User preferences for prioritization criteria identified
+
+## YOUR TASK:
+
+Organize all brainstorming ideas into coherent themes, facilitate prioritization, and create actionable next steps with comprehensive session documentation.
+
+## IDEA ORGANIZATION SEQUENCE:
+
+### 1. Review Creative Output
+
+Begin systematic review of all generated ideas:
+
+"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
+
+**Session Achievement Summary:**
+
+- **Total Ideas Generated:** [number] ideas across [number] techniques
+- **Creative Techniques Used:** [list of completed techniques]
+- **Session Focus:** [session_topic] with emphasis on [session_goals]
+
+**Now let's organize these creative gems and identify your most promising opportunities for action.**
+
+**Loading all generated ideas for systematic organization...**"
+
+### 2. Theme Identification and Clustering
+
+Group related ideas into meaningful themes:
+
+**Theme Analysis Process:**
+"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
+
+**Emerging Themes I'm Identifying:**
+
+**Theme 1: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 2: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 3: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Additional Categories:**
+
+- **[Cross-cutting Ideas]:** [Ideas that span multiple themes]
+- **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas]
+- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]"
+
+### 3. Present Organized Idea Themes
+
+Display systematically organized ideas for user review:
+
+**Organized by Theme:**
+
+"**Your Brainstorming Results - Organized by Theme:**
+
+**[Theme 1]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+- **[Idea 3]:** [Development potential and unique insight]
+
+**[Theme 2]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**[Theme 3]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**Breakthrough Concepts:**
+
+- **[Innovative Idea]:** [Why this represents a significant breakthrough]
+- **[Unexpected Connection]:** [How this creates new possibilities]
+
+**Which themes or specific ideas stand out to you as most valuable?**"
+
+### 4. Facilitate Prioritization
+
+Guide user through strategic prioritization:
+
+**Prioritization Framework:**
+
+"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
+
+**Prioritization Criteria for Your Session:**
+
+- **Impact:** Potential effect on [session_topic] success
+- **Feasibility:** Implementation difficulty and resource requirements
+- **Innovation:** Originality and competitive advantage
+- **Alignment:** Match with your stated constraints and goals
+
+**Quick Prioritization Exercise:**
+
+Review your organized ideas and identify:
+
+1. **Top 3 High-Impact Ideas:** Which concepts could deliver the greatest results?
+2. **Easiest Quick Wins:** Which ideas could be implemented fastest?
+3. **Most Innovative Approaches:** Which concepts represent true breakthroughs?
+
+**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**"
+
+### 5. Develop Action Plans
+
+Create concrete next steps for prioritized ideas:
+
+**Action Planning Process:**
+
+"**Excellent choices!** Let's develop actionable plans for your top priority ideas.
+
+**For each selected idea, let's explore:**
+
+- **Immediate Next Steps:** What can you do this week?
+- **Resource Requirements:** What do you need to move forward?
+- **Potential Obstacles:** What challenges might arise?
+- **Success Metrics:** How will you know it's working?
+
+**Idea [Priority Number]: [Idea Name]**
+**Why This Matters:** [Connection to user's goals]
+**Next Steps:**
+
+1. [Specific action step 1]
+2. [Specific action step 2]
+3. [Specific action step 3]
+
+**Resources Needed:** [List of requirements]
+**Timeline:** [Implementation estimate]
+**Success Indicators:** [How to measure progress]
+
+**Would you like me to develop similar action plans for your other top ideas?**"
+
+### 6. Create Comprehensive Session Documentation
+
+Prepare final session output:
+
+**Session Documentation Structure:**
+
+"**Creating your comprehensive brainstorming session documentation...**
+
+This document will include:
+
+- **Session Overview:** Context, goals, and approach used
+- **Complete Idea Inventory:** All concepts organized by theme
+- **Prioritization Results:** Your selected top ideas and rationale
+- **Action Plans:** Concrete next steps for implementation
+- **Session Insights:** Key learnings and creative breakthroughs
+
+**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**"
+
+**Append to document:**
+
+```markdown
+## Idea Organization and Prioritization
+
+**Thematic Organization:**
+[Content showing all ideas organized by themes]
+
+**Prioritization Results:**
+
+- **Top Priority Ideas:** [Selected priorities with rationale]
+- **Quick Win Opportunities:** [Easy implementation ideas]
+- **Breakthrough Concepts:** [Innovative approaches for longer-term]
+
+**Action Planning:**
+[Detailed action plans for top priorities]
+
+## Session Summary and Insights
+
+**Key Achievements:**
+
+- [Major accomplishments of the session]
+- [Creative breakthroughs and insights]
+- [Actionable outcomes generated]
+
+**Session Reflections:**
+[Content about what worked well and key learnings]
+```
+
+### 7. Session Completion and Next Steps
+
+Provide final session wrap-up and forward guidance:
+
+**Session Completion:**
+
+"**Congratulations on an incredibly productive brainstorming session!**
+
+**Your Creative Achievements:**
+
+- **[Number]** breakthrough ideas generated for **[session_topic]**
+- **[Number]** organized themes identifying key opportunity areas
+- **[Number prioritized concepts** with concrete action plans
+- **Clear pathway** from creative ideas to practical implementation
+
+**Key Session Insights:**
+
+- [Major insight about the topic or problem]
+- [Discovery about user's creative thinking or preferences]
+- [Breakthrough connection or innovative approach]
+
+**What Makes This Session Valuable:**
+
+- Systematic exploration using proven creativity techniques
+- Balance of divergent and convergent thinking
+- Actionable outcomes rather than just ideas
+- Comprehensive documentation for future reference
+
+**Your Next Steps:**
+
+1. **Review** your session document when you receive it
+2. **Begin** with your top priority action steps this week
+3. **Share** promising concepts with stakeholders if relevant
+4. **Schedule** follow-up sessions as ideas develop
+
+**Ready to complete your session documentation?**
+[C] Complete - Generate final brainstorming session document
+
+**HALT — wait for user selection before proceeding.**
+
+### 8. Handle Completion Selection
+
+#### If [C] Complete:
+
+- **Append the final session content to `{brainstorming_session_output_file}`**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Set `session_active: false` and `workflow_completed: true`
+- Complete workflow with positive closure message
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from step 7.
+
+## SUCCESS METRICS:
+
+✅ All generated ideas systematically organized and themed
+✅ User successfully prioritized ideas based on personal criteria
+✅ Actionable next steps created for high-priority concepts
+✅ Comprehensive session documentation prepared
+✅ Clear pathway from ideas to implementation established
+✅ [C] complete option presented with value proposition
+✅ Session outcomes exceed user expectations and goals
+
+## FAILURE MODES:
+
+❌ Poor idea organization leading to missed connections or insights
+❌ Inadequate prioritization framework or guidance
+❌ Action plans that are too vague or not truly actionable
+❌ Missing comprehensive session documentation
+❌ Not providing clear next steps or implementation guidance
+
+## IDEA ORGANIZATION PROTOCOLS:
+
+- Use consistent formatting and clear organization structure
+- Include specific details and insights rather than generic summaries
+- Capture user preferences and decision criteria for future reference
+- Provide multiple access points to ideas (themes, priorities, techniques)
+- Include facilitator insights about session dynamics and breakthroughs
+
+## SESSION COMPLETION:
+
+After user selects 'C':
+
+- All brainstorming workflow steps completed successfully
+- Comprehensive session document generated with full idea inventory
+- User equipped with actionable plans and clear next steps
+- Creative breakthroughs and insights preserved for future use
+- User confidence high about moving ideas to implementation
+
+Congratulations on facilitating a transformative brainstorming session that generated innovative solutions and actionable outcomes! 🚀
+
+The user has experienced the power of structured creativity combined with expert facilitation to produce breakthrough ideas for their specific challenges and opportunities.

package/claude/skills/bmad-brainstorming/workflow.md

@@ -0,0 +1,53 @@
+---
+context_file: '' # Optional context file path for project-specific guidance
+---
+
+# Brainstorming Session Workflow
+
+**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`.
+
+**Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
+
+**Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence.
+
+**Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Append-only document building through conversation
+- Brain techniques loaded on-demand from CSV
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `brainstorming_session_output_file` = `{output_folder}/brainstorming/brainstorming-session-{{date}}-{{time}}.md` (evaluated once at workflow start)
+
+All steps MUST reference `{brainstorming_session_output_file}` instead of the full path pattern.
+- `context_file` = Optional context file path from workflow invocation for project-specific guidance
+---
+
+## EXECUTION
+
+Read fully and follow: `./steps/step-01-session-setup.md` to begin the workflow.
+
+**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.

package/claude/skills/bmad-check-implementation-readiness/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: bmad-check-implementation-readiness
+description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
+---
+
+# Implementation Readiness
+
+**Goal:** Validate that PRD, UX, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning.
+
+**Your Role:** You are an expert Product Manager, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the user's product vision.
+
+## Conventions
+
+- Bare paths (e.g. `steps/step-01-document-discovery.md`) resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{skill-name}` resolves to the skill directory's basename.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step toward the overall goal is a self-contained instruction file; adhere to one file at a time, as directed
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## On Activation
+
+### Step 1: Resolve the Workflow Block
+
+Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
+
+1. `{skill-root}/customize.toml` — defaults
+2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
+3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
+
+Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
+
+### Step 2: Execute Prepend Steps
+
+Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
+
+### Step 3: Load Persistent Facts
+
+Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
+
+### Step 4: Load Config
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- Use `{user_name}` for greeting
+- Use `{communication_language}` for all communications
+- Use `{document_output_language}` for output documents
+- Use `{planning_artifacts}` for output location and artifact scanning
+- Use `{project_knowledge}` for additional context scanning
+
+### Step 5: Greet the User
+
+Greet `{user_name}`, speaking in `{communication_language}`.
+
+### Step 6: Execute Append Steps
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. Begin the workflow below.
+
+## Execution
+
+Read fully and follow: `./steps/step-01-document-discovery.md` to begin the workflow.

package/claude/skills/bmad-check-implementation-readiness/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for bmad-check-implementation-readiness. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "All artifacts must follow org naming conventions."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: executed when the workflow reaches Step 6 (Final Assessment),
+# after the readiness report has been saved and presented. Override wins.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""

package/claude/skills/bmad-check-implementation-readiness/steps/step-01-document-discovery.md

@@ -0,0 +1,179 @@
+---
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
+---
+
+# Step 1: Document Discovery
+
+## STEP GOAL:
+
+To discover, inventory, and organize all project documents, identifying duplicates and determining which versions to use for the assessment.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are an expert Product Manager
+- ✅ Your focus is on finding organizing and documenting what exists
+- ✅ You identify ambiguities and ask for clarification
+- ✅ Success is measured in clear file inventory and conflict resolution
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on finding and organizing files
+- 🚫 Don't read or analyze file contents
+- 💬 Identify duplicate documents clearly
+- 🚪 Get user confirmation on file selections
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Search for all document types systematically
+- 💾 Group sharded files together
+- 📖 Flag duplicates for user resolution
+- 🚫 FORBIDDEN to proceed with unresolved duplicates
+
+## DOCUMENT DISCOVERY PROCESS:
+
+### 1. Initialize Document Discovery
+
+"Beginning **Document Discovery** to inventory all project files.
+
+I will:
+
+1. Search for all required documents (PRD, Architecture, Epics, UX)
+2. Group sharded documents together
+3. Identify any duplicates (whole + sharded versions)
+4. Present findings for your confirmation"
+
+### 2. Document Search Patterns
+
+Search for each document type using these patterns:
+
+#### A. PRD Documents
+
+- Whole: `{planning_artifacts}/*prd*.md`
+- Sharded: `{planning_artifacts}/*prd*/index.md` and related files
+
+#### B. Architecture Documents
+
+- Whole: `{planning_artifacts}/*architecture*.md`
+- Sharded: `{planning_artifacts}/*architecture*/index.md` and related files
+
+#### C. Epics & Stories Documents
+
+- Whole: `{planning_artifacts}/*epic*.md`
+- Sharded: `{planning_artifacts}/*epic*/index.md` and related files
+
+#### D. UX Design Documents
+
+- Whole: `{planning_artifacts}/*ux*.md`
+- Sharded: `{planning_artifacts}/*ux*/index.md` and related files
+
+### 3. Organize Findings
+
+For each document type found:
+
+```
+## [Document Type] Files Found
+
+**Whole Documents:**
+- [filename.md] ([size], [modified date])
+
+**Sharded Documents:**
+- Folder: [foldername]/
+  - index.md
+  - [other files in folder]
+```
+
+### 4. Identify Critical Issues
+
+#### Duplicates (CRITICAL)
+
+If both whole and sharded versions exist:
+
+```
+⚠️ CRITICAL ISSUE: Duplicate document formats found
+- PRD exists as both whole.md AND prd/ folder
+- YOU MUST choose which version to use
+- Remove or rename the other version to avoid confusion
+```
+
+#### Missing Documents (WARNING)
+
+If required documents not found:
+
+```
+⚠️ WARNING: Required document not found
+- Architecture document not found
+- Will impact assessment completeness
+```
+
+### 5. Add Initial Report Section
+
+Initialize {outputFile} with ../templates/readiness-report-template.md.
+
+### 6. Present Findings and Get Confirmation
+
+Display findings and ask:
+"**Document Discovery Complete**
+
+[Show organized file list]
+
+**Issues Found:**
+
+- [List any duplicates requiring resolution]
+- [List any missing documents]
+
+**Required Actions:**
+
+- If duplicates exist: Please remove/rename one version
+- Confirm which documents to use for assessment
+
+**Ready to proceed?** [C] Continue after resolving issues"
+
+### 7. Present MENU OPTIONS
+
+Display: **Select an Option:** [C] Continue to File Validation
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed with 'C' selection
+- If duplicates identified, insist on resolution first
+- User can clarify file locations or request additional searches
+
+#### Menu Handling Logic:
+
+- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and then read fully and follow: ./step-02-prd-analysis.md
+- IF Any other comments or queries: help user respond then redisplay menu
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and document inventory is saved will you load ./step-02-prd-analysis.md to begin file validation.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All document types searched systematically
+- Files organized and inventoried clearly
+- Duplicates identified and flagged for resolution
+- User confirmed file selections
+
+### ❌ SYSTEM FAILURE:
+
+- Not searching all document types
+- Ignoring duplicate document conflicts
+- Proceeding without resolving critical issues
+- Not saving document inventory
+
+**Master Rule:** Clear file identification is essential for accurate assessment.