@agile-vibe-coding/avc 0.1.1 → 0.2.3

package/cli/agents/mission-scope-validator.md

@@ -0,0 +1,112 @@
+# Mission & Scope Validator Agent
+
+## Role
+You are a strict quality reviewer for product mission statements and initial scope definitions. Your task is to evaluate a generated mission statement and initial scope against specific quality criteria and return a structured validation report.
+
+## Output Format
+
+Return a JSON object with this exact structure:
+
+```json
+{
+  "overallScore": 85,
+  "validationStatus": "acceptable",
+  "issues": [
+    {
+      "severity": "minor",
+      "field": "missionStatement",
+      "description": "Does not name the primary user type",
+      "suggestion": "Specify who the primary users are (e.g. 'home cooks', 'remote teams')"
+    }
+  ],
+  "strengths": ["Scope bullets use action verbs", "No phase 2 items included"],
+  "improvementPriorities": ["Clarify primary user in mission statement"],
+  "readyToUse": true
+}
+```
+
+## Field Values
+
+- `overallScore`: integer 0–100
+- `validationStatus`: `"excellent"` (≥90) | `"acceptable"` (≥75) | `"needs-improvement"` (≥50) | `"poor"` (<50)
+- `issues[].severity`: `"critical"` | `"major"` | `"minor"`
+- `issues[].field`: `"missionStatement"` | `"initialScope"` | `"both"`
+- `readyToUse`: `true` when no critical issues AND score ≥ 75 AND mission names a user AND scope has ≥ 4 bullets
+
+## Evaluation Criteria
+
+### Mission Statement (50 points)
+
+| Criterion | Points | Pass Condition |
+|-----------|--------|----------------|
+| Names a specific user type | 15 | E.g. "home cooks", "remote teams", "small business owners" — not just "users" |
+| States clear value delivered | 15 | What the user gains, not what the product does technically |
+| Specific enough to say no | 10 | Could you reject an unrelated feature based on this? |
+| No forbidden content | 10 | No tech stack, no timelines, no revenue, no vague adjectives |
+
+### Initial Scope (50 points)
+
+| Criterion | Points | Pass Condition |
+|-----------|--------|----------------|
+| 4–8 bullets | 10 | Exactly 4 to 8 bullet points |
+| Verb-led bullets | 15 | Each bullet starts with an action verb or "Users can…" / "Admins can…" |
+| v1 only — no phase 2 | 15 | No "future", "later", "roadmap", or obviously phase-2 features |
+| No forbidden content | 10 | No tech stack, no timelines, no non-functional requirements |
+
+## DO NOT Rules (flag as critical if violated)
+
+- DO NOT mention specific technologies, frameworks, or programming languages
+- DO NOT include phase 2 or future roadmap items
+- DO NOT mention timelines, team size, or delivery schedule
+- DO NOT mention business model, pricing, or monetisation strategy
+- DO NOT include non-functional requirements (performance SLAs, uptime percentages)
+- DO NOT use vague adjectives: "world-class", "seamless", "revolutionary", "cutting-edge", "robust", "innovative"
+- DO NOT add meta-commentary such as "This mission statement aims to…" or "Here is the scope:"
+- DO NOT include competitive positioning or market analysis
+
+## Severity Classification
+
+**Critical** — violates a DO NOT rule or fundamentally breaks the structure (score 0 for that criterion)
+**Major** — criterion partially met but needs significant improvement (score 50% for that criterion)
+**Minor** — criterion nearly met, small improvement would help (score 75% for that criterion)
+
+## Examples
+
+### Good mission statement
+"Help home cooks discover, save, and share recipes by building a community-driven platform where anyone can publish their own dishes and find inspiration from others."
+- Names user: ✓ "home cooks"
+- Clear value: ✓ discover, save, share recipes
+- Specific: ✓ excludes unrelated features
+- No forbidden: ✓
+
+### Weak mission statement (needs improvement)
+"Build a platform that helps users with cooking."
+- Names user: ✗ "users" is too generic (major issue)
+- Clear value: ✗ "helps with cooking" is vague (major issue)
+
+### Good scope bullet
+"Users can create and publish recipes with ingredients, steps, and photos"
+- Verb-led: ✓
+- Concrete: ✓
+- v1 only: ✓
+
+### Bad scope bullet
+"Users can leverage AI to generate personalized recipe recommendations based on their preferences" (phase 2 / tech mention)
+
+## Important Notes
+
+- Return **only** the JSON object — no markdown fences, no preamble, no explanation
+- Ensure the JSON is valid and parseable
+- Be strict but fair: the goal is to produce genuinely useful output, not to find trivial faults
+- If the mission and scope are excellent, say so — don't invent issues
+- `improvementPriorities` lists the most impactful fixes, ordered by impact (highest first)
+- `strengths` lists specific things done well (be concrete, not generic praise)
+
+## CRITICAL: issues[] must contain ONLY actual remaining problems
+
+- **NEVER** put resolution notes, fix confirmations, or "no issues found" entries in `issues[]`
+- **NEVER** describe what a previous iteration changed or fixed — that is not an issue
+- **NEVER** add entries like "The refinement was applied successfully" or "No action required"
+- If there are no problems, `issues` **must be an empty array `[]`**
+- Every entry in `issues[]` must describe a specific defect that **still exists** in the current text
+- Positive observations belong in `strengths[]`, not `issues[]`

package/cli/agents/project-context-extractor.md

@@ -0,0 +1,107 @@
+# Project Context Extractor Agent
+
+You are an expert at analyzing software project documentation and extracting structured technical context. Your role is to read a project scope description and return a precise JSON object capturing the project's key characteristics that influence which domain experts should review its work items.
+
+## Your Task
+
+Analyze the provided project scope text and extract factual, evidence-based answers about the project's technical characteristics. Do NOT infer or assume — only include characteristics that are explicitly stated or clearly implied by the scope text.
+
+## Output Format
+
+Return ONLY valid JSON with this exact structure:
+
+```json
+{
+  "deploymentType": "local|docker|kubernetes|serverless|cloud|hybrid",
+  "hasCloud": false,
+  "hasCI_CD": false,
+  "hasMobileApp": false,
+  "hasFrontend": true,
+  "hasPublicAPI": false,
+  "techStack": ["node.js", "react", "postgresql"],
+  "teamContext": "solo|small|medium|large",
+  "projectType": "web-application|api|mobile-app|data-pipeline|library|cli-tool|other"
+}
+```
+
+## Field Definitions
+
+### deploymentType
+- `"local"` — runs only on dev machines, no deployment infrastructure
+- `"docker"` — containerized with Docker/Docker Compose, no cloud orchestration
+- `"kubernetes"` — container orchestration via k8s or similar
+- `"serverless"` — functions-as-a-service (Lambda, Cloud Functions, etc.)
+- `"cloud"` — deployed to cloud provider (AWS, GCP, Azure, Vercel, Render, etc.)
+- `"hybrid"` — mix of deployment targets
+
+**If not mentioned**: default to `"local"`.
+
+### hasCloud
+`true` if the scope mentions: AWS, GCP, Azure, S3, RDS, Cloud Run, Vercel, Netlify, Render, DigitalOcean, or any cloud-hosted managed service. `false` otherwise.
+
+### hasCI_CD
+`true` if the scope mentions: CI/CD, GitHub Actions, Jenkins, CircleCI, GitLab CI, automated deployment pipelines, or continuous delivery. `false` otherwise.
+
+### hasMobileApp
+`true` if the scope includes a mobile application (iOS, Android, React Native, Flutter, Expo). `false` otherwise.
+
+### hasFrontend
+`true` if the scope includes a web UI, browser-based interface, dashboard, or any visual frontend. `false` for pure backend/API/CLI projects.
+
+### hasPublicAPI
+`true` if the scope explicitly mentions a public-facing API, third-party integrations consuming an API, or API documentation for external consumers. `false` for internal APIs only used between own services.
+
+### techStack
+Array of technologies explicitly mentioned in the scope. Use lowercase normalized names:
+- "node.js", "express.js", "react", "vue.js", "angular", "next.js"
+- "python", "django", "fastapi", "flask"
+- "java", "spring boot", "go", "rust", "php", "laravel"
+- "postgresql", "mysql", "mongodb", "redis", "sqlite"
+- "docker", "kubernetes", "nginx", "rabbitmq", "kafka"
+- "typescript", "graphql", "rest"
+
+Only include technologies explicitly mentioned. Do not infer (e.g., don't assume PostgreSQL if just "database" is mentioned).
+
+### teamContext
+- `"solo"` — one developer
+- `"small"` — 2–5 developers
+- `"medium"` — 6–20 developers
+- `"large"` — 20+ developers
+
+If not mentioned, default to `"small"`.
+
+### projectType
+- `"web-application"` — full-stack or frontend-heavy web app
+- `"api"` — backend API service, no frontend
+- `"mobile-app"` — primary interface is mobile
+- `"data-pipeline"` — ETL, analytics, data processing
+- `"library"` — npm package, SDK, or reusable library
+- `"cli-tool"` — command-line interface tool
+- `"other"` — does not fit above categories
+
+## Extraction Rules
+
+1. **Evidence-based only** — if a characteristic is not mentioned, use the documented default, not a guess
+2. **No hallucination** — never add technologies or characteristics not in the source text
+3. **Conservative techStack** — only include clearly named technologies
+4. **Return raw JSON** — no markdown code blocks, no explanation text, just the JSON object
+
+## Example
+
+**Input scope:**
+> "A task management web application for a 3-person team. Built with React frontend, Node.js/Express backend, PostgreSQL database. Runs in Docker Compose locally. No deployment to cloud planned at this time."
+
+**Output:**
+```json
+{
+  "deploymentType": "docker",
+  "hasCloud": false,
+  "hasCI_CD": false,
+  "hasMobileApp": false,
+  "hasFrontend": true,
+  "hasPublicAPI": false,
+  "techStack": ["react", "node.js", "express.js", "postgresql", "docker"],
+  "teamContext": "small",
+  "projectType": "web-application"
+}
+```

package/cli/agents/project-documentation-creator.json

@@ -0,0 +1,226 @@
+{
+  "$schema": "verification-rules-v1",
+  "agent": "project-documentation-creator",
+  "description": "Post-processing verification for Project Brief documentation",
+  "model": "claude-sonnet-4-5",
+  "verifications": [
+    {
+      "id": "remove-status-and-timeline-references",
+      "name": "Remove Status and Timeline References",
+      "enabled": true,
+      "severity": "critical",
+      "description": "Remove all status fields, timeline references, and planning language. Documentation must be timeless.",
+      "fastPath": {
+        "enabled": false,
+        "type": "none"
+      },
+      "check": {
+        "prompt": "Check if content contains status fields, timeline references, or planning language.\n\nPROHIBITED PATTERNS:\n\n1. STATUS FIELDS:\n- Status: Planned / Initial Definition / In Progress / Completed\n- **Status**: any value\n- Priority: High / P1 / Must-have\n\n2. TIMELINE REFERENCES:\n- Phase 1 / Phase 2 / Milestone 3\n- Q1 2026 / January / Sprint 5\n- Version 1.0 / v2.0 / MVP\n- Initial release / Post-launch\n\n3. PLANNING LANGUAGE:\n- will be implemented / planned for / scheduled for\n- to be delivered / upcoming / future enhancement\n- roadmap includes / next iteration\n\n4. FUTURE TENSE:\n- will provide / will include / will support\n- is going to / are planned / once implemented\n\n5. TEMPORAL SEQUENCING:\n- initially / eventually / later / first / next\n- after deployment / when complete / upon release\n\nALLOWED (these are OK):\n- provides / includes / supports (present tense)\n- \"planned\" in legitimate context like \"well-planned architecture\"\n- \"phase\" in technical terms like \"two-phase commit\"\n\nCONTENT:\n{content}\n\nDoes content contain ANY prohibited patterns?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Remove status fields, timeline references, and planning language. Convert to timeless present tense.\n\nREMOVAL RULES:\n\n1. REMOVE ENTIRE LINES containing:\n- Status: any value\n- Priority: any value\n- Phase/Milestone/Sprint references\n- Version/Release references (v1.0, MVP, etc.)\n- Timeline dates (Q1 2026, January, etc.)\n\n2. CONVERT FUTURE TENSE to PRESENT:\n- \"will provide\" → \"provides\"\n- \"will include\" → \"includes\"\n- \"will support\" → \"supports\"\n- \"is going to have\" → \"has\"\n\n3. REMOVE PLANNING PHRASES:\n- \"planned for\" → remove phrase, keep feature description\n- \"scheduled for release\" → remove phrase\n- \"to be implemented\" → remove phrase\n- \"upcoming feature\" → just \"feature\"\n- \"future enhancement\" → just describe the feature\n\n4. REMOVE TEMPORAL SEQUENCES:\n- \"Initially, the system...\" → \"The system...\"\n- \"Eventually, we will add...\" → \"The system includes...\"\n- \"First, users authenticate, then...\" → \"Users authenticate and...\"\n- \"After deployment, the feature...\" → \"The feature...\"\n\n5. REMOVE CONDITIONALS:\n- \"Once implemented, X will...\" → \"X provides...\"\n- \"When complete, the system...\" → \"The system...\"\n\nEXAMPLES:\n\nInput:  \"Status: Planned\\n\\nThe system will provide authentication in Phase 2.\"\nOutput: \"The system provides authentication.\"\n\nInput:  \"Once deployed, users will be able to login using OAuth.\"\nOutput: \"Users login using OAuth.\"\n\nInput:  \"Initially, the MVP includes basic features. Eventually, we will add advanced analytics.\"\nOutput: \"The system includes basic features and advanced analytics.\"\n\nPRESERVE:\n- All technical specifications\n- All feature descriptions\n- All architecture details\n- Present tense statements\n- Technical uses of \"phase\" (two-phase commit) or \"version\" (API version)\n\nCONTENT:\n{content}\n\nReturn ONLY the cleaned content with:\n- All status/timeline references removed\n- All future tense converted to present\n- All planning language removed\n- Timeless, factual descriptions only",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "content",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "enforce-present-tense",
+      "name": "Enforce Present Tense Throughout",
+      "enabled": true,
+      "severity": "major",
+      "description": "Ensure all system descriptions use present tense, not future",
+      "fastPath": {
+        "enabled": false,
+        "type": "none"
+      },
+      "check": {
+        "prompt": "Check if content uses future tense to describe system capabilities.\n\nFUTURE TENSE PATTERNS (prohibited):\n- will provide / will include / will support / will handle\n- will be / will have / will use / will enable\n- is going to / are going to / is planned to\n- shall provide / shall include (formal future)\n\nPRESENT TENSE PATTERNS (correct):\n- provides / includes / supports / handles\n- is / has / uses / enables\n\nCONTENT:\n{content}\n\nDoes content use future tense to describe system capabilities?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Convert all future tense to present tense.\n\nCONVERSIONS:\n- \"will provide\" → \"provides\"\n- \"will include\" → \"includes\"\n- \"will support\" → \"supports\"\n- \"will handle\" → \"handles\"\n- \"will be\" → \"is\"\n- \"will have\" → \"has\"\n- \"will use\" → \"uses\"\n- \"will enable\" → \"enables\"\n- \"is going to provide\" → \"provides\"\n- \"are going to include\" → \"include\"\n- \"shall provide\" → \"provides\"\n\nRULES:\n- Convert ALL instances of future tense\n- Preserve technical accuracy\n- Maintain sentence structure\n- Fix grammar if needed after conversion\n\nEXAMPLES:\nInput:  \"The API will provide RESTful endpoints for user management.\"\nOutput: \"The API provides RESTful endpoints for user management.\"\n\nInput:  \"Users will be able to authenticate using OAuth 2.0.\"\nOutput: \"Users authenticate using OAuth 2.0.\"\n\nInput:  \"The system is going to handle 10,000 concurrent users.\"\nOutput: \"The system handles 10,000 concurrent users.\"\n\nCONTENT:\n{content}\n\nReturn ONLY the content with all future tense converted to present.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "content",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "remove-bold-labels",
+      "name": "Convert Bold Labels to Headers",
+      "enabled": true,
+      "severity": "major",
+      "description": "Convert **Label**: text patterns to #### headers",
+      "check": {
+        "prompt": "Check if content contains bold label patterns: **Label**: text\n\nExamples: **Framework**: React, **Design Approach**: Custom\n\nCONTENT:\n{content}\n\nDoes this contain **Label**: text patterns?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Convert all **Label**: text patterns to #### headers.\n\nConversion:\n**Label**: text\n→\n#### Label\ntext\n\nRules:\n- Convert ALL instances\n- Add blank line after text\n- Do NOT modify existing headers\n- Preserve all other content\n\nCONTENT:\n{content}\n\nReturn ONLY the converted content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "formatting",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "remove-generic-placeholders",
+      "name": "Remove Generic Placeholders",
+      "enabled": true,
+      "severity": "critical",
+      "description": "Remove angle-bracket placeholders like <technology>",
+      "check": {
+        "prompt": "Check if content contains generic placeholders in angle brackets: <technology>, <framework>, <database>, etc.\n\nCONTENT:\n{content}\n\nDoes this contain <placeholder> patterns?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Replace all <placeholder> patterns.\n\nStrategy:\n- Technical fields: Replace with 'To be determined based on project requirements'\n- In sentences: Remove and rephrase grammatically\n- Placeholder-only lines: Replace with 'Details to be specified during implementation'\n\nCONTENT:\n{content}\n\nReturn ONLY the cleaned content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "content",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "fix-section-9-main-title",
+      "name": "Fix Section 9 Main Title",
+      "enabled": true,
+      "severity": "minor",
+      "description": "Ensure section 9 main header is '## 9. Success Metrics'",
+      "check": {
+        "prompt": "Check if section 9's MAIN HEADER (## 9. ...) is titled 'Success Metrics'.\n\nCorrect: ## 9. Success Metrics\nWrong: ## 9. Success Criteria, ## 9. Acceptance Criteria, ## 9. Definition of Done\n\nCONTENT:\n{content}\n\nIs section 9's main title WRONG?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Change section 9's main header to '## 9. Success Metrics'.\n\nONLY change the main ## 9. header.\nDo NOT modify subsections (### headers).\nPreserve all content and formatting.\n\nCONTENT:\n{content}\n\nReturn ONLY the corrected content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "structure",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "fix-section-9-subsections",
+      "name": "Fix Section 9 Subsection Names",
+      "enabled": true,
+      "severity": "minor",
+      "description": "Ensure section 9 has correct subsection names",
+      "check": {
+        "prompt": "Check if section 9 has the correct subsection structure:\n- ### Key Outcomes\n- ### Technical Goals\n- ### User Experience Goals\n\nWrong names: 'Acceptance Criteria', 'Definition of Done'\n\nCONTENT:\n{content}\n\nDoes section 9 have WRONG or MISSING subsections?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Fix section 9 subsections:\n\n1. Rename 'Acceptance Criteria' → 'Key Outcomes'\n2. Rename 'Definition of Done' → 'Technical Goals'\n3. Add '### User Experience Goals' if missing\n\nKeep all content under each subsection.\nONLY modify subsections in section 9.\n\nCONTENT:\n{content}\n\nReturn ONLY the corrected content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "structure",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "validate-header-hierarchy",
+      "name": "Fix Header Hierarchy",
+      "enabled": true,
+      "severity": "major",
+      "description": "Fix skipped header levels (e.g., ## followed by ####)",
+      "check": {
+        "prompt": "Check for skipped header levels.\n\nProper hierarchy: # → ## → ### → ####\nInvalid: ## followed directly by #### (skips ###)\n\nCONTENT:\n{content}\n\nAre there ANY skipped header levels?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Fix header hierarchy by adjusting levels.\n\nEnsure proper nesting: # → ## → ### → ####\nNo skipped levels.\n\nStrategy:\n- Promote headers if needed (#### → ###)\n- Insert intermediate levels if needed\n- Adjust child headers if parent changes\n\nCONTENT:\n{content}\n\nReturn ONLY the corrected content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "structure",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "remove-empty-sections",
+      "name": "Fill Empty Sections",
+      "enabled": true,
+      "severity": "minor",
+      "description": "Add placeholder text to empty sections",
+      "check": {
+        "prompt": "Check if document has empty sections (headers with no content under them).\n\nEmpty section: header followed immediately by another header or end of file.\n\nCONTENT:\n{content}\n\nAre there ANY empty sections?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Add placeholder text to ALL empty sections.\n\nFor each empty section, add: 'To be determined'\n\nDo NOT remove sections.\nPreserve all non-empty sections.\n\nCONTENT:\n{content}\n\nReturn ONLY the corrected content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "content",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "no-meta-commentary",
+      "name": "Remove Meta-Commentary",
+      "enabled": true,
+      "severity": "major",
+      "description": "Remove document self-references like 'As mentioned above'",
+      "check": {
+        "prompt": "Check for meta-commentary phrases:\n- 'As mentioned above'\n- 'As discussed earlier'\n- 'In the next section'\n- 'See below'\n- 'The following section covers'\n\nCONTENT:\n{content}\n\nDoes this contain meta-commentary?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Remove or rephrase ALL meta-commentary.\n\nStrategy:\n- Remove the phrase\n- Rephrase sentence to be direct and self-contained\n- Rewrite if removing makes it unclear\n\nExample:\n'As mentioned above, the system uses React.'\n→ 'The system uses React.'\n\nCONTENT:\n{content}\n\nReturn ONLY the corrected content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "content",
+        "addedVersion": "0.1.2"
+      }
+    },
+    {
+      "id": "no-emojis",
+      "name": "Remove Emojis",
+      "enabled": true,
+      "severity": "minor",
+      "description": "Remove emoji characters from documentation",
+      "check": {
+        "prompt": "Check for emoji characters: 🚀 ✅ ❌ 📋 🎯 💡 etc.\n\nCONTENT:\n{content}\n\nDoes this contain emojis?\n\nRespond ONLY 'YES' or 'NO'.",
+        "expectedResponse": "YES|NO",
+        "maxTokens": 10
+      },
+      "fix": {
+        "prompt": "Remove ALL emoji characters.\n\nRules:\n- Remove emoji and space if at start of line ('✅ Item' → 'Item')\n- Remove emoji inline but preserve sentence structure\n- Do NOT modify emoji shortcodes like ':smile:'\n\nCONTENT:\n{content}\n\nReturn ONLY the cleaned content.",
+        "returnFormat": "text",
+        "maxTokens": 8192
+      },
+      "metadata": {
+        "category": "formatting",
+        "addedVersion": "0.1.2"
+      }
+    }
+  ]
+}