tritonkit-subagent-supervision

Orchestrates subagent task delegation, evidence-based auditing, and integration closure for parallel development work.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-subagent-supervision-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-subagent-supervision
Source: https://github.com/NeptuneKit/TritonKit/tree/main/.agents/skills/tritonkit-subagent-supervision
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-subagent-supervision-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI subagents on parallel coding tasks often leads to conflicting edits, unverified claims of completion, and messy Git history. This Skill gives a supervising agent a disciplined workflow for splitting work, auditing subagent output against real evidence, and closing the loop on integration, testing, and GitHub issue cleanup. ## Core Features & Use Cases - Supervision Modes: Choose between watch-only monitoring, read-only audit, audit-and-fix, or multi-agent comparison depending on the user's request and permissions. - Evidence-Based Auditing: Verify subagent claims against git status, diffs, command output, CI results, and screenshots, classifying findings as Gap, Bug, Verification miss, Scope drift, or No issue. - GitHub Issue Parallelism: Isolate each issue in its own worktree and branch, then merge, test, clean up worktrees, push, and close issues through a controlled end-to-end procedure. - Use Case: A user asks to process three GitHub issues in parallel without mixing work; the supervising agent spawns one subagent per issue worktree, audits each result, merges branches with preflight conflict checks, runs focused tests, and closes only the verified issues. ## Quick Start Ask the agent to split this task across subagents and supervise them through to verified completion.

Frequently Asked Questions about tritonkit-subagent-supervision

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

FAQPage Schema
How do I supervise multiple AI subagents working in parallel?▼

Split the work by write surface so no two subagents edit the same files, give each a self-contained handoff packet with goals, allowed files, and verification commands, then integrate results continuously. The supervising agent keeps final completion judgment and verifies all claims against evidence.

How to audit code changes made by another AI agent?▼

Rebuild the original request and constraints as a contract, then check git status, diffs, command outputs, CI logs, and screenshots rather than trusting the agent's summary. Classify findings as Gap, Bug, Verification miss, Scope drift, or No issue in a structured report.

Can I process multiple GitHub issues in parallel without mixing work?▼

Yes, assign each issue its own space, branch, and git worktree so subagents never share files. The supervisor merges branches individually with preflight conflict checks, runs focused tests, and only then pushes and closes the verified issues.

When should I not use subagent parallelization?▼

Avoid parallel subagents for simple tasks, tightly coupled changes to the same file, or work with shared environment side effects. Read-only audits can run in parallel, but write tasks must be isolated by file surface to prevent conflicts.

What evidence should a subagent return when finishing a task?▼

A subagent should return touched files with line numbers, a diff summary, the verification commands run with their real output, any failures or skipped steps, screenshots for UI changes, and remaining open questions. Completion claims without this evidence are treated as unverified.