agent-issue-delegation

Files (9)

• SKILL.md
• batch-pr-integration.md · references/
• dart-commands.md · references/
• label-refresh-and-pr-noise.md · references/
• ola6-incidentes-referencia.md · references/
• ola8-wave1-results.md · references/
• session-failure-patterns.md · references/
• wave10-validated-template.md · references/
• xavier-980-template.md · references/

SKILL.md (first lines)

# Agent Issue Delegation — Professional Issue Templates

> ⚠️ **CANONICAL TEMPLATE:** `gitcore-jules-issues` v3.0+ (unifica 6 skills previos, Jul 2026).
> Este skill contiene **reglas generales de delegación** válidas para cualquier agente.
> Para el template section-by-section exacto, cargar `gitcore-jules-issues`.

> ⚠️ **Rule:** Label `jules` triggers Jules. For other agents use their convention.
>
> ⚠️ **Language:** Issues, documentation, and code examples MUST be in English. Only user-facing conversation may be in the user's language. When the user writes in Spanish, respond in Spanish but keep code comments, issue bodies, documentation, and PR descriptions in English.
>
> ⚠️ **Wave Size = 14-15 issues:** Jules takes issues with the `jules` label up to ~14-15 simultaneously. Create waves of exactly 14-15 with disjoint file islands.
> - Less than 10 wastes parallel capacity
> - More than 16 becomes unmanageable for review/merge
> - Issue #15 = reconciliation (features.json update) — ALWAYS last
> - Each issue = single action. 1 issue = 1 file = 1 change. Multi-feature issues fail 100%.
>
> ⚠️ **features.json NOT modified during the wave.** Each issue writes progress to `.gitcore/ola8-progress/<feature-id>.json` (individual file). The reconciliation issue at wave end unifies all into features.json.
>
> ⚠️ **Single Action = Success:** Single-action issues (verify + update progress file) have ~70% success rate. Multi-feature issues have 0%. Always split.
>
> ⚠️ **Delivery binding:** Every issue delegated to an agent MUST result in committed+push to GitHub. Local-only changes are not a valid delivery.
>
> ⚠️ **Repo boundary:** Xavier (Rust) and isar_agent_memory (Dart) are separate repos. Do not cross-contaminate issues. They communicate via MCP/HTTP only.

## ⚠️ MANDATORY RULES FOR EVERY ISSUE


### 🔍 Web Research Required (MANDATORY — in EVERY issue)

⚠️ **The user WILL correct you if this section is missing. Always include it.**

Every issue MUST contain a Web Research Required section. This is non-negotiable.

The agent must research the most current approaches BEFORE implementing. Without this section, the agent implements with potentially outdated knowledge.

Include **3-4 specific, searchable queries**:
```markdown
## Web Research Required
1. `search: "[primary technology] best practices 2026"`
2. `search: "[alternative library/pattern] comparison"`
3. `search: "[crate/package] documentation latest API"`
4. `search: "[algorithm/approach] modern implementation"`
```

Failure to include this section = issue is INCOMPLETE. Do not delegate without it. Use `gitcore-jules-issues` skill for the exact template.

### ✅ Tests + Lint (MANDATORY)
**Every delivery MUST include:**
- Tests validating the functionality (unit + integration where applicable)
- Lint passes with 0 errors (use correct command per stack):
  - **Rust:** `cargo clippy -p xavier --all-targets -- -D warnings`
  - **Dart/Flutter:** `dart analyze lib/`
  - If the agent cannot pass lint, document why in the PR

Without tests + green lint → the PR will NOT be merged.

### 📍 Documentation Language (MANDATORY)
All code comments, variable names, issue bodies, PR descriptions, README, docs, and commit messages MUST be in English. Only user-facing conversation may be in the user's language (e.g. Spanish when the user writes in Spanish). When in doubt, write in English.

### 🧱 Repo Boundaries (MANDATORY)
Before creating any issue, confirm the feature belongs to THIS repo:
- **Xavier** (`iberi22/xavier`) = Rust memory server — MCP/HTTP interface, mesh sync, security
- **isar_agent_memory** (`iberi22/isar_agent_memory`) = Dart/Flutter memory engine — offline-first, mobile/edge
- They communicate via MCP/HTTP only. Never create Xavier features in isar_agent_memory or vice versa.

### Delivery Requirements

**Every issue delegated to an agent MUST result in committed+push to GitHub.** Local-only changes are not a valid delivery — the repo on GitHub is the single source of truth.

**Documentation and code MUST be in English.** Only user-facing conversation may be in the user's language. Issue bodies, code comments, variable names, PR descriptions, API docs — all English.

**Xavier integration is via MCP only.** Never couple code between Xavier (Rust) and isar_agent_memory (Dart). They are separate repos that communicate through MCP/HTTP.

### Post-Creation QA Audit

After creating ALL issues in a wave, run verification BEFORE applying any `jules` label:

```bash
# 1. Check body length (empty body = wasted session)
for n in $(gh issue list --repo <repo> --label wave-N --state open --json number --jq '.[].number'); do
  body=$(gh issue view $n --repo <repo> --json body --jq '.body | length')
  title=$(gh issue view $n --repo <repo> --json title --jq .title)
  if [ "$body" -lt 50 ]; then
    echo "❌ #$n EMPTY BODY ($body chars): $title"
  elif [ "$body" -lt 200 ]; then
    echo "⚠️ #$n SHORT BODY ($body chars): $title"
  else
    echo "✅ #$n ($body chars)"
  fi
done

# 2. Check Web Research Required section exists
for n in $(gh issue list --repo <repo> --label wave-N --state open --json number --jq '.[].number'); do
  body=$(gh issue view $n --repo <repo> --json body --jq .body)
  if echo "$body" | grep -q "Web Research"; then
    echo "✅ #$n has Web Research"
  else
    echo "❌ #$n MISSING Web Research Required — FIX BEFORE DELEGATING"
  fi
done

# 3. Check Acceptance Criteria and Failure Recovery
for n in $(gh issue list --repo <repo> --label wave-N --state open --json number --jq '.[].number'); do
  body=$(gh issue view $n --repo <repo> --json body --jq .body)
  has_ac=$(echo "$body" | grep -c "Acceptance Criteria")
  has_fr=$(echo "$body" | grep -c "Failure Recovery")
  echo "#$n: AC=$has_ac FR=$has_fr"
done

# 4. Verify file islands are disjoint
python3 -c "
issues = {}
for n in [LIST_OF_ISSUE_NUMBERS]:
    # Extract Files to Modify from each issue
    issues[f'#{n}'] = ['path1.rs', 'path2.rs']  # fill from issue bodies
for i1, f1 in issues.items():
    for i2, f2 in issues.items():
        if i1 < i2 and set(f1) & set(f2):
            print(f'❌ CONFLICT: {i1} and {i2} share files!')

From iberi22/skills, MIT.

More from iberi22/skills