Jules Delegator

[TheRealAshik]

---

name: jules-delegator
description: Autonomous delegation of complex, multi-file coding tasks to the Jules AI Agent. Use when the user mentions "Jules", "Delegate", or "Agent", or when a task requires changes across more than 3 files, involves dependency management, or needs a Pull Request generated.
metadata:
version: "1.1.0"
category: automation/workflow

🎯 Purpose & Scope

Use this skill to offload deep architectural refactoring, multi-file feature implementations, or complex debugging sessions to an autonomous environment.

Trigger Conditions

• Keywords: Whenever the user mentions "Jules", "Delegate", or "Agent".
• Complexity: Tasks requiring changes across >3 files or involving dependency management.
• Autonomy: Requests for long-running background tasks or Pull Request (PR) generation.

⚙️ Execution SOP

1. Pre-Flight Check (Silent)

Gather environmental context without bothering the user:

• Identify Repo: Run git remote get-url origin.
• Identify Branch: Run git branch --show-current.
• Validation: If metadata is missing, use message_user to clarify: "I need the target repository and branch to proceed."

2. Triage & Strategy (Silent)

Analyze the request to determine:

• Intent: (e.g., Feature, Fix, Refactor).
• Scope: Which specific directories or modules are impacted?
• Risks: Potential breaking changes or security implications.

3. Synthesis

Draft the mission parameters. If blockers exist, resolve them via a single consolidated message_user call.

4. User Confirmation

Present the delegation card using the following format:

📋 Delegation Summary

• Task: [Title]
• Mission: [1-sentence core objective]
• Scope: [Module A, Module B]
• Risk Level: [Low | Medium | High]
• Mode: [Autonomous | Interactive]
  Ready to launch Jules? (Confirm or provide adjustments)

5. Execution

Once the user confirms, call create_session using the Jules Prompt Template below.

📝 Jules Prompt Template

# 🎭 Role
Expert [Language/Framework] Engineer...

# 🚀 Mission
[High-level goal the user wants to achieve]

# 🔍 Details
[Detailed explanation of the technical requirements, existing architecture, UI UX style requirements etc]

# ✅ Acceptance Criteria
- [ ] Criterion 1 (e.g., "All tests in /tests/unit pass")
- [ ] Criterion 2 (e.g., "No changes to public API signatures")
- [ ] Criterion 3 (e.g., "Documentation updated in /docs")

# ⚠️ Constraints
- [Specific constraint, e.g., "Do not use external libraries"]
- [Specific constraint, e.g., "Maintain compatibility with Node v18"]

🛡️ Risk Management

Risk Level	Action Required
Low	Proceed with Autonomous mode; report back upon completion.
Medium	Use Interactive mode; request checkpoints after core logic changes.
High	Requires a dry-run or manual code review of the plan before any file writes.