hunt

Automate brief implementation from planning through commit with subagent orchestration.

10|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/fiftynotai/igris-ai --skill hunt-fiftynotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt
Source: https://github.com/fiftynotai/igris-ai/tree/main/.claude/skills/hunt
Command: npx skills add https://github.com/fiftynotai/igris-ai --skill hunt-fiftynotai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates manual coordination and context-switching when implementing a development brief by automating the full lifecycle from planning to commit, ensuring each step is tracked and validated.

Core Features & Use Cases

  • End-to-end orchestration: Delegates planning, implementation, testing, review, documentation, and committing across specialized subagents (architect, forger, sentinel, warden, mender, document).
  • Integration and guards: Updates session state, emits optional brain MCP events and heartbeats, enforces retry and blocking logic for failing tests or reviews, and produces conventional commits that reference the brief.
  • Use Case: Run /hunt BR-008 to load a brief from ai/briefs, generate a plan, implement changes, run tests, perform review gates, update docs if needed, and commit the result.

Quick Start

Invoke the hunt skill with a brief ID to run the full implementation workflow for that brief, for example: /hunt BR-008

Frequently Asked Questions about hunt

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

FAQPage Schema
How do I automate git workflow implementation from a project brief?

Automating git workflow implementation from a project brief is done by orchestrating subagents to handle planning, building, testing, reviewing, documenting, and committing. This ensures each step is tracked and validated through approval gates.

What is the best way to orchestrate subagents for end-to-end development tasks?

Orchestrating subagents for end-to-end development tasks involves delegating work across specialized agents like architect, forger, sentinel, warden, mender, and document. This eliminates manual coordination and context-switching during brief implementation.

How do I enforce testing and review gates before committing code changes?

Enforcing testing and review gates before committing code changes requires applying retry and blocking logic during the workflow. If tests or reviews fail, the orchestration blocks progress until issues are resolved.

Can I integrate session state and MCP events into my automated build process?

Integrating session state and MCP events into an automated build process is supported through local git updates, ai/session/CURRENT_SESSION.md tracking, and optional igris-brain MCP events like igris_agent_event and igris_instance_heartbeat.

Do I need a specific brief format to start automated project implementation?

A specific brief format stored in ai/briefs is needed to start automated project implementation. You invoke the workflow with a brief ID, such as BR-008, to load the requirements and generate a plan.

What are the limitations of automating brief implementation with subagent orchestration?

Limitations of automating brief implementation with subagent orchestration include dependency on specific directory structures like ai/briefs and ai/session/CURRENT_SESSION.md, and potential blocking if failing tests or reviews cannot be automatically resolved.