6730fce9b1
Replace tool-specific setup commands with a generic recipe-based system. New tools become config entries, not code changes. Changes: - Add internal/recipes/ package with Recipe type and built-in recipes - Add --list flag to show available recipes - Add --print flag to output template to stdout - Add -o flag to write template to arbitrary path - Add --add flag to save custom recipes to .beads/recipes.toml - Add built-in recipes: windsurf, cody, kilocode (new) - Legacy recipes (cursor, claude, gemini, aider, factory) continue to work The recipe system enables: - Adding new tool support without code changes - User-defined recipes in .beads/recipes.toml - Shared template across all file-based integrations 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> Executed-By: beads/crew/dave Rig: beads Role: crew
60 lines
2.0 KiB
Go
60 lines
2.0 KiB
Go
package recipes
|
|
|
|
// Template is the universal beads workflow template.
|
|
// This content is written to all file-based recipes.
|
|
const Template = `# Beads Issue Tracking
|
|
|
|
This project uses [Beads (bd)](https://github.com/steveyegge/beads) for issue tracking.
|
|
|
|
## Core Rules
|
|
|
|
- Track ALL work in bd (never use markdown TODOs or comment-based task lists)
|
|
- Use ` + "`bd ready`" + ` to find available work
|
|
- Use ` + "`bd create`" + ` to track new issues/tasks/bugs
|
|
- Use ` + "`bd sync`" + ` at end of session to sync with git remote
|
|
- Git hooks auto-sync on commit/merge
|
|
|
|
## Quick Reference
|
|
|
|
` + "```bash" + `
|
|
bd prime # Load complete workflow context
|
|
bd ready # Show issues ready to work (no blockers)
|
|
bd list --status=open # List all open issues
|
|
bd create --title="..." --type=task # Create new issue
|
|
bd update <id> --status=in_progress # Claim work
|
|
bd close <id> # Mark complete
|
|
bd dep add <issue> <depends-on> # Add dependency
|
|
bd sync # Sync with git remote
|
|
` + "```" + `
|
|
|
|
## Workflow
|
|
|
|
1. Check for ready work: ` + "`bd ready`" + `
|
|
2. Claim an issue: ` + "`bd update <id> --status=in_progress`" + `
|
|
3. Do the work
|
|
4. Mark complete: ` + "`bd close <id>`" + `
|
|
5. Sync: ` + "`bd sync`" + ` (or let git hooks handle it)
|
|
|
|
## Issue Types
|
|
|
|
- ` + "`bug`" + ` - Something broken
|
|
- ` + "`feature`" + ` - New functionality
|
|
- ` + "`task`" + ` - Work item (tests, docs, refactoring)
|
|
- ` + "`epic`" + ` - Large feature with subtasks
|
|
- ` + "`chore`" + ` - Maintenance (dependencies, tooling)
|
|
|
|
## Priorities
|
|
|
|
- ` + "`0`" + ` - Critical (security, data loss, broken builds)
|
|
- ` + "`1`" + ` - High (major features, important bugs)
|
|
- ` + "`2`" + ` - Medium (default, nice-to-have)
|
|
- ` + "`3`" + ` - Low (polish, optimization)
|
|
- ` + "`4`" + ` - Backlog (future ideas)
|
|
|
|
## Context Loading
|
|
|
|
Run ` + "`bd prime`" + ` to get complete workflow documentation in AI-optimized format.
|
|
|
|
For detailed docs: see AGENTS.md, QUICKSTART.md, or run ` + "`bd --help`" + `
|
|
`
|