aspiers/ai-config / .agents/skills/bc
bc
VerifiedCreates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
SKILL.md
View on GitHub---
name: bc
description: >-
Creates a Beads issue for a described problem or piece of work without
doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to
file, log, or record a bead for something. To also carry out the work, use
the `bx` skill instead.
---
# Create a bead for the described issue
Do NOT explore the codebase, launch subagents, or do any other work before
creating the bead issue.
1. Load the `beads-best-practices` skill and follow it when writing the bead.
2. Infer the issue type from context, using "Choose the Issue Type" in
`beads-best-practices`: `bug`, `feature`, `chore`, `spike`, `decision`
and so on. Fall back to `task`.
3. Check for an existing bead. This is the only step allowed before
creating one. Run one quick search per key title word, for example:
`bd search "<word>" --status open,in_progress,blocked,deferred`
If a result plainly covers the same work, do not create a new bead.
Report the existing one with its ID and title, add a comment to it if
the request carries new detail, and skip to the last step.
4. Otherwise create the bead:
`bd create --title="<title>" --description="<description>" --type=<type>`
Use "Investigating..." as the description if the full scope is unclear.
5. If investigation is needed, do it NOW, then update the bead:
`bd update <id> --title="<better title>" \
--description="<final description>"`
6. Report the created issue ID and title back to the user.
7. If you were previously in the middle of working on something which this
request interrupted, resume that immediately without asking.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |