Research

Dev-Loop Research Agent

Pluggable research cycle for dev-loop. Scans configurable health tracks, cross-references findings with retros, outputs prioritized work-item recommendations.

Model Strategy

This agent is spawned by dev-loop with model: "sonnet". Code health scanning (coverage gaps, skills drift, spec drift, unpushed commits) and vault health scanning (raw coverage, cross-links, page quality, type coverage) are mechanical analysis tasks — searching, counting, pattern matching. Sonnet handles these at ~5x lower cost than Opus with no quality loss for this work.

When invoked standalone (not via dev-loop), default to the calling session's model.

Architecture

┌─────────────────────────────────────────┐
│ 0. RESOLVE CAPABILITIES                 │
│    Detect: cli_backend, vault_backend   │
├─────────────────────┬─────────────────┤
│ TRACK A (optional)  │ TRACK B (opt)   │
│ Code Health         │ Vault Health    │
│ - Coverage gaps     │ - Raw coverage  │
│ - Skills drift      │ - Cross-links   │
│ - Spec drift        │ - Page quality  │
│ - Unpushed commits  │ - Type coverage │
├─────────────────────┴─────────────────┤
│ 1. RETROS (if vault_backend)            │
│ 2. SYNTHESIZE → P0-P3 (P4+ in high)     │
│ 3. OUTPUT (vault log + memory)          │
└─────────────────────────────────────────┘

Capabilities Detection

At REFRESH, re-derive BACKEND_CAPS using the same logic as the parent dev-loop skill. Do NOT assume inherited state — explicitly resolve from config:

1. Read knowledge_layer from project config (default: skillwiki if vault exists, none otherwise).
2. Resolve BACKEND_CAPS from knowledge_layer — same registry/defaults as parent skill REFRESH step.
3. Derive track booleans from BACKEND_CAPS membership:

Skip tracks when backends unavailable. Run with available tracks only.

Critical: BACKEND_CAPS controls work-item creation paths in the Output step. If create_work_item is in BACKEND_CAPS, use proj-work for vault-native paths. Only fall back to git-local (.claude/dev-loop-work/) when create_work_item is absent.

Intensity

Parse args for high (case-insensitive). Default: normal.

Track A: Code Health

Skip if cli_backend unavailable.

A0. Critical-Path Ranking Bias

If CRITICAL_PATHS session variable is non-empty, apply ranking bias:

• Coverage gaps in files matching CRITICAL_PATHS.*.code globs are promoted one priority tier above their calculated score (e.g., P2 → P1).
• This ensures hot-spot files get attention before equivalent-severity findings in non-critical paths.
• The bias applies AFTER scoring, as a post-rank adjustment.

A1. Coverage Gaps

• Source files in {cli_src}/ without matching {cli_test}/ tests
• Missing behavioral conventions (--human, exit codes)
• Markers: TODO|FIXME|HACK|XXX

A2. Skills Drift

• SKILL.md files referencing non-existent CLI commands
• Skill descriptions stale vs actual behavior
• Skill counts drift from documented

A3. Spec Drift

• New commands not in canonical spec
• Changed counts vs spec snapshot
• Schema changes unreflected

A4. Unpushed Commits

git log origin/${release_branch:-main}..HEAD --oneline 2>/dev/null | wc -l

• ≥10 → P1 | 5-9 → P2 | 1-4 → P4+ (defer, unless high)

Track B: Vault Health

Skip if vault_backend unavailable.

B1. Raw Coverage

• Uncited raw files % (P1: >50% normal, >20% high)
• Single-source pages (P2)

B2. Cross-Link Density

• Isolated pages (<2 links normal, <3 high)
• Orphan clusters (via backend orphans if available)
• Overlap clusters (via backend overlap if available)

B3. Page Quality

• Thin pages (<40L normal, <60L high)
• Missing Overview/Related sections
• Missing TL;DR: pages with confidence: high but TL;DR section contains only placeholder strings (Pending summary., TBD, TODO, single-bullet stub). Flag as info severity — high-confidence hub pages should not ship with placeholder summaries. Surface alongside thin-page findings.

B4. Type Coverage

• Empty type dirs (entities, comparisons, queries, meta)
• High: flag regardless of total pages

Retros

If vault_backend:

• Scan {vault}/log.md for Improve: actions
• Check {vault}/projects/{slug}/compound/ for pending work
• Retro actions → direct work-item candidates

Idle Deep-Research Handoff

When this research agent returns no P2+ findings (truly idle), the parent dev-loop may invoke /deep-research per the idle_deep_research config section (see IDLE DISCOVERY step 3.5 in SKILL.md).

This agent's role in the handoff:

1. Report the idle state clearly: "Research idle — no P2+ findings."
2. The parent loop then decides whether to invoke deep-research based on idle_deep_research.enabled, cooldown, and daily cap.
3. Deep-research is a separate skill invocation — this agent does NOT call it directly. The handoff is at the dev-loop orchestration layer.

If the research agent returns P2+ findings, deep-research is skipped — there's claimable work to pick up.

Synthesize

Score: impact × effort

Ownership classification (applied before final ranking): Classify each finding by ownership boundary before applying P-scores:

• project-owned: the finding is in the current repository/project's code or vault pages. Highest claimability.
• vault-global: vault-wide findings (sensitive-content detections, broken wikilinks across projects). Real maintenance, but should not displace the highest actionable project-owned finding.
• cross-project: findings spanning multiple projects. Route to the appropriate project or maintenance project.
• external-approval-required: findings that require human approval before any code or mutation change.

Report both a global maintenance priority and a current-project priority. Prevent sensitive-content detector hits from being described as confirmed live secrets until attended classification occurs; never print detected values. Route global SkillWiki integrity work to the appropriate llm-wiki or maintenance project rather than creating an unrelated agent-skills work item automatically.

Output format:

### #[N]: [title] (Px)
**Source**: [track.source]
**What**: One-paragraph spec.
**Acceptance**: Verifiable outcomes.

Idle Detection

Pre-idle gate: Check metrics before declaring idle.

Healthy thresholds:

• Uncited: <50% (normal), <20% (high)
• Isolated: 0
• Thin: 0 (at thresholds)

Never report idle with actionable gaps.

Output

Work-item creation

When synthesizing recommendations that need work items, check create_work_item in BACKEND_CAPS:

• create_work_item in BACKEND_CAPS: Use proj-work to create work items under {vault}/projects/{slug}/work/. This ensures wiki indexing, knowledge.md references, and wiki-lint visibility.
• create_work_item not in BACKEND_CAPS: Fall back to .claude/dev-loop-work/YYYY-MM-DD-{slug}/ (git-local path). Ensure .claude/dev-loop-work/ is in .gitignore.

Never silently default to git-local when the vault backend is configured — this bypasses the vault and breaks provenance.

Logging

If vault_backend:

• Append to {vault}/log.md
• Update MEMORY.md if top-N changed

Always: one-line exit summary.

Backend Interface (Pluggable)

The agent delegates to configured backends. Expected interface:

interface ResearchBackend {
  // Detection
  isAvailable(): boolean;

  // Track A
  listSourceFiles(): string[];
  listTestFiles(): string[];
  listSkillFiles(): string[];

  // Track B
  countRawFiles(): number;
  countCitedRaw(): number;
  countIsolatedPages(): number;
  countThinPages(threshold: number): number;
  listOrphanPages(): string[];

  // Output
  appendLog(entry: string): void;

  // Work-item creation (requires create_work_item in BACKEND_CAPS)
  createWorkItem(slug: string, kind: string): { specPath: string; planPath: string };
}

Default implementations provided for:

• cli_backend: filesystem + git
• vault_backend: skillwiki CLI (if available), else fs-only