fellowship

Plugin fellowship in justinjdev/fellowship. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• openspec-apply-change

  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

• openspec-archive-change

  Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

• openspec-bulk-archive-change

  Archive multiple completed changes at once. Use when archiving several parallel changes.

• openspec-continue-change

  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

• openspec-explore

  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

• openspec-ff-change

  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

• openspec-new-change

  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

• openspec-onboard

  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

• openspec-sync-specs

  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

• openspec-verify-change

  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

• council

  Invoke when the user runs /council or from /scout. Quest inlines this orientation as its Research step 2 and does not call it. Loads focused, task-relevant context by reading CLAUDE.md, scanning for related files, and producing a structured Session Context block.

• fellowship

  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.

• gather-lore

  Invoke only when the user runs /gather-lore. Quest inlines this pattern extraction as its Research step 4 and does not call it. Studies the reference files CLAUDE.md documents to extract conventions before code is written, preventing wrong-approach review rework.

• lembas

  Use between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.

• lorebook

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

• missive

  Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.

• quest

  Use for multi-file or multi-step changes that need research and a plan — not single-file fixes under ~50 lines that follow an existing pattern (see Escape Hatch below). Runs the Research → Plan → Implement → Review lifecycle with a hard gate leaving each of the first three phases and context compact

• retro

  Invoke after a fellowship disbands, or when the user explicitly asks for a retrospective. Collects gate history, palantir alerts, and quest metrics to surface patterns and interactively recommend configuration improvements.

• scout

  Research & analysis workflow. Investigates questions, gathers findings, optionally validates with a fresh subagent. Produces a report — no code, no PRs, no commits. Use standalone or as a fellowship teammate.

• warden

  Use before opening a PR from a quest, once the code is written. Simulates a strict code reviewer by comparing changes against reference files and documented conventions, catching convention feedback before your human reviewer does.