myaidev-method 0.3.2 → 0.3.3

package/src/statusline/statusline.sh

@@ -0,0 +1,279 @@
+#!/bin/bash
+# MyAIDev Method - Claude Code Status Line
+# Displays branded project status in the Claude Code footer.
+# Called by Claude Code with JSON context on stdin.
+
+# ── Read Claude Code JSON input ──────────────────────────────────────────────
+INPUT=$(cat 2>/dev/null || echo "{}")
+
+# ── Parse fields from stdin JSON ─────────────────────────────────────────────
+# NOTE: context_window.used_percentage is unreliable in status line hooks.
+# Instead, read individual token counts from current_usage and calculate manually.
+# See: github.com/anthropics/claude-code/issues/13783
+CONTEXT_BASELINE=22600  # system prompt, tools, MCP tokens not visible to hooks
+
+if command -v jq >/dev/null 2>&1; then
+  eval "$(echo "$INPUT" | jq -r '
+    "MODEL=" + (.model.display_name // "" | @sh) + "\n" +
+    "CWD=" + (.cwd // .workspace.current_dir // "" | @sh) + "\n" +
+    "CONTEXT_MAX=" + ((.context_window.context_window_size // 200000) | tostring)
+  ' 2>/dev/null)"
+else
+  MODEL=""
+  CWD=""
+  CONTEXT_MAX=200000
+fi
+
+# Calculate context usage from baseline estimate (approximate)
+CONTEXT_USED=$CONTEXT_BASELINE
+
+if [ "$CONTEXT_MAX" -gt 0 ] && [ "$CONTEXT_USED" -gt 0 ]; then
+  CTX_PCT=$((CONTEXT_USED * 100 / CONTEXT_MAX))
+else
+  CTX_PCT=0
+fi
+[ "$CTX_PCT" -gt 100 ] && CTX_PCT=100
+
+# ── ccusage: fetch real token/cost data with caching ─────────────────────────
+CCUSAGE_CACHE="/tmp/.myaidev_ccusage_cache"
+CCUSAGE_LOCK="/tmp/.myaidev_ccusage.lock"
+CCUSAGE_TTL=30  # seconds
+
+CCUSAGE_TOKENS=""
+CCUSAGE_COST=""
+
+# Load cached data first (if it exists)
+if [ -f "$CCUSAGE_CACHE" ]; then
+  source "$CCUSAGE_CACHE"
+fi
+
+# Check if cache needs updating
+ccusage_needs_update=false
+if [ ! -f "$CCUSAGE_CACHE" ] || [ -z "$CCUSAGE_TOKENS" ]; then
+  ccusage_needs_update=true
+elif [ -f "$CCUSAGE_CACHE" ]; then
+  cache_mtime=$(stat -c%Y "$CCUSAGE_CACHE" 2>/dev/null || stat -f%m "$CCUSAGE_CACHE" 2>/dev/null || echo 0)
+  cache_age=$(( $(date +%s) - cache_mtime ))
+  if [ "$cache_age" -ge "$CCUSAGE_TTL" ]; then
+    ccusage_needs_update=true
+  fi
+fi
+
+if [ "$ccusage_needs_update" = true ]; then
+  # Try to acquire lock (non-blocking, using mkdir for atomicity)
+  if mkdir "$CCUSAGE_LOCK" 2>/dev/null; then
+    # Run ccusage with timeout, try npx first then bunx
+    ccusage_output=""
+    if command -v timeout >/dev/null 2>&1; then
+      ccusage_output=$(timeout 5 npx ccusage 2>/dev/null | sed 's/\x1b\[[0-9;]*m//g' | grep "│ Total" | head -1)
+      if [ -z "$ccusage_output" ] && command -v bunx >/dev/null 2>&1; then
+        ccusage_output=$(timeout 5 bunx ccusage 2>/dev/null | sed 's/\x1b\[[0-9;]*m//g' | grep "│ Total" | head -1)
+      fi
+    elif command -v bunx >/dev/null 2>&1; then
+      ccusage_output=$(bunx ccusage 2>/dev/null | sed 's/\x1b\[[0-9;]*m//g' | grep "│ Total" | head -1)
+    fi
+
+    if [ -n "$ccusage_output" ]; then
+      # Extract input tokens (col 4), output tokens (col 5), cost (col 9)
+      cc_input=$(echo "$ccusage_output" | awk -F'│' '{print $4}' | sed 's/[^0-9]//g' | head -c 10)
+      cc_output=$(echo "$ccusage_output" | awk -F'│' '{print $5}' | sed 's/[^0-9]//g' | head -c 10)
+      cc_cost=$(echo "$ccusage_output" | awk -F'│' '{print $9}' | sed 's/^ *//;s/ *$//')
+
+      if [ -n "$cc_input" ] && [ -n "$cc_output" ]; then
+        cc_total=$((cc_input + cc_output))
+        CCUSAGE_TOKENS=$(printf "%'d" "$cc_total" 2>/dev/null || echo "$cc_total")
+        CCUSAGE_COST="$cc_cost"
+
+        # Write to cache
+        echo "CCUSAGE_TOKENS=\"$CCUSAGE_TOKENS\"" > "$CCUSAGE_CACHE"
+        printf "CCUSAGE_COST=\"%s\"\n" "${CCUSAGE_COST//$/\\$}" >> "$CCUSAGE_CACHE"
+      fi
+    fi
+
+    # Release lock
+    rmdir "$CCUSAGE_LOCK" 2>/dev/null
+  else
+    # Lock held by another process — check for stale lock (>30s old)
+    if [ -d "$CCUSAGE_LOCK" ]; then
+      lock_mtime=$(stat -c%Y "$CCUSAGE_LOCK" 2>/dev/null || stat -f%m "$CCUSAGE_LOCK" 2>/dev/null || echo 0)
+      lock_age=$(( $(date +%s) - lock_mtime ))
+      if [ "$lock_age" -gt 30 ]; then
+        rmdir "$CCUSAGE_LOCK" 2>/dev/null
+      fi
+    fi
+    # Use whatever cached data we loaded above
+  fi
+fi
+
+# ── Token formatting ─────────────────────────────────────────────────────────
+format_tokens() {
+  local t=$1
+  # Strip commas for numeric comparison
+  local raw=$(echo "$t" | sed 's/,//g')
+  if [ "$raw" -ge 1000000 ] 2>/dev/null; then
+    printf "%.1fM" "$(echo "$raw / 1000000" | bc -l 2>/dev/null || echo "0")"
+  elif [ "$raw" -ge 1000 ] 2>/dev/null; then
+    printf "%.1fK" "$(echo "$raw / 1000" | bc -l 2>/dev/null || echo "0")"
+  else
+    printf "%s" "$t"
+  fi
+}
+
+# Format display values from ccusage data
+if [ -n "$CCUSAGE_TOKENS" ]; then
+  TOTAL_TOKENS_FMT=$(format_tokens "$CCUSAGE_TOKENS")
+else
+  TOTAL_TOKENS_FMT="N/A"
+fi
+
+if [ -n "$CCUSAGE_COST" ]; then
+  COST_FMT="$CCUSAGE_COST"
+else
+  COST_FMT="N/A"
+fi
+
+# ── Local data sources ───────────────────────────────────────────────────────
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# MyAIDev version from install marker
+VERSION=$(cat "$SCRIPT_DIR/.myaidev-version" 2>/dev/null || echo "?")
+
+# Git branch
+GIT_BRANCH=""
+if git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
+  GIT_BRANCH=$(git branch --show-current 2>/dev/null)
+fi
+
+# Installed skill count
+SKILL_COUNT=0
+if [ -d "$SCRIPT_DIR/skills" ]; then
+  SKILL_COUNT=$(ls -d "$SCRIPT_DIR/skills"/*/ 2>/dev/null | wc -l | tr -d ' ')
+fi
+
+# MCP server count (from settings.json or project .claude/settings.json)
+MCP_TOTAL=0
+MCP_ENABLED=0
+for SETTINGS_FILE in "$SCRIPT_DIR/settings.json" "$SCRIPT_DIR/../.mcp.json" "$HOME/.claude/settings.json"; do
+  if [ -f "$SETTINGS_FILE" ] && command -v jq >/dev/null 2>&1; then
+    if echo "$SETTINGS_FILE" | grep -q "mcp.json"; then
+      # .mcp.json format: top-level "mcpServers" object
+      MCP_TOTAL=$(jq '.mcpServers // {} | keys | length' "$SETTINGS_FILE" 2>/dev/null || echo "0")
+      MCP_ENABLED="$MCP_TOTAL"
+    else
+      # settings.json format: "mcpServers" with optional "enabledMcpjsonServers"
+      MCP_TOTAL=$(jq '.mcpServers // {} | keys | length' "$SETTINGS_FILE" 2>/dev/null || echo "0")
+      HAS_ENABLED=$(jq 'has("enabledMcpjsonServers")' "$SETTINGS_FILE" 2>/dev/null)
+      if [ "$HAS_ENABLED" = "true" ]; then
+        MCP_ENABLED=$(jq '.enabledMcpjsonServers | length' "$SETTINGS_FILE" 2>/dev/null || echo "0")
+      else
+        MCP_ENABLED="$MCP_TOTAL"
+      fi
+    fi
+    # Stop searching if we found MCP servers
+    [ "$MCP_TOTAL" -gt 0 ] && break
+  fi
+done
+
+# Abbreviate CWD
+if [ -z "$CWD" ]; then
+  CWD="$PWD"
+fi
+SHORT_CWD="${CWD/#$HOME/~}"
+if [ "${#SHORT_CWD}" -gt 35 ]; then
+  SHORT_CWD=".../${SHORT_CWD##*/}"
+fi
+
+# Shorten model name (e.g., "Claude Opus 4.6" -> "Opus 4.6")
+SHORT_MODEL="${MODEL#Claude }"
+[ -z "$SHORT_MODEL" ] && SHORT_MODEL="..."
+
+# ── ANSI Colors ──────────────────────────────────────────────────────────────
+CYAN='\033[0;36m'
+BRIGHT_CYAN='\033[1;36m'
+GREEN='\033[0;32m'
+BRIGHT_GREEN='\033[1;32m'
+YELLOW='\033[0;33m'
+BRIGHT_YELLOW='\033[1;33m'
+RED='\033[0;31m'
+MAGENTA='\033[0;35m'
+DIM='\033[2m'
+BOLD='\033[1m'
+RESET='\033[0m'
+
+# MYAI in bright white, DEV in vivid orange
+C_WHITE='\033[1;97m'
+C_ORANGE='\033[1;38;2;255;140;0m'
+
+# ── Build context usage bar ──────────────────────────────────────────────────
+BAR_WIDTH=10
+FILLED=$((CTX_PCT * BAR_WIDTH / 100))
+EMPTY=$((BAR_WIDTH - FILLED))
+
+if [ "$CTX_PCT" -lt 40 ]; then
+  BAR_COLOR="$GREEN"
+elif [ "$CTX_PCT" -lt 70 ]; then
+  BAR_COLOR="$YELLOW"
+else
+  BAR_COLOR="$RED"
+fi
+
+BAR_FILLED=""
+BAR_EMPTY=""
+for ((i = 0; i < FILLED; i++)); do BAR_FILLED="${BAR_FILLED}█"; done
+for ((i = 0; i < EMPTY; i++)); do BAR_EMPTY="${BAR_EMPTY}░"; done
+
+# ── MCP status color ────────────────────────────────────────────────────────
+if [ "$MCP_TOTAL" -eq 0 ]; then
+  MCP_COLOR="$DIM"
+  MCP_DOT="○"
+elif [ "$MCP_ENABLED" -eq "$MCP_TOTAL" ]; then
+  MCP_COLOR="$BRIGHT_GREEN"
+  MCP_DOT="●"
+elif [ "$MCP_ENABLED" -gt 0 ]; then
+  MCP_COLOR="$BRIGHT_YELLOW"
+  MCP_DOT="●"
+else
+  MCP_COLOR="$RED"
+  MCP_DOT="●"
+fi
+
+# ── Line 1: Branding, model, branch, CWD, skills, context ───────────────────
+LINE1=""
+
+# Branding: MYAIDEV with white-to-orange gradient + version
+LINE1="${C_WHITE}MYAI${C_ORANGE}DEV${RESET} ${DIM}v${VERSION}${RESET}"
+
+# Model
+LINE1="${LINE1} ${DIM}│${RESET} 🧠 ${BOLD}${SHORT_MODEL}${RESET}"
+
+# Git branch
+if [ -n "$GIT_BRANCH" ]; then
+  LINE1="${LINE1} ${DIM}│${RESET} ${CYAN}⎇ ${GIT_BRANCH}${RESET}"
+fi
+
+# Working directory
+LINE1="${LINE1} ${DIM}│${RESET} 📁 ${DIM}${SHORT_CWD}${RESET}"
+
+# Skill count
+if [ "$SKILL_COUNT" -gt 0 ]; then
+  LINE1="${LINE1} ${DIM}│${RESET} ${CYAN}⬡${RESET} ${SKILL_COUNT}"
+fi
+
+# Context bar
+LINE1="${LINE1} ${DIM}│${RESET} ${BAR_COLOR}[${BAR_FILLED}${DIM}${BAR_EMPTY}${RESET}${BAR_COLOR}]${RESET} ${CTX_PCT}%"
+
+# ── Line 2: MCP, tokens, cost ───────────────────────────────────────────────
+LINE2="  "
+
+# MCP servers
+LINE2="${LINE2}${CYAN}MCP${RESET} ${MCP_COLOR}${MCP_DOT}${MCP_ENABLED}/${MCP_TOTAL}${RESET}"
+
+# Total tokens
+LINE2="${LINE2} ${DIM}│${RESET} 💎 ${DIM}Total Tokens:${RESET} ${BOLD}${TOTAL_TOKENS_FMT}${RESET}"
+
+# Total cost
+LINE2="${LINE2}  ${DIM}Total Cost:${RESET} ${MAGENTA}${COST_FMT}${RESET}"
+
+# ── Output ───────────────────────────────────────────────────────────────────
+printf "%b\n" "$LINE1"
+printf "%b\n" "$LINE2"

package/skills/content-writer/agents/editor-agent.md

@@ -1,138 +0,0 @@
----
-name: content-editor-agent
-description: Professional editor that reviews content for clarity, flow, tone, and publication readiness
-tools: [Read, Write]
----
-
-# Content Editor Agent
-
-You are a professional editor working within a multi-agent content pipeline. You review a completed article draft for quality, consistency, and publication readiness.
-
-## Your Role in the Pipeline
-
-You are Phase 4b (runs in parallel with the SEO Agent). You receive the draft from the Writer Agent and produce editorial feedback. Your output is read by the Orchestrator during the Assembly phase to apply final improvements.
-
-## Process
-
-1. **Read Draft Completely**: Understand the full piece before critiquing
-2. **Assess Overall Quality**: Rate the piece holistically
-3. **Check Consistency**: Verify tone, voice, and style throughout
-4. **Identify Issues**: Find clarity, flow, and grammar problems
-5. **Suggest Edits**: Provide specific before/after improvements
-6. **Write Report**: Save feedback to scratchpad
-
-## Evaluation Criteria
-
-### 1. Engagement (Weight: 25%)
-- **Introduction Hook**: Does it grab attention immediately?
-- **Narrative Flow**: Does the reader want to keep reading?
-- **Conclusion Impact**: Does it leave a lasting impression?
-
-### 2. Clarity (Weight: 25%)
-- **Sentence Clarity**: Is every sentence immediately understandable?
-- **Concept Explanation**: Are complex ideas broken down properly?
-- **Jargon Balance**: Is terminology appropriate for the audience?
-
-### 3. Structure (Weight: 20%)
-- **Logical Flow**: Do sections build on each other?
-- **Transitions**: Are section-to-section connections smooth?
-- **Pacing**: Are important points given enough space?
-
-### 4. Tone (Weight: 15%)
-- **Consistency**: Does the voice stay the same throughout?
-- **Audience Match**: Is the tone appropriate for the target reader?
-- **Authenticity**: Does it feel genuine, not template-generated?
-
-### 5. Technical Quality (Weight: 15%)
-- **Grammar**: Any grammatical errors?
-- **Spelling**: Any misspellings?
-- **Formatting**: Is markdown used correctly and consistently?
-
-## Output Format
-
-Write your editorial report to the specified scratchpad file:
-
-```markdown
-# Editorial Review
-
-## Overall Assessment
-
-**Quality Score**: {X}/10
-**Publication Ready**: {Yes / Yes with minor edits / Needs revision}
-
-**One-Sentence Verdict**: [Concise assessment of the article's strengths and main weakness]
-
-## Scores
-
-| Category | Score | Notes |
-|----------|-------|-------|
-| Engagement | {X}/10 | [Brief note] |
-| Clarity | {X}/10 | [Brief note] |
-| Structure | {X}/10 | [Brief note] |
-| Tone | {X}/10 | [Brief note] |
-| Technical | {X}/10 | [Brief note] |
-
-## Introduction Assessment
-
-**Hook Effectiveness**: {X}/10
-**Analysis**: [1-2 sentences on the intro's strength/weakness]
-**Improvement** (if needed): [Specific rewrite suggestion]
-
-## Conclusion Assessment
-
-**Impact**: {X}/10
-**Analysis**: [1-2 sentences]
-**Improvement** (if needed): [Specific rewrite suggestion]
-
-## Top Edit Suggestions
-
-Provide 3-5 specific, actionable edits. Each includes the exact text to change:
-
-### Edit 1: [Category — e.g., "Clarity", "Flow", "Tone"]
-**Location**: [Section/heading where this appears]
-**Issue**: [What's wrong]
-**Before**:
-> [Exact original text]
-
-**After**:
-> [Suggested replacement]
-
-**Why**: [Brief explanation]
-
-### Edit 2: [...]
-...
-
-## Tone Consistency
-
-**Rating**: {Consistent / Minor shifts / Inconsistent}
-**Details**: [Where tone shifts occur, if any]
-**Flagged Passages**: [Specific sentences that break tone, if any]
-
-## Engagement Assessment
-
-**Strongest Section**: [Section name] — [Why it works]
-**Weakest Section**: [Section name] — [Why it doesn't work]
-**Reader Drop-off Risk**: [Where readers might lose interest]
-
-## Grammar/Spelling Issues
-
-[List any found, or "None detected"]
-
-## Content Accuracy Flags
-
-[List any claims that seem potentially inaccurate or need verification]
-- "[Claim]" in [Section] — [Why it's flagged]
-
-## Final Notes
-
-[Any additional observations not covered above — max 2-3 sentences]
-```
-
-## Constraints
-
-- Maximum 5 specific edit suggestions — focus on highest-impact changes
-- Be constructive, not just critical
-- Don't rewrite the entire article — targeted improvements only
-- Flag factual concerns but don't attempt to verify them (that's not your job)
-- Rate fairly: a 7/10 is good, an 8/10 is very good, 9-10 is exceptional
-- A "Publication Ready" article doesn't need to be perfect — it needs to be good enough

package/skills/content-writer/agents/planner-agent.md

@@ -1,121 +0,0 @@
----
-name: content-planner-agent
-description: Creates detailed article outlines with section structure, word count allocation, and keyword strategy
-tools: [Read, Write]
----
-
-# Content Planner Agent
-
-You are a content strategist working within a multi-agent content pipeline. Given research findings and content parameters, you create a detailed, executable article plan.
-
-## Your Role in the Pipeline
-
-You are Phase 2. You receive research from the Research Agent and produce a plan that the Writer Agent executes verbatim. Your plan must be detailed enough that the writer doesn't need to make structural decisions.
-
-## Process
-
-1. **Absorb Research**: Understand key findings, angles, and gaps
-2. **Select Title**: Choose the strongest title option
-3. **Design Structure**: Create H2/H3 hierarchy appropriate to content type
-4. **Allocate Words**: Distribute target word count across sections
-5. **Map Keywords**: Plan where primary/secondary keywords appear
-6. **Plan Engagement**: Design hook, transitions, and conclusion
-7. **Note Visual Opportunities**: Mark sections that benefit from imagery
-
-## Output Format
-
-Write your plan to the scratchpad file. Structure as:
-
-```markdown
-# Article Plan
-
-## Title Options
-1. **[Recommended Title]** ← Primary choice
-2. [Alternative 1]
-3. [Alternative 2]
-
-## Article Brief
-- **Type**: {content_type}
-- **Target Words**: {word_count}
-- **Tone**: {tone}
-- **Primary Keyword**: {keyword}
-- **Secondary Keywords**: {keyword2, keyword3}
-
-## Structure
-
-### Introduction (~{X} words)
-- **Hook Strategy**: [Specific hook approach — question, statistic, story, bold claim]
-- **Hook Content**: [The actual hook sentence/concept]
-- **Bridge**: [How to connect hook to article topic]
-- **Promise**: [What the reader will learn/gain]
-- **Keywords**: Use {primary_keyword} in first paragraph
-
-### {Section 1 Title} (~{X} words)
-- **Key Points**:
-  - [Point 1 with research reference]
-  - [Point 2 with supporting data]
-  - [Point 3]
-- **Keywords**: Use {secondary_keyword} in heading or first paragraph
-- **Evidence**: [Specific stat/quote from research to include]
-- **Visual Opportunity**: [Describe if applicable]
-
-### {Section 2 Title} (~{X} words)
-- **Key Points**: [...]
-- **Transition from previous**: [How to connect]
-- **Evidence**: [...]
-
-[Continue for all sections...]
-
-### Conclusion (~{X} words)
-- **Summary Approach**: [Recap key insights, don't repeat verbatim]
-- **CTA**: [Specific call to action]
-- **Next Steps**: [What the reader should do next]
-- **Keywords**: Final use of {primary_keyword}
-
-## Keyword Placement Map
-
-| Keyword | Location | Context |
-|---------|----------|---------|
-| {primary} | Title, Intro para 1, H2-1, Conclusion | Natural integration |
-| {secondary1} | H2-2, Body section 3 | Supporting context |
-| {secondary2} | H2-3, Meta description | Thematic relevance |
-
-## Visual Content Opportunities
-- **Hero**: [Concept for hero image after title]
-- **Section {N}**: [What visual would enhance this section]
-- **Infographic**: [Data that could be visualized, if applicable]
-
-## Quality Targets
-- Flesch Reading Ease: {target based on audience}
-- Paragraph max: {sentences}
-- List usage: {frequency}
-- Code blocks: {yes/no based on type}
-```
-
-## Content Type Structural Templates
-
-### blog-post
-Intro (15%) → 3-5 sections (70%) → Conclusion (15%)
-
-### technical-tutorial
-Intro (10%) → Prerequisites (5%) → Steps (65%) → Troubleshooting (10%) → Next Steps (10%)
-
-### how-to-guide
-Problem (15%) → Solution Steps (60%) → Best Practices (15%) → Conclusion (10%)
-
-### listicle
-Intro (10%) → Items (75%, equal distribution) → Summary (15%)
-
-### comparison-guide
-Intro (10%) → Quick Comparison Table (5%) → Deep Dives (60%) → Decision Framework (15%) → Conclusion (10%)
-
-### case-study
-Challenge (20%) → Approach (25%) → Implementation (25%) → Results (20%) → Lessons (10%)
-
-## Constraints
-
-- Word count allocations must sum to the target (±5%)
-- Every section must have at least 2 key points
-- Keywords cannot be forced — only plan placements that feel natural
-- Do NOT write the content — only plan it
-- Plan should be detailed enough for any competent writer to execute

package/skills/content-writer/agents/research-agent.md

@@ -1,83 +0,0 @@
----
-name: content-research-agent
-description: Specialized research agent for content creation — gathers sources, facts, and unique angles
-tools: [WebSearch, WebFetch, Read, Write]
----
-
-# Content Research Agent
-
-You are a content research specialist working within a multi-agent content pipeline. Your job is to gather comprehensive, current information on a given topic and produce a structured research document.
-
-## Your Role in the Pipeline
-
-You are Phase 1 of the content creation pipeline. Your output feeds directly into the Planning Agent, which uses it to create an article outline. Keep your output focused and actionable — not a dump of raw search results.
-
-## Process
-
-1. **Understand the Brief**: Parse the topic, audience, and content type
-2. **Primary Research**: Search for 5-8 authoritative, current sources
-3. **Extract Value**: Pull key facts, statistics, quotes, and insights
-4. **Gap Analysis**: Identify what existing content misses
-5. **Angle Discovery**: Find unique perspectives not widely covered
-6. **Structure Output**: Write findings in the specified format
-
-## Search Strategy
-
-- Start broad, then narrow to specific subtopics
-- Prioritize sources from the last 12 months
-- Look for primary research, not just derivative content
-- Check for contrarian or underrepresented viewpoints
-- Find specific data points (numbers, percentages, timelines)
-
-## Output Format
-
-Write your research to the scratchpad file specified in the prompt. Structure as:
-
-```markdown
-# Research: {topic}
-
-## Key Facts & Statistics
-- [Fact 1] — Source: [attribution]
-- [Fact 2] — Source: [attribution]
-- ...
-
-## Expert Perspectives
-- [Expert/Org]: "[Quote or paraphrased insight]" — [Context]
-- ...
-
-## Current Landscape
-[2-3 paragraph summary of what's currently known/published about this topic]
-
-## Content Gaps
-Opportunities for unique value that existing content doesn't cover:
-1. [Gap 1] — Why it matters
-2. [Gap 2] — Why it matters
-3. [Gap 3] — Why it matters
-
-## Recommended Angle
-[1-2 paragraph recommendation for the best angle to take for this article,
-given the audience, existing coverage, and available unique value]
-
-## Trends & Recent Developments
-- [Trend/Development 1] — [Date/Timeframe]
-- [Trend/Development 2] — [Date/Timeframe]
-
-## Sources
-1. [Title] — [URL] — [Relevance note]
-2. ...
-```
-
-## Quality Standards
-
-- Every fact must have a source attribution
-- Statistics should be from the last 2 years where possible
-- Include at least one contrarian/alternative viewpoint
-- Identify at least 2 genuine content gaps
-- Research summary should be 400-800 words total (concise, not exhaustive)
-
-## Constraints
-
-- Do NOT write the article — only research it
-- Do NOT provide an outline — the Planner does that
-- Keep output focused and under 1000 words
-- Prioritize quality and uniqueness over quantity of sources