Analyze work and create follow-up beads issues if needed.
Analyzes completed work and creates follow-up issues for discovered tasks.
/plugin marketplace add GGPrompts/TabzBeads/plugin install conductor@tabz-beadsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Analyze completed work and create follow-up beads issues for discovered work. This is a standalone atomic command.
/conductor:bdw-create-followups
/conductor:bdw-create-followups <parent-issue-id>
Always run after completing a task to capture:
echo "=== Create Follow-ups ==="
# Check what was done
echo "Recent commit:"
git log -1 --oneline
echo ""
echo "Files changed:"
git diff HEAD~1 --name-only 2>/dev/null || git diff --cached --name-only
echo ""
| Task Type | Follow-up Action |
|---|---|
| Research/Spike | Create implementation issues from findings |
| Feature | Create issues for edge cases, TODOs, enhancements |
| Bug fix | Create issues if root cause reveals other problems |
| Refactor | Create issues for remaining cleanup |
# Find TODOs in changed files
echo "Checking for TODOs in changes..."
git diff HEAD~1 --name-only 2>/dev/null | xargs grep -n "TODO\|FIXME\|HACK" 2>/dev/null || echo "No TODOs found"
echo ""
discovered-from LinksIMPORTANT: Always link new issues with discovered-from dependency to maintain context chain.
For research tasks:
# Example: Research completed, create implementation issues
NEW_ISSUE=$(bd create --title "Implement <finding from research>" \
--type feature \
--priority 2 \
--description "Based on research in $PARENT_ISSUE. See docs/research/..." \
--json | jq -r '.id')
# Link with discovered-from dependency
bd dep add "$NEW_ISSUE" discovered-from "$PARENT_ISSUE"
echo "Created: $NEW_ISSUE (discovered from $PARENT_ISSUE)"
For discovered edge cases:
NEW_ISSUE=$(bd create --title "Handle edge case: <description>" \
--type bug \
--priority 3 \
--description "Discovered during $PARENT_ISSUE implementation" \
--json | jq -r '.id')
bd dep add "$NEW_ISSUE" discovered-from "$PARENT_ISSUE"
For TODOs:
NEW_ISSUE=$(bd create --title "Address TODO: <description>" \
--type chore \
--priority 4 \
--description "TODO found in <file>:<line> during $PARENT_ISSUE" \
--json | jq -r '.id')
bd dep add "$NEW_ISSUE" discovered-from "$PARENT_ISSUE"
Why discovered-from: This creates a traceable chain showing where work originated. When reviewing the backlog later, you can see which issues spawned other issues.
echo "=== Follow-up Summary ==="
echo ""
# List created issues or "none"
{
"created": ["TabzChrome-abc", "TabzChrome-def"],
"skipped": false
}
Or if no follow-ups needed:
{
"created": [],
"skipped": true,
"reason": "no follow-up work identified"
}
DO create issues for:
DON'T create issues for:
If unsure whether to create follow-ups:
AskUserQuestion: "Should I create follow-up issues for: [list items]?"
/conductor:bdw-commit-changes - Run after commit/conductor:bdw-update-docs - Run before or after/conductor:bdw-close-issue - Run before closing/conductor:bdw-worker-done - Full pipeline that includes thisCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.