scribe

Forge Template — Create Quest Templates

Overview

Creates quest templates that encode project-specific knowledge — conventions Claude wouldn't know, domain rules that aren't in code, team workflows that matter. Templates are worthless if they contain generic advice ("write tests," "follow patterns"). They're valuable when they capture things like "payments changes require idempotency tests" or "all API routes need OpenAPI spec updates."

When to Use

• Setting up fellowship for a new project
• After noticing quests repeatedly miss a project convention
• When a category of work has domain-specific requirements

Process

1. Gather Context

Ask the user:

• What kind of quest is this template for? (e.g., "API endpoint," "database migration," "UI component," not generic categories like "bugfix")
• What do quests of this type consistently get wrong or miss? This is the core value — things Claude wouldn't infer from code alone.
• Are there project-specific gates or checks? (e.g., "security review required for auth changes," "design approval before UI work")

Then investigate the codebase:

• Read CLAUDE.md, CONTRIBUTING.md, and any project conventions docs
• Look at recent PRs or commits of the same type for patterns
• Identify project-specific tooling, scripts, or workflows (e.g., custom test runners, migration generators, code generators)

2. Draft the Template

Write a template with YAML frontmatter and phase-specific sections. Every line of guidance must be specific to this project — if the advice would apply to any codebase, delete it.

Format:

---
name: {name}
description: {one-line description}
keywords: [{comma-separated trigger words}]
---

## Research Guidance
{project-specific research steps}

## Plan Guidance
{project-specific planning constraints}

## Implement Guidance
{project-specific implementation rules}

## Review Guidance
{project-specific review checklist}

Rules for good templates:

• Every bullet must reference something concrete: a file path, a tool, a convention, a domain rule
• If you can't point to a specific project artifact or convention, the bullet doesn't belong
• Keywords should match how the user naturally describes this kind of work
• Fewer, sharper bullets beat comprehensive generic lists