Install

Add the plugin marketplace, then install Fellowship:

/plugin marketplace add justinjdev/claude-plugins
/plugin install fellowship@justinjdev

Dependencies

These plugins are optional but recommended. Fellowship skill prompts reference them by name.

PluginSkills UsedInstall Commands
superpowersusing-git-worktrees, test-driven-development, verification-before-completion, finishing-a-development-branch
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace
pr-review-toolkitreview-pr
/plugin install pr-review-toolkit@claude-plugins-official

These are referenced by name in skill prompts. If a dependency isn't installed, Claude will skip that step rather than fail -- but you lose the discipline that step provides.

System Dependencies

Go CLI binary
Gate enforcement hooks use a Go binary automatically downloaded from GitHub releases on first use. No manual installation needed.

Project Setup

Optionally add a SessionStart hook to detect checkpoints from previous sessions. Add this to .claude/settings.local.json in your project:

{
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "if [ -f .fellowship/checkpoint.md ]; then echo '--- CHECKPOINT DETECTED ---'; cat .fellowship/checkpoint.md; echo '--- END CHECKPOINT ---'; echo 'A checkpoint from a previous session was found. Use /council to resume or start fresh.'; fi"
          }
        ]
      }
    ]
  }
}

Also add .fellowship/ to your .gitignore so checkpoint files are not committed. If you have configured a custom dataDir in ~/.claude/fellowship.json, use that directory name instead.

Your First Quest

Here is what a typical quest looks like end to end:

  1. Open Claude Code in your project directory.
  2. Run your quest:
    /quest "your task description"
  3. Phase 0 · Onboard Creates a git worktree and loads project context via /council.
  4. Phase 1 · Research Explores the codebase, gathers conventions and relevant prior art.
  5. Phase 2 · Plan Presents a plan for your approval -- review it carefully.
  6. Phase 3 · Implement TDD implementation: red-green-refactor.
  7. Phase 4 · Review Convention check and verification pass.
  8. Phase 5 · Complete Creates a PR and cleans up the worktree.

See How It Works for a deeper explanation of each phase, or Configuration to customize behavior.