agileflow 3.3.0 → 3.4.1

package/src/core/commands/seo/competitor.md

@@ -0,0 +1,174 @@
+---
+description: SEO competitor comparison - analyze competing pages, generate feature matrices, and create comparison content with schema markup
+argument-hint: "YOUR_URL COMPETITOR_URL [COMPETITOR_URL_2]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:competitor - Competitor SEO comparison"
+    - "Fetch both your page and competitor page(s)"
+    - "Generate feature comparison matrix"
+    - "Produce comparison page content with Product schema"
+  state_fields:
+    - your_url
+    - competitor_urls
+    - comparison_matrix
+---
+
+# /agileflow:seo:competitor
+
+Analyze competitor pages and generate SEO-optimized comparison content with feature matrices and structured data.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:competitor https://you.com https://competitor.com          # 1v1 comparison
+/agileflow:seo:competitor https://you.com https://comp1.com https://comp2.com  # Multi-competitor
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| YOUR_URL | Any valid URL | Required | Your product/service page |
+| COMPETITOR_URL | Any valid URL(s) | Required | Competitor page(s) to compare (1-3) |
+
+---
+
+## Process
+
+### STEP 1: Fetch All Pages
+
+Use WebFetch to retrieve your page and each competitor page. Extract:
+- Product/service name
+- Features list
+- Pricing (if visible)
+- Key differentiators
+- Schema markup present
+- Meta title/description
+
+### STEP 2: Build Feature Matrix
+
+Create a comparison matrix:
+
+```markdown
+| Feature | Your Product | Competitor A | Competitor B |
+|---------|-------------|-------------|-------------|
+| {feature 1} | Yes/No/Value | Yes/No/Value | Yes/No/Value |
+| {feature 2} | Yes/No/Value | Yes/No/Value | Yes/No/Value |
+| Pricing | {price} | {price} | {price} |
+| Free Trial | Yes/No | Yes/No | Yes/No |
+```
+
+### STEP 3: SEO Comparison
+
+Compare SEO elements:
+
+| Element | You | Competitor |
+|---------|-----|-----------|
+| Title tag | {length, keywords} | {length, keywords} |
+| Meta description | {present, quality} | {present, quality} |
+| H1 | {text} | {text} |
+| Schema types | {types} | {types} |
+| Word count | {count} | {count} |
+| Internal links | {count} | {count} |
+| Image optimization | {score} | {score} |
+
+### STEP 4: Generate Comparison Content
+
+Produce draft comparison page content:
+
+```markdown
+# {Your Product} vs {Competitor}: {Year} Comparison
+
+## Quick Summary
+
+{2-3 sentence overview}
+
+## Feature Comparison
+
+[Feature matrix table]
+
+## {Your Product} Advantages
+
+1. {advantage with evidence}
+2. {advantage}
+
+## When to Choose {Competitor}
+
+{Fair, balanced assessment}
+
+## Pricing Comparison
+
+[Pricing table]
+
+## Verdict
+
+{Balanced recommendation}
+```
+
+### STEP 5: Generate Schema
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "WebPage",
+  "name": "{Your Product} vs {Competitor}",
+  "description": "Compare {Your Product} and {Competitor} features, pricing, and capabilities",
+  "mainEntity": {
+    "@type": "ItemList",
+    "itemListElement": [
+      {
+        "@type": "Product",
+        "name": "{Your Product}",
+        "url": "{your_url}"
+      },
+      {
+        "@type": "Product",
+        "name": "{Competitor}",
+        "url": "{competitor_url}"
+      }
+    ]
+  }
+}
+```
+
+### STEP 6: Output
+
+```markdown
+# Competitor Analysis: {You} vs {Competitor(s)}
+
+## SEO Comparison
+[Side-by-side SEO element comparison]
+
+## Feature Matrix
+[Feature comparison table]
+
+## Content Gaps
+[What competitor has that you're missing]
+
+## Generated Comparison Page
+[Draft content ready to publish]
+
+## Schema Markup
+[JSON-LD for the comparison page]
+
+## SEO Recommendations
+1. {Priority improvement}
+2. {Next priority}
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:competitor` - Competitor SEO comparison
+
+**Output**: Feature matrix, SEO comparison, draft comparison page content, schema markup
+
+**Usage**: `/agileflow:seo:competitor YOUR_URL COMPETITOR_URL [COMPETITOR_URL_2]`
+<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/seo/content.md

@@ -0,0 +1,107 @@
+---
+description: E-E-A-T content quality analysis - trustworthiness, expertise, authoritativeness, experience scoring with AI content detection
+argument-hint: "URL [TYPE=homepage|service|blog|product|location]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:content - E-E-A-T content quality analysis"
+    - "Deploy seo-analyzer-content for comprehensive E-E-A-T assessment"
+    - "Score: Trust 30%, Expertise 25%, Authoritativeness 25%, Experience 20%"
+    - "Check content minimums by page type (from quality-gates.md)"
+  state_fields:
+    - target_url
+    - page_type
+    - eeat_score
+---
+
+# /agileflow:seo:content
+
+Analyze content quality using the E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness). Includes AI content detection and citation readiness assessment.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:content https://example.com                    # Homepage content analysis
+/agileflow:seo:content https://example.com/blog/post TYPE=blog # Blog post analysis
+/agileflow:seo:content https://example.com/services TYPE=service # Service page analysis
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL | Required | Page to analyze |
+| TYPE | homepage, service, blog, product, location | Auto-detect | Page type (affects content minimums) |
+
+---
+
+## Process
+
+### STEP 1: Deploy Content Analyzer
+
+```xml
+<invoke name="Task">
+<parameter name="description">E-E-A-T content quality analysis</parameter>
+<parameter name="prompt">TASK: Perform deep E-E-A-T content quality analysis.
+
+TARGET URL: {url}
+PAGE TYPE: {type or "auto-detect"}
+
+Score each E-E-A-T factor:
+- Trustworthiness (30%): HTTPS, contact, privacy, transparency, no deception
+- Expertise (25%): Author credentials, citations, accuracy, depth
+- Authoritativeness (25%): Brand signals, testimonials, certifications, NAP
+- Experience (20%): First-hand accounts, original media, specific data, case studies
+
+Also assess:
+- Content depth vs minimums (homepage 500w, service 800w, blog 1500w, product 300w)
+- Content uniqueness (boilerplate vs original)
+- Readability level
+- AI content red flags (generic phrasing, no insights, fabricated experience)
+- AI citation readiness (self-contained blocks, specific facts, question headers)
+
+OUTPUT: Content Quality Score X/100 with E-E-A-T breakdown.</parameter>
+<parameter name="subagent_type">seo-analyzer-content</parameter>
+</invoke>
+```
+
+### STEP 2: Present Results
+
+Show E-E-A-T breakdown with signal-level detail and remediation steps.
+
+---
+
+## E-E-A-T Scoring
+
+| Factor | Weight | Key Signals |
+|--------|--------|-------------|
+| Trustworthiness | 30% | HTTPS, contact info, privacy policy, editorial transparency |
+| Expertise | 25% | Author bylines, cited sources, technical depth |
+| Authoritativeness | 25% | Brand identity, certifications, media mentions |
+| Experience | 20% | First-person accounts, original photos, specific data |
+
+## Content Minimums (from quality-gates.md)
+
+| Page Type | Min Words | Unique % |
+|-----------|-----------|----------|
+| Homepage | 500 | 100% |
+| Service | 800 | 60% |
+| Blog | 1,500 | 100% |
+| Product | 300 | 40% |
+| Location | 500 | 40% |
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:content` - E-E-A-T content quality analysis
+
+**Scoring**: Trust 30%, Expertise 25%, Authority 25%, Experience 20%
+
+**Usage**: `/agileflow:seo:content URL [TYPE=page_type]`
+<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/seo/geo.md

@@ -0,0 +1,229 @@
+---
+description: Generative Engine Optimization (GEO) - analyze and optimize content for AI search platforms like ChatGPT, Google AI Overviews, and Perplexity
+argument-hint: "URL"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:geo - AI search optimization"
+    - "Assess 5 GEO dimensions: Citability, Structure, Multimodal, Authority, Technical Access"
+    - "Check robots.txt for AI bot access (GPTBot, ClaudeBot, PerplexityBot)"
+    - "Check for /llms.txt file"
+    - "Optimize for 134-167 word citation blocks"
+  state_fields:
+    - target_url
+    - geo_score
+    - ai_bot_access
+---
+
+# /agileflow:seo:geo
+
+Analyze and optimize content for AI search platforms (Generative Engine Optimization). Ensure your content gets cited by ChatGPT, Google AI Overviews, Perplexity, and Claude.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:geo https://example.com                      # Full GEO analysis
+/agileflow:seo:geo https://example.com/blog/guide            # Analyze specific content page
+```
+
+---
+
+## Background
+
+**GEO (Generative Engine Optimization)** optimizes content for AI-powered search platforms:
+- Google AI Overviews
+- ChatGPT (with Browse/Search)
+- Perplexity
+- Claude
+
+**Key insight**: Brand correlation is 3x stronger than backlinks for AI visibility. 92% of AI citations come from top-10 traditional search results.
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL | Required | Page or site to analyze |
+
+---
+
+## GEO Assessment Framework
+
+### 1. Citability (25%)
+
+AI platforms cite content that contains self-contained, quotable blocks:
+
+| Signal | Good | Poor |
+|--------|------|------|
+| Answer blocks | 134-167 word self-contained paragraphs | Long unbroken paragraphs |
+| Specific facts | Numbers, dates, names, percentages | Vague generalizations |
+| Definitions | Clear "X is Y" statements | Implied definitions |
+| Lists | Numbered/bulleted key points | Points buried in prose |
+| Attribution | "According to [source]..." | Unsourced claims |
+
+**Check**: Count paragraphs in the 134-167 word range. Assess whether they answer specific questions independently.
+
+### 2. Structure (20%)
+
+AI platforms parse structured content more effectively:
+
+| Signal | Good | Poor |
+|--------|------|------|
+| Question headers | H2/H3 as questions (Who, What, How) | Generic headings |
+| Short paragraphs | 2-4 sentences | Wall of text |
+| Tables | Comparison data in tables | Comparisons in prose |
+| Numbered steps | Step-by-step instructions | Instructions in paragraphs |
+| TL;DR / Summary | Key takeaway at top or bottom | No summary |
+
+### 3. Multimodal Content (15%)
+
+Pages with multiple content types get 156% higher AI citation rates:
+
+| Signal | Good | Poor |
+|--------|------|------|
+| Text + Images | Informative images with good alt text | Text only |
+| Text + Video | Embedded video with transcript | No video |
+| Text + Tables | Data visualization | Numbers in paragraphs |
+| Interactive | Calculators, tools, quizzes | Static content only |
+| Infographics | Visual summaries | No visual aids |
+
+### 4. Authority (20%)
+
+AI platforms prioritize authoritative sources:
+
+| Signal | Good | Poor |
+|--------|------|------|
+| Author credentials | Named author with bio/credentials | No attribution |
+| Publication dates | Recent, prominently displayed | No dates or old |
+| Primary sources | Original data, research, case studies | Only secondary sources |
+| Citations | Links to authoritative references | No outbound links |
+| Brand presence | Wikipedia, Reddit, YouTube mentions | No cross-platform presence |
+
+### 5. Technical Access (20%)
+
+AI bots must be able to access your content:
+
+| Signal | Good | Poor |
+|--------|------|------|
+| GPTBot allowed | Not blocked in robots.txt | Blocked |
+| ClaudeBot allowed | Not blocked in robots.txt | Blocked |
+| PerplexityBot allowed | Not blocked in robots.txt | Blocked |
+| Google-Extended allowed | Not blocked | Blocked |
+| `/llms.txt` present | Exists at root | Missing |
+| Server-side rendering | Content in HTML source | JS-only rendering |
+| Fast response | Quick TTFB | Slow or rate-limited |
+
+---
+
+## Process
+
+### STEP 1: Fetch Target Page
+
+Use WebFetch to retrieve the page content.
+
+### STEP 2: Fetch robots.txt
+
+Check `{domain}/robots.txt` for AI bot rules:
+```
+User-agent: GPTBot
+User-agent: ClaudeBot
+User-agent: PerplexityBot
+User-agent: Google-Extended
+```
+
+### STEP 3: Check for llms.txt
+
+Fetch `{domain}/llms.txt` - a machine-readable site description for AI platforms.
+
+### STEP 4: Analyze Each Dimension
+
+Score each of the 5 dimensions out of 100, then apply weights:
+
+| Dimension | Weight |
+|-----------|--------|
+| Citability | 25% |
+| Structure | 20% |
+| Multimodal | 15% |
+| Authority | 20% |
+| Technical Access | 20% |
+
+### STEP 5: Output Report
+
+```markdown
+# GEO Analysis: {URL}
+
+## AI Search Readiness Score: {X}/100
+
+| Dimension | Score | Weight | Weighted | Key Finding |
+|-----------|-------|--------|----------|-------------|
+| Citability | {X}/100 | 25% | {X} | {finding} |
+| Structure | {X}/100 | 20% | {X} | {finding} |
+| Multimodal | {X}/100 | 15% | {X} | {finding} |
+| Authority | {X}/100 | 20% | {X} | {finding} |
+| Technical Access | {X}/100 | 20% | {X} | {finding} |
+
+## AI Bot Access Status
+
+| Bot | Status | robots.txt |
+|-----|--------|-----------|
+| GPTBot (ChatGPT) | Allowed/Blocked | {rule or "No rule"} |
+| ClaudeBot (Claude) | Allowed/Blocked | {rule or "No rule"} |
+| PerplexityBot | Allowed/Blocked | {rule or "No rule"} |
+| Google-Extended (AI Overviews) | Allowed/Blocked | {rule or "No rule"} |
+
+## llms.txt: {Present/Missing}
+
+## Citability Analysis
+
+- Citation-ready blocks found: {N}
+- Average paragraph length: {N} words
+- Self-contained answer blocks: {N}
+
+## Recommendations
+
+### Quick Wins
+1. {highest impact, easiest change}
+2. {next priority}
+
+### Content Improvements
+1. {content change for better citability}
+2. {structural improvement}
+
+### Technical Changes
+1. {robots.txt or llms.txt change}
+```
+
+### STEP 6: Offer Next Steps
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "GEO analysis: AI Search Readiness {X}/100. {bot_status}. {N} citation-ready blocks found.",
+  "header": "Next steps",
+  "multiSelect": false,
+  "options": [
+    {"label": "Improve citability (Recommended)", "description": "Restructure content into 134-167 word answer blocks"},
+    {"label": "Fix AI bot access", "description": "Update robots.txt to allow GPTBot, ClaudeBot, PerplexityBot"},
+    {"label": "Create llms.txt", "description": "Generate machine-readable site description"},
+    {"label": "Run full SEO audit", "description": "/agileflow:seo:audit {domain}"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:geo` - AI search optimization (Generative Engine Optimization)
+
+**5 Dimensions**: Citability 25%, Structure 20%, Multimodal 15%, Authority 20%, Technical Access 20%
+
+**Key Checks**: AI bot access in robots.txt, llms.txt presence, 134-167 word citation blocks
+
+**Target Platforms**: Google AI Overviews, ChatGPT, Perplexity, Claude
+<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/seo/hreflang.md

@@ -0,0 +1,140 @@
+---
+description: Multi-language SEO validation - hreflang tag correctness, reciprocity checks, language code validation, and international targeting
+argument-hint: "URL"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:hreflang - Multi-language SEO"
+    - "Check hreflang tags, reciprocity, language codes, x-default"
+    - "Verify all language versions reference each other"
+  state_fields:
+    - target_url
+    - languages_found
+    - reciprocity_issues
+---
+
+# /agileflow:seo:hreflang
+
+Validate multi-language SEO implementation: hreflang tags, reciprocity, language codes, x-default, and international targeting.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:hreflang https://example.com                  # Check hreflang implementation
+/agileflow:seo:hreflang https://example.com/es/              # Check from Spanish version
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL | Required | Page to check hreflang |
+
+---
+
+## What Gets Checked
+
+### 1. Hreflang Tag Detection
+
+Look for hreflang in three possible locations:
+- HTML `<head>`: `<link rel="alternate" hreflang="es" href="...">`
+- HTTP headers: `Link: <...>; rel="alternate"; hreflang="es"`
+- XML sitemap: `<xhtml:link rel="alternate" hreflang="es" href="..."/>`
+
+### 2. Validation Rules
+
+| Rule | Check | Common Error |
+|------|-------|-------------|
+| **Valid language codes** | ISO 639-1 (2-letter) | "eng" instead of "en" |
+| **Valid region codes** | ISO 3166-1 (2-letter) | "uk" instead of "gb" |
+| **x-default present** | Fallback for unmatched | Missing x-default |
+| **Self-referencing** | Page includes itself | Missing self-reference |
+| **Reciprocity** | A→B means B→A | One-way hreflang |
+| **Consistent URLs** | Match canonical | hreflang to non-canonical |
+| **Absolute URLs** | Full https:// URLs | Relative paths |
+| **Return 200** | All hreflang URLs live | 404 or redirect targets |
+
+### 3. Reciprocity Check
+
+For each language version:
+1. Fetch the page
+2. Check that it links back to all other versions
+3. Flag any broken reciprocity chains
+
+```
+Page A (en) → B (es), C (fr)
+Page B (es) → A (en), C (fr)  ← Must reference A and C
+Page C (fr) → A (en), B (es)  ← Must reference A and B
+```
+
+### 4. Common Issues
+
+| Issue | Severity | Fix |
+|-------|----------|-----|
+| Missing x-default | HIGH | Add x-default pointing to canonical version |
+| Broken reciprocity | HIGH | Ensure all versions reference each other |
+| Invalid language code | MEDIUM | Use ISO 639-1 codes |
+| hreflang to redirect | MEDIUM | Point to final destination URL |
+| hreflang to noindex | HIGH | Don't noindex alternate versions |
+| Mixed implementation | LOW | Use one method consistently |
+
+---
+
+## Process
+
+### STEP 1: Fetch the Target Page
+
+Use WebFetch to retrieve the page. Extract hreflang tags from HTML head.
+
+### STEP 2: Map All Language Versions
+
+Build a matrix of all language versions and their hreflang references.
+
+### STEP 3: Verify Reciprocity
+
+Fetch each alternate version and verify it references back to all other versions.
+
+### STEP 4: Output Report
+
+```markdown
+# Hreflang Analysis: {URL}
+
+## Language Versions Found
+
+| Language | Region | URL | Status |
+|----------|--------|-----|--------|
+| en | - | https://example.com/ | 200 |
+| es | - | https://example.com/es/ | 200 |
+| fr | FR | https://example.com/fr/ | 200 |
+| x-default | - | https://example.com/ | 200 |
+
+## Reciprocity Matrix
+
+| Page | → en | → es | → fr | → x-default |
+|------|------|------|------|-------------|
+| /en/ | self | yes | yes | yes |
+| /es/ | yes | self | NO | yes |
+| /fr/ | yes | yes | self | yes |
+
+## Issues Found
+
+[Detailed findings]
+
+## Hreflang Score: X/100
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:hreflang` - Multi-language SEO validation
+
+**Checks**: hreflang tags, reciprocity, language codes, x-default, canonical consistency
+
+**Usage**: `/agileflow:seo:hreflang URL`
+<!-- COMPACT_SUMMARY_END -->