deep-issue-id

Orchestrate multi-agent waves to identify translation issues in ULT/UST chapters.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill deep-issue-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-issue-id
Source: https://github.com/unfoldingWord/bp-assistant-skills/tree/main/.claude/skills/deep-issue-id
Command: npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill deep-issue-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial multi-agent issue identification for human-authored ULT/UST from repo master. This skill orchestrates issue-identification agents to surface translation concerns and alignment gaps.

Core Features & Use Cases

  • Orchestrates multi-wave issue identification across Wave 2 (structure and rhetoric analysis), Wave 3 (challenger rulings), and Wave 4a (merge/adjudication) to surface actionable translation issues.
  • Supports per-chapter or verse-range analysis with optional context (including editor notes) to inform analysts and align outputs with the human text.
  • Outputs consolidated per-chapter TSVs (and per-verse ranges when provided) suitable for downstream review and publishing workflows.

Quick Start

Ask Claude to run deep-issue-id on a chosen Book and Chapter (optionally with --verses to limit the range) to identify translation issues.

Frequently Asked Questions about deep-issue-id

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify translation issues in ULT and UST text?▼

Translation issue identification in ULT and UST text is handled by orchestrating multiple agents to compare text, detect structural and lexical problems, and apply domain-specific rules across multi-wave workflows.

Can I analyze specific verse ranges instead of a full chapter for translation alignment?▼

You can analyze specific verse ranges by providing optional verse limits alongside the book and chapter, allowing the multi-agent workflow to scope detection and generate per-verse range TSV outputs.

How does multi-agent issue detection work for Bible translation analysis?▼

Multi-agent issue detection works through a deterministic, multi-stage workflow that orchestrates sub-agents across distinct waves for structure analysis, challenger rulings, and merge adjudication to surface actionable translation issues.

What format are translation issues output in for downstream review?▼

Translation issues are output as consolidated per-chapter TSV files, and per-verse range TSVs when specified, making them suitable for downstream review and publishing workflows.

Do I need to provide editor notes when running translation alignment analysis?▼

Editor notes are optional context you can provide to inform analysts and align outputs with the human text, but the workflow can run using the human-authored ULT and UST text directly from the repo master.

What are the limitations of automated issue identification for human-authored translations?▼

Automated issue identification is limited to detecting structural and lexical problems through domain-specific rules and sub-agent adjudication, meaning it surfaces actionable flags for review rather than automatically correcting translation text.