start

Orchestrates multi-agent workflows to autonomously process GitHub Issues from research through merged PR.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/seal-harness/seal-harness --skill start-seal-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/seal-harness/seal-harness/tree/main/.agents/skills/start
Command: npx skills add https://github.com/seal-harness/seal-harness --skill start-seal-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple AI agents on a software task is error-prone: agents self-certify their own work, skip reviews, and lose context between steps. This Skill provides a structured orchestration workflow that takes a GitHub Issue from initial research through planning, adversarial review, TDD implementation, and PR merge with enforced quality gates. ## Core Features & Use Cases - Multi-Agent Orchestration: Spawns specialized agents (Researcher, Architect, Coder, Code Reviewer, Security Auditor, PR Shepherd, Release Engineer) with defined roles and handoff protocols. - Gated Review Pipeline: Enforces a Plan Review Gate, a parallel Design Review Gate, and a 4-phase execution loop (Implement, Validate, Adversarial Review, Commit) where quality gates are blocking state transitions. - Task Tracking & Escalation: Manages work via markdown task documents in docs/tasks/, with human escalation after 3 failed iterations and GTG merge-readiness checks. - Use Case: A GitHub Issue labeled agent-ready is claimed automatically: the orchestrator researches the codebase, produces a reviewed implementation plan, decomposes it into work units, implements each with TDD and independent adversarial review, then opens and shepherds the PR to merge. ## Quick Start Start work on GitHub Issue 123 by saying: start task 123.

Frequently Asked Questions about start

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

FAQPage Schema
How do I start an AI agent on a GitHub Issue?

Label the issue agent-ready, then trigger the workflow with a command like start task 123. The orchestrator verifies the label, creates a task document in docs/tasks/, posts an acknowledgment comment, and spawns the Issue Orchestrator agent.

How does multi-agent code review work in this workflow?

Implementation passes a 4-phase loop: implement, independent validation by the orchestrator, adversarial review with binary PASS/FAIL verdicts and file:line evidence, then commit. Re-reviews always use a fresh reviewer instance to prevent anchoring bias.

When should I not use orchestrated execution?

Skip it for single-file bug fixes, copy changes, tasks without a written spec or Definition of Done items, and quick prototyping. The standard linear flow of implement, code review, and PR is sufficient for simple tasks.

What happens when an agent fails repeatedly on a task?

After 3 failed iterations the task is marked blocked with a waiting:human label, and the agent posts a structured escalation comment on the GitHub Issue with options and a recommendation. Humans respond with approve, respond, request-changes, or defer commands.

Can external AI tools like Codex or Gemini participate in the workflow?

Yes, when configured in docs/external-tools.yaml, the orchestrator can delegate implementation to OpenAI Codex CLI or Google Gemini CLI in isolated git worktrees. Cross-model adversarial review ensures the writer is always reviewed by a different model.