feat: Add polecat workflow quality levels (basic/shiny/chrome)
Three pre-baked polecat workflows with increasing rigor: - mol-polecat-basic: 3 steps, for trivial P4 fixes - mol-polecat-shiny: 6 steps, standard quality with design/review - mol-polecat-chrome: 16 steps, max rigor with strategic context reading, triple code review, and decomposed implementation phases Added --quality (-q) flag to gt sling as shorthand: gt sling gt-abc gastown -q basic # quick fix gt sling gt-abc gastown -q shiny # standard gt sling gt-abc gastown -q chrome # max rigor Chrome explicitly requires reading ~/gt/docs/hop/CONTEXT.md and ~/gt/docs/PRIMING.md before design begins. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
89
.beads/formulas/mol-polecat-basic.formula.toml
Normal file
89
.beads/formulas/mol-polecat-basic.formula.toml
Normal file
@@ -0,0 +1,89 @@
|
||||
description = """
|
||||
Minimal polecat workflow for trivial fixes.
|
||||
|
||||
Use this for P4 backlog items, typo fixes, and simple changes that don't
|
||||
require design review or extensive testing. Just get it done.
|
||||
|
||||
## When to Use
|
||||
- Typo fixes
|
||||
- Simple config changes
|
||||
- Obvious bug fixes
|
||||
- Documentation updates
|
||||
- P4 priority items
|
||||
|
||||
## When NOT to Use
|
||||
- New features (use shiny or chrome)
|
||||
- Security-related changes (use chrome)
|
||||
- Complex refactoring (use shiny)
|
||||
- Anything P1 or P0 (use chrome)
|
||||
"""
|
||||
formula = "mol-polecat-basic"
|
||||
type = "workflow"
|
||||
version = 1
|
||||
|
||||
[[steps]]
|
||||
id = "preflight"
|
||||
title = "Quick preflight check"
|
||||
description = """
|
||||
Fast initialization - just enough to start working.
|
||||
|
||||
```bash
|
||||
gt prime # Load context
|
||||
gt mol status # Check your hook
|
||||
bd show {{issue}} # Understand the task
|
||||
```
|
||||
|
||||
Verify you understand what needs to be done. If unclear, ask.
|
||||
|
||||
**Exit criteria:** You know what to do."""
|
||||
|
||||
[[steps]]
|
||||
id = "implement"
|
||||
title = "Implement {{feature}}"
|
||||
needs = ["preflight"]
|
||||
description = """
|
||||
Just do it. Keep it simple.
|
||||
|
||||
1. Make the change
|
||||
2. Test it works locally
|
||||
3. Commit with clear message:
|
||||
|
||||
```bash
|
||||
git add <files>
|
||||
git commit -m "fix: <description> ({{issue}})"
|
||||
```
|
||||
|
||||
Don't overthink. Don't gold-plate. Don't scope-creep.
|
||||
|
||||
**Exit criteria:** Change implemented and committed."""
|
||||
|
||||
[[steps]]
|
||||
id = "postflight"
|
||||
title = "Submit and signal done"
|
||||
needs = ["implement"]
|
||||
description = """
|
||||
Push and signal completion.
|
||||
|
||||
```bash
|
||||
# Quick test
|
||||
go test ./... # Must pass
|
||||
|
||||
# Push
|
||||
git push -u origin $(git branch --show-current)
|
||||
|
||||
# Close issue
|
||||
bd close {{issue}} --reason "Fixed"
|
||||
bd sync
|
||||
|
||||
# Signal done
|
||||
gt done
|
||||
```
|
||||
|
||||
**Exit criteria:** Witness takes over from here."""
|
||||
|
||||
[vars]
|
||||
[vars.issue]
|
||||
description = "The issue ID assigned to this polecat"
|
||||
required = true
|
||||
[vars.feature]
|
||||
description = "Brief description of what's being fixed"
|
||||
Reference in New Issue
Block a user