fellowship

One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.

Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.

Use after receiving PR review feedback. Extracts conventions from reviewer comments and offers to add them to CLAUDE.md. Closes the convention learning loop.

Recover a fellowship after a session crash. Scans worktrees and state files, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.

Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.

Adversarial validation agent. Spawned by quest between Implement and Review phases. Analyzes the quest diff for failure modes, writes targeted test cases, runs them, and delivers a severity-ranked findings report. Critical/High findings must be addressed before the Review gate opens.

Background monitor during fellowship execution. Watches quest progress via task metadata, detects stuck quests, scope drift, and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.

Quest executor that uses the fellowship CLI for gate management. Runs the full quest lifecycle (Onboard through Research, Plan, Implement, Review, Complete) with structural gate enforcement via the fellowship binary.

Research & analysis agent. Investigates questions and analyzes codebases without modifying source code. Can write research notes to docs/research/ or .fellowship/. No git operations, no commits, no PRs.

Use at the start of any non-trivial task. Loads focused, task-relevant context by reading CLAUDE.md, scanning for related files, and producing a structured Session Context block. Invoked automatically by quest or standalone via /council.

Multi-task orchestrator. Coordinates agent teammates (led by Gandalf) running /quest (code) or /scout (research) workflows. Use when you have multiple independent tasks to run in parallel.

Use BEFORE writing any code in an unfamiliar area. Studies reference files from CLAUDE.md to extract conventions and patterns. Prevents "wrong approach" code review rework by understanding how things are done before writing anything.

Use between workflow phases or when context feels bloated. Compresses the current conversation into a structured summary capturing task, findings, files, state, and next steps. Invoke standalone or automatically between quest phases.

Load phase-specific guidance from a quest template. Invoke at the start of each quest phase when a template has been assigned.

6 hooks across 3 events