using-beads-bv
Coordinate dependency-aware task planning
Manage complex multi-agent workflows with dependency tracking. Beads provides a lightweight issue database where bd CLI handles task management and bv delivers graph metrics for execution planning with deterministic robot flags.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"using-beads-bv" ์ฌ์ฉ ์ค์ ๋๋ค. Show me all issues ready to work
์์ ๊ฒฐ๊ณผ:
- Ready issues (no blockers):
- โข agent-relay-456 - Implement auth middleware (P1)
- โข agent-relay-458 - Add rate limiting (P2)
- โข agent-relay-459 - Write integration tests (P2)
- ย
- These items can be worked on immediately.
"using-beads-bv" ์ฌ์ฉ ์ค์ ๋๋ค. What should I work on first based on priorities
์์ ๊ฒฐ๊ณผ:
- Priority order for current session:
- 1. bd-123 (P0) - Database migration blocker
- 2. bd-124 (P0) - API security fix
- 3. bd-125 (P1) - Performance optimization
- ย
- P0 items are blocking other work.
๋ณด์ ๊ฐ์ฌ
์์ Pure documentation skill containing only markdown guidance for using beads/bv CLI tools. No executable code, no network calls, no file system access, no command execution. All 61 static findings are false positives from misinterpreting markdown command examples as executable backtick syntax.
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (45)
๐ ๋คํธ์ํฌ ์ ๊ทผ (2)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Coordinate agent task dependencies
Plan and track work across multiple AI agents with clear dependency chains and parallel execution paths
Manage sprint execution metrics
Use bv graph insights to identify critical path items and optimize team workflow sequencing
Track priority work allocation
Apply P0-P4 numeric priorities and visualize what work items unblock other deliverables
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Show me all issues ready to work using beads
Generate an execution plan for the current sprint using bv
Create a new issue for feature X and another for its tests, then make the tests depend on the feature
Show me the project graph metrics including critical path and any cycles
๋ชจ๋ฒ ์ฌ๋ก
- Always use `--robot-*` flags with bv to avoid blocking TUI sessions
- Use P0-P4 numeric priorities instead of high/medium/low labels
- Include beads issue IDs (e.g., bd-123) in all commit messages for traceability
- Run `bd sync` before ending any session to commit changes
ํผํ๊ธฐ
- Using bv without robot flags and getting stuck in interactive TUI
- Managing tasks in markdown files instead of beads database
- Missing issue IDs in commit messages breaks traceability
- Using high/medium/low priority labels instead of P0-P4 format
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What are the P0-P4 priority levels?
How do I avoid blocking in bv?
Can I use this for single-agent tasks?
How do I create dependent issues?
What data does this skill access?
How is this different from TodoWrite?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md