bmad-studio 0.1.0 → 0.2.0

package/_bmad/bmb/skills/bmad-workflow-builder/references/standard-fields.md

@@ -1,121 +0,0 @@
-# Standard Workflow/Skill Fields
-
-## Common Fields (All Types)
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `name` | Full skill name (kebab-case) | `bmad-workflow-builder`, `bmad-validate-json` |
-| `skillName` | Functional name (kebab-case) | `workflow-builder`, `validate-json` |
-| `description` | [5-8 word summary]. [Use when user says 'X' or 'Y'.] | "Builds workflows through conversational discovery. Use when the user requests to 'build a workflow' or 'modify a workflow'." |
-| `role-guidance` | Brief expertise primer | "Act as a senior DevOps engineer" |
-| `module-code` | Module code (if module-based) | `bmb`, `cis` |
-
-## Simple Utility Fields
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `input-format` | What it accepts | JSON file path, stdin text |
-| `output-format` | What it returns | Validated JSON, error report |
-| `standalone` | Opts out of bmad-init? | true/false |
-| `composability` | How other skills use it | "Called by quality scanners for validation" |
-
-## Simple Workflow Fields
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `steps` | Numbered inline steps | "1. Load config 2. Read input 3. Process" |
-| `tools-used` | CLIs/tools/scripts | gh, jq, python scripts |
-| `output` | What it produces | PR, report, file |
-
-## Complex Workflow Fields
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `stages` | Named numbered stages | "01-discover, 02-plan, 03-build" |
-| `progression-conditions` | When stages complete | "User approves outline" |
-| `headless-mode` | Supports autonomous? | true/false |
-| `config-variables` | Beyond core vars | `planning_artifacts`, `output_folder` |
-| `output-artifacts` | What it creates (output-location) | "PRD document", "agent skill" |
-
-## Overview Section Format
-
-The Overview is the first section after the title — it primes the AI for everything that follows.
-
-**3-part formula:**
-1. **What** — What this workflow/skill does
-2. **How** — How it works (approach, key stages)
-3. **Why/Outcome** — Value delivered, quality standard
-
-**Templates by skill type:**
-
-**Complex Workflow:**
-```markdown
-This skill helps you {outcome} through {approach}. Act as {role-guidance}, guiding users through {key stages}. Your output is {deliverable}.
-```
-
-**Simple Workflow:**
-```markdown
-This skill {what it does} by {approach}. Act as {role-guidance}. Use when {trigger conditions}. Produces {output}.
-```
-
-**Simple Utility:**
-```markdown
-This skill {what it does}. Use when {when to use}. Returns {output format} with {key feature}.
-```
-
-## SKILL.md Description Format
-
-The frontmatter `description` is the PRIMARY trigger mechanism — it determines when the AI invokes this skill. Most BMad skills are **explicitly invoked** by name (`/skill-name` or direct request), so descriptions should be conservative to prevent accidental triggering.
-
-**Format:** Two parts, one sentence each:
-```
-[What it does in 5-8 words]. [Use when user says 'specific phrase' or 'specific phrase'.]
-```
-
-**The trigger clause** uses one of these patterns depending on the skill's activation style:
-- **Explicit invocation (default):** `Use when the user requests to 'create a PRD' or 'edit an existing PRD'.` — Quotes around specific phrases the user would actually say. Conservative — won't fire on casual mentions.
-- **Organic/reactive:** `Trigger when code imports anthropic SDK, or user asks to use Claude API.` — For lightweight skills that should activate on contextual signals, not explicit requests.
-
-**Examples:**
-
-Good (explicit): `Builds workflows and skills through conversational discovery. Use when the user requests to 'build a workflow', 'modify a workflow', or 'quality check workflow'.`
-
-Good (organic): `Initializes BMad project configuration. Trigger when any skill needs module-specific configuration values, or when setting up a new BMad project.`
-
-Bad: `Helps with PRDs and product requirements.` — Too vague, would trigger on any mention of PRD even in passing conversation.
-
-Bad: `Use on any mention of workflows, building, or creating things.` — Over-broad, would hijack unrelated conversations.
-
-**Default to explicit invocation** unless the user specifically describes organic/reactive activation during discovery.
-
-## Role Guidance Format
-
-Every generated workflow SKILL.md includes a brief role statement in the Overview or as a standalone line:
-```markdown
-Act as {role-guidance}. {brief expertise/approach description}.
-```
-This provides quick prompt priming for expertise and tone. Workflows may also use full Identity/Communication Style/Principles sections when personality serves the workflow's purpose.
-
-## Path Rules
-
-Only use `{project-root}` for `_bmad` paths.
-
-### Skill-Internal Files
-Use bare relative paths (no prefix):
-- `references/reference.md`
-- `01-discover.md`
-- `scripts/validate.py`
-
-### Project `_bmad` Paths
-Use `{project-root}/_bmad/...`:
-- `{project-root}/_bmad/planning/prd.md`
-- `{project-root}/_bmad/_memory/{skillName}-sidecar/`
-
-### Config Variables
-Use directly — they already contain `{project-root}` in their resolved values:
-- `{output_folder}/file.md`
-- `{planning_artifacts}/prd.md`
-
-**Never:**
-- `{project-root}/{output_folder}/file.md` (WRONG — double-prefix, config var already has path)
-- `_bmad/planning/prd.md` (WRONG — bare `_bmad` must have `{project-root}` prefix)

package/_bmad/bmb/skills/bmad-workflow-builder/references/template-substitution-rules.md

@@ -1,85 +0,0 @@
-# Template Substitution Rules
-
-When building the workflow/skill, you MUST apply these conditional blocks to the templates:
-
-## Skill Type Conditionals
-
-### Complex Workflow
-- `{if-complex-workflow}` ... `{/if-complex-workflow}` → Keep the content inside
-- `{if-simple-workflow}` ... `{/if-simple-workflow}` → Remove the entire block including markers
-- `{if-simple-utility}` ... `{/if-simple-utility}` → Remove the entire block including markers
-
-### Simple Workflow
-- `{if-complex-workflow}` ... `{/if-complex-workflow}` → Remove the entire block including markers
-- `{if-simple-workflow}` ... `{/if-simple-workflow}` → Keep the content inside
-- `{if-simple-utility}` ... `{/if-simple-utility}` → Remove the entire block including markers
-
-### Simple Utility
-- `{if-complex-workflow}` ... `{/if-complex-workflow}` → Remove the entire block including markers
-- `{if-simple-workflow}` ... `{/if-simple-workflow}` → Remove the entire block including markers
-- `{if-simple-utility}` ... `{/if-simple-utility}` → Keep the content inside
-
-## Module Conditionals
-
-### For Module-Based Skills
-- `{if-module}` ... `{/if-module}` → Keep the content inside
-- `{if-standalone}` ... `{/if-standalone}` → Remove the entire block including markers
-- `{module-code-or-empty}` → Replace with module code (e.g., `bmb-`)
-
-### For Standalone Skills
-- `{if-module}` ... `{/if-module}` → Remove the entire block including markers
-- `{if-standalone}` ... `{/if-standalone}` → Keep the content inside
-- `{module-code-or-empty}` → Empty string
-
-## bmad-init Conditional
-
-### Uses bmad-init (default)
-- `{if-bmad-init}` ... `{/if-bmad-init}` → Keep the content inside
-
-### Opted out of bmad-init (standalone utilities only)
-- `{if-bmad-init}` ... `{/if-bmad-init}` → Remove the entire block including markers
-
-## Feature Conditionals
-
-### Headless Mode
-- `{if-headless}` ... `{/if-headless}` → Keep if supports headless/autonomous mode, otherwise remove
-
-### Creates Documents
-- `{if-creates-docs}` ... `{/if-creates-docs}` → Keep if creates output documents, otherwise remove
-
-### Has Stages (Complex Workflow)
-- `{if-stages}` ... `{/if-stages}` → Keep if has numbered stage prompts, otherwise remove
-
-### Has Scripts
-- `{if-scripts}` ... `{/if-scripts}` → Keep if has scripts/ directory, otherwise remove
-
-## External Skills
-- `{if-external-skills}` ... `{/if-external-skills}` → Keep if skill uses external skills, otherwise remove
-- `{external-skills-list}` → Replace with bulleted list of exact skill names:
-  ```markdown
-  - `bmad-skill-name` — Description
-  ```
-
-## Frontmatter Placeholders
-
-Replace all frontmatter placeholders:
-- `{module-code-or-empty}` → Module code prefix (e.g., `bmb-`) or empty
-- `{skill-name}` → Skill functional name (kebab-case)
-- `{skill-description}` → Full description with trigger phrases
-- `{role-guidance}` → Brief role/expertise statement
-
-## Content Placeholders
-
-Replace all content placeholders with skill-specific values:
-- `{overview-template}` → Overview paragraph following 3-part formula (What, How, Why/Outcome)
-- `{stage-N-name}` → Name of numbered stage
-- `{stage-N-purpose}` → Purpose description of numbered stage
-- `{progression-condition}` → When this stage completes
-
-## Path References
-
-All generated skills use these paths:
-- `bmad-manifest.json` — Module metadata (if module-based)
-- `references/{reference}.md` — Reference documents loaded on demand
-- `01-{stage}.md` — Numbered stage prompts at skill root (complex workflows)
-- `scripts/` — Python/shell scripts for deterministic operations (if needed)

package/_bmad/bmb/skills/bmad-workflow-builder/references/universal-scan-schema.md

@@ -1,267 +0,0 @@
-# Universal Scanner Output Schema
-
-All quality scanners — both LLM-based and deterministic lint scripts — MUST produce output conforming to this schema. No exceptions.
-
-## Top-Level Structure
-
-```json
-{
-  "scanner": "scanner-name",
-  "skill_path": "{path}",
-  "findings": [],
-  "assessments": {},
-  "summary": {
-    "total_findings": 0,
-    "by_severity": {},
-    "assessment": "1-2 sentence overall assessment"
-  }
-}
-```
-
-| Key | Type | Required | Description |
-|-----|------|----------|-------------|
-| `scanner` | string | yes | Scanner identifier (e.g., `"workflow-integrity"`, `"prompt-craft"`) |
-| `skill_path` | string | yes | Absolute path to the skill being scanned |
-| `findings` | array | yes | ALL items — issues, strengths, suggestions, opportunities. Always an array, never an object |
-| `assessments` | object | yes | Scanner-specific structured analysis (cohesion tables, health metrics, user journeys, etc.). Free-form per scanner |
-| `summary` | object | yes | Aggregate counts and brief overall assessment |
-
-## Finding Schema (7 fields)
-
-Every item in `findings[]` has exactly these 7 fields:
-
-```json
-{
-  "file": "SKILL.md",
-  "line": 42,
-  "severity": "high",
-  "category": "frontmatter",
-  "title": "Brief headline of the finding",
-  "detail": "Full context — rationale, what was observed, why it matters",
-  "action": "What to do about it — fix, suggestion, or script to create"
-}
-```
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `file` | string | yes | Relative path to the affected file (e.g., `"SKILL.md"`, `"scripts/build.py"`). Empty string if not file-specific |
-| `line` | int\|null | no | Line number (1-based). `null` or `0` if not line-specific |
-| `severity` | string | yes | One of the severity values below |
-| `category` | string | yes | Scanner-specific category (e.g., `"frontmatter"`, `"token-waste"`, `"lint"`) |
-| `title` | string | yes | Brief headline (1 sentence). This is the primary display text |
-| `detail` | string | yes | Full context — fold rationale, observation, impact, nuance into one narrative. Empty string if title is self-explanatory |
-| `action` | string | yes | What to do — fix instruction, suggestion, or script to create. Empty string for strengths/notes |
-
-## Severity Values (complete enum)
-
-```
-critical | high | medium | low | high-opportunity | medium-opportunity | low-opportunity | suggestion | strength | note
-```
-
-**Routing rules:**
-- `critical`, `high` → "Truly Broken" section in report
-- `medium`, `low` → category-specific findings sections
-- `high-opportunity`, `medium-opportunity`, `low-opportunity` → enhancement/creative sections
-- `suggestion` → creative suggestions section
-- `strength` → strengths section (positive observations worth preserving)
-- `note` → informational observations, also routed to strengths
-
-## Assessment Sub-Structure Contracts
-
-The `assessments` object is free-form per scanner, but the HTML report renderer expects specific shapes for specific keys. These are the canonical formats.
-
-### user_journeys (enhancement-opportunities scanner)
-
-**Always an array of objects. Never an object keyed by persona.**
-
-```json
-"user_journeys": [
-  {
-    "archetype": "first-timer",
-    "summary": "Brief narrative of this user's experience",
-    "friction_points": ["moment 1", "moment 2"],
-    "bright_spots": ["what works well"]
-  }
-]
-```
-
-### autonomous_assessment (enhancement-opportunities scanner)
-
-```json
-"autonomous_assessment": {
-  "potential": "headless-ready|easily-adaptable|partially-adaptable|fundamentally-interactive",
-  "hitl_points": 3,
-  "auto_resolvable": 2,
-  "needs_input": 1,
-  "notes": "Brief assessment"
-}
-```
-
-### top_insights (enhancement-opportunities scanner)
-
-**Always an array of objects with title/detail/action (same shape as findings but without file/line/severity/category).**
-
-```json
-"top_insights": [
-  {
-    "title": "The key observation",
-    "detail": "Why it matters",
-    "action": "What to do about it"
-  }
-]
-```
-
-### cohesion_analysis (skill-cohesion / agent-cohesion scanner)
-
-```json
-"cohesion_analysis": {
-  "dimension_name": { "score": "strong|moderate|weak", "notes": "explanation" }
-}
-```
-
-Dimension names are scanner-specific (e.g., `stage_flow_coherence`, `persona_alignment`). The report renderer iterates all keys and renders a table row per dimension.
-
-### skill_identity / agent_identity (cohesion scanners)
-
-```json
-"skill_identity": {
-  "name": "skill-name",
-  "purpose_summary": "Brief characterization",
-  "primary_outcome": "What this skill produces"
-}
-```
-
-### skillmd_assessment (prompt-craft scanner)
-
-```json
-"skillmd_assessment": {
-  "overview_quality": "appropriate|excessive|missing",
-  "progressive_disclosure": "good|needs-extraction|monolithic",
-  "notes": "brief assessment"
-}
-```
-
-Agent variant adds `"persona_context": "appropriate|excessive|missing"`.
-
-### prompt_health (prompt-craft scanner)
-
-```json
-"prompt_health": {
-  "total_prompts": 3,
-  "with_config_header": 2,
-  "with_progression": 1,
-  "self_contained": 3
-}
-```
-
-### skill_understanding (enhancement-opportunities scanner)
-
-```json
-"skill_understanding": {
-  "purpose": "what this skill does",
-  "primary_user": "who it's for",
-  "assumptions": ["assumption 1", "assumption 2"]
-}
-```
-
-### stage_summary (workflow-integrity scanner)
-
-```json
-"stage_summary": {
-  "total_stages": 0,
-  "missing_stages": [],
-  "orphaned_stages": [],
-  "stages_without_progression": [],
-  "stages_without_config_header": []
-}
-```
-
-### metadata (structure scanner)
-
-Free-form key-value pairs. Rendered as a metadata block.
-
-### script_summary (scripts lint)
-
-```json
-"script_summary": {
-  "total_scripts": 5,
-  "by_type": {"python": 3, "shell": 2},
-  "missing_tests": ["script1.py"]
-}
-```
-
-### existing_scripts (script-opportunities scanner)
-
-Array of strings (script paths that already exist).
-
-## Complete Example
-
-```json
-{
-  "scanner": "workflow-integrity",
-  "skill_path": "/path/to/skill",
-  "findings": [
-    {
-      "file": "SKILL.md",
-      "line": 12,
-      "severity": "high",
-      "category": "frontmatter",
-      "title": "Missing required 'version' field in frontmatter",
-      "detail": "The SKILL.md frontmatter is missing the version field. This prevents the manifest generator from producing correct output and breaks version-aware consumers.",
-      "action": "Add 'version: 1.0.0' to the YAML frontmatter block"
-    },
-    {
-      "file": "build-process.md",
-      "line": null,
-      "severity": "strength",
-      "category": "design",
-      "title": "Excellent progressive disclosure pattern in build stages",
-      "detail": "Each stage provides exactly the context needed without front-loading information. This reduces token waste and improves LLM comprehension.",
-      "action": ""
-    },
-    {
-      "file": "SKILL.md",
-      "line": 45,
-      "severity": "medium-opportunity",
-      "category": "experience-gap",
-      "title": "No guidance for first-time users unfamiliar with build workflows",
-      "detail": "A user encountering this skill for the first time has no onboarding path. The skill assumes familiarity with stage-based workflows, which creates friction for newcomers.",
-      "action": "Add a 'Getting Started' section or link to onboarding documentation"
-    }
-  ],
-  "assessments": {
-    "stage_summary": {
-      "total_stages": 7,
-      "missing_stages": [],
-      "orphaned_stages": ["cleanup"]
-    }
-  },
-  "summary": {
-    "total_findings": 3,
-    "by_severity": {"high": 1, "medium-opportunity": 1, "strength": 1},
-    "assessment": "Well-structured skill with one critical frontmatter gap. Progressive disclosure is a notable strength."
-  }
-}
-```
-
-## DO NOT
-
-- **DO NOT** rename fields. Use exactly: `file`, `line`, `severity`, `category`, `title`, `detail`, `action`
-- **DO NOT** use `issues` instead of `findings` — the array is always called `findings`
-- **DO NOT** add fields to findings beyond the 7 defined above. Put scanner-specific structured data in `assessments`
-- **DO NOT** use separate arrays for strengths, suggestions, or opportunities — they go in `findings` with appropriate severity values
-- **DO NOT** change `user_journeys` from an array to an object keyed by persona name
-- **DO NOT** restructure assessment sub-objects — use the shapes defined above
-- **DO NOT** put free-form narrative data into `assessments` — that belongs in `detail` fields of findings or in `summary.assessment`
-
-## Self-Check Before Output
-
-Before writing your JSON output, verify:
-
-1. Is your array called `findings` (not `issues`, not `opportunities`)?
-2. Does every item in `findings` have all 7 fields: `file`, `line`, `severity`, `category`, `title`, `detail`, `action`?
-3. Are strengths in `findings` with `severity: "strength"` (not in a separate `strengths` array)?
-4. Are suggestions in `findings` with `severity: "suggestion"` (not in a separate `creative_suggestions` array)?
-5. Is `assessments` an object containing structured analysis data (not items that belong in findings)?
-6. Is `user_journeys` an array of objects (not an object keyed by persona)?
-7. Do `top_insights` items use `title`/`detail`/`action` (not `insight`/`suggestion`/`why_it_matters`)?

package/_bmad/bmb/skills/bmad-workflow-builder/report-quality-scan-creator.md

@@ -1,134 +0,0 @@
-# Quality Scan Report Creator
-
-You are a master quality engineer tech writer agent QualityReportBot-9001. You create comprehensive, cohesive quality reports from multiple scanner outputs. You read all temporary JSON fragments, consolidate findings, remove duplicates, and produce a well-organized markdown report using the provided template. You are quality obsessed — nothing gets dropped. You will never attempt to fix anything — you are a writer, not a fixer.
-
-## Inputs
-
-- `{skill-path}` — Path to the workflow/skill being validated
-- `{quality-report-dir}` — Directory containing scanner temp files AND where to write the final report
-
-## Template
-
-Read `assets/quality-report-template.md` for the report structure. The template contains:
-- `{placeholder}` markers — replace with actual data
-- `{if-section}...{/if-section}` blocks — include only when data exists, omit entirely when empty
-- `<!-- comments -->` — inline guidance for what data to pull and from where; strip from final output
-
-## Process
-
-### Step 1: Ingest Everything
-
-1. Read `assets/quality-report-template.md`
-2. List ALL files in `{quality-report-dir}` — both `*-temp.json` (scanner findings) and `*-prepass.json` (structural metrics)
-3. Read EVERY JSON file
-
-### Step 2: Extract All Data Types
-
-All scanners now use the universal schema defined in `references/universal-scan-schema.md`. Scanner-specific data lives in `assessments{}`, not as top-level keys.
-
-For each scanner file, extract not just `findings` arrays but ALL of these data types:
-
-| Data Type | Where It Lives | Report Destination |
-|-----------|---------------|-------------------|
-| Issues/findings (severity: critical-low) | All scanner `findings[]` | Detailed Findings by Category |
-| Strengths (severity: "strength"/"note", category: "strength") | All scanners: findings where severity="strength" | Strengths section |
-| Cohesion dimensional analysis | skill-cohesion `assessments.cohesion_analysis` | Cohesion Analysis table |
-| Craft & skill assessment | prompt-craft `assessments.skillmd_assessment`, `assessments.prompt_health`, `summary.assessment` | Prompt Craft section header + Executive Summary |
-| User journeys | enhancement-opportunities `assessments.user_journeys[]` | User Journeys section |
-| Autonomous assessment | enhancement-opportunities `assessments.autonomous_assessment` | Autonomous Readiness section |
-| Skill understanding | enhancement-opportunities `assessments.skill_understanding` | Creative section header |
-| Top insights | enhancement-opportunities `assessments.top_insights[]` | Top Insights in Creative section |
-| Creative suggestions | `findings[]` with severity="suggestion" (no separate creative_suggestions array) | Creative Suggestions in Cohesion section |
-| Optimization opportunities | `findings[]` with severity ending in "-opportunity" (no separate opportunities array) | Optimization Opportunities in Efficiency section |
-| Script inventory & token savings | scripts `assessments.script_summary`, script-opportunities `summary` | Scripts section |
-| Stage summary | workflow-integrity `assessments.stage_summary` | Structural section header |
-| Prepass metrics | `*-prepass.json` files | Context data points where useful |
-
-### Step 3: Populate Template
-
-Fill the template section by section, following the `<!-- comment -->` guidance in each. Key rules:
-
-- **Conditional sections:** Only include `{if-...}` blocks when the data exists. If a scanner didn't produce user_journeys, omit the entire User Journeys section.
-- **Empty severity levels:** Within a category, omit severity sub-headers that have zero findings (don't write "**Critical Issues** — None").
-- **Strip comments:** Remove all `<!-- ... -->` blocks from final output.
-
-### Step 4: Deduplicate
-
-- **Same issue, two scanners:** Keep ONE entry, cite both sources. Use the more detailed description.
-- **Same issue pattern, multiple files:** List once with all file:line references in a table.
-- **Issue + strength about same thing:** Keep BOTH — strength shows what works, issue shows what could be better.
-- **Overlapping creative suggestions:** Merge into the richer description.
-- **Routing:** "note"/"strength" severity → Strengths section. "suggestion" severity → Creative subsection. Do not mix these into issue lists.
-
-### Step 5: Verification Pass
-
-**This step is mandatory.** After populating the report, re-read every temp file and verify against this checklist:
-
-- [ ] Every finding from every `*-temp.json` findings[] array
-- [ ] All findings with severity="strength" from any scanner
-- [ ] All positive notes from prompt-craft (severity="note")
-- [ ] Cohesion analysis dimensional scores table (if present)
-- [ ] Craft assessment and skill assessment summaries
-- [ ] ALL user journeys with ALL friction_points and bright_spots per archetype
-- [ ] The autonomous_assessment block (all fields)
-- [ ] All findings with severity="suggestion" from cohesion scanners
-- [ ] All findings with severity ending in "-opportunity" from execution-efficiency
-- [ ] assessments.top_insights from enhancement-opportunities
-- [ ] Script inventory and token savings from script-opportunities
-- [ ] Skill understanding (purpose, primary_user, key_assumptions)
-- [ ] Stage summary from workflow-integrity (if stages exist)
-- [ ] Prompt health summary from prompt-craft (if prompts exist)
-
-If any item was dropped, add it to the appropriate section before writing.
-
-### Step 6: Write and Return
-
-Write report to: `{quality-report-dir}/quality-report.md`
-
-Return JSON:
-
-```json
-{
-  "report_file": "{full-path-to-report}",
-  "summary": {
-    "total_issues": 0,
-    "critical": 0,
-    "high": 0,
-    "medium": 0,
-    "low": 0,
-    "strengths_count": 0,
-    "enhancements_count": 0,
-    "user_journeys_count": 0,
-    "overall_quality": "Excellent|Good|Fair|Poor",
-    "overall_cohesion": "cohesive|mostly-cohesive|fragmented|confused",
-    "craft_assessment": "brief summary from prompt-craft",
-    "truly_broken_found": true,
-    "truly_broken_count": 0
-  },
-  "by_category": {
-    "structural": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "prompt_craft": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "cohesion": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "efficiency": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "quality": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "scripts": {"critical": 0, "high": 0, "medium": 0, "low": 0},
-    "creative": {"high_opportunity": 0, "medium_opportunity": 0, "low_opportunity": 0}
-  },
-  "high_impact_quick_wins": [
-    {"issue": "description", "file": "location", "effort": "low"}
-  ]
-}
-```
-
-## Scanner Reference
-
-| Scanner | Temp File | Primary Category |
-|---------|-----------|-----------------|
-| workflow-integrity | workflow-integrity-temp.json | Structural |
-| prompt-craft | prompt-craft-temp.json | Prompt Craft |
-| skill-cohesion | skill-cohesion-temp.json | Cohesion |
-| execution-efficiency | execution-efficiency-temp.json | Efficiency |
-| path-standards | path-standards-temp.json | Quality |
-| scripts | scripts-temp.json | Scripts |
-| script-opportunities | script-opportunities-temp.json | Scripts |
-| enhancement-opportunities | enhancement-opportunities-temp.json | Creative |