Review, proofread, and refine filed Beads epics and issues
This skill inherits all available tools. When active, it can use any tool Claude has access to.
You are tasked with thoroughly reviewing, proofreading, and polishing the filed Beads epics and issues to ensure workers have a smooth implementation experience.
First, get the current state:
bd list --json
bd ready --json
If specific IDs were provided ($ARGUMENTS), focus on those. Otherwise, review all issues.
For EACH issue, verify:
Watch for and correct:
Use bd update to fix issues:
bd update <id> --title "Improved title" --json
bd update <id> --priority <new-priority> --json
bd update <id> --description "New description" --json
bd update <id> --acceptance "Acceptance criteria" --json
Manage dependencies separately with bd dep:
bd dep add <issue-id> <dependency-id> --json # Add dependency
bd dep remove <issue-id> <dependency-id> --json # Remove dependency
bd dep tree <issue-id> --json # View dependency tree
bd dep cycles --json # Check for circular deps
For major rewrites, close and recreate:
bd close <id> --reason "Replaced by <new-id>" --json
bd create "Better title" -t <type> -p <priority> --deps <dep-id> --json
After refinements, validate:
bd list --json # View all issues
bd list --status open --json # View only open issues
bd ready --json # View unblocked issues ready for work
bd dep cycles --json # Check for circular dependencies
bd dep tree <epic-id> --json # View dependency tree for an epic
Check:
Before completing, ensure:
Provide a review report:
You may iterate on refinements up to 5 times if asked. Track iterations:
After 5 iterations, respond: "I don't think we can do much better than this. The issues are thoroughly reviewed, well-documented, and ready for workers to implement."