From bounty-board
Show the wanted-poster bounty board — this repo's TODO/FIXME/HACK debt priced as aging XP bounties
How this skill is triggered — by the user, by Claude, or both
Slash command
/bounty-board:boardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../bounty-board.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/bounty-board.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../bounty-board.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/bounty-board.js" --render
The card above is this repository's open bounties — each TODO/FIXME/HACK/skip/lint-suppression
priced as a wanted-poster bounty whose XP scales with its git-blame age (older debt = fatter
bounty). It is produced by the bounty-board hook, which scans the repo on demand.
Briefly call out the 1–3 fattest bounties and, for each, name the file:line and what it would take to genuinely clear it (resolve the debt, not just delete the marker). Keep it short; do not re-run any commands.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub karanb192/claude-code-hooks --plugin bounty-board