beads-workflow

Name: beads-workflow
Author: Dicklesworthstone

87installs13forks

How to install beads-workflow?

dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow

$npx -y skills add Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill beads-workflow

Installs into the current project.

Summary

Converting markdown plans into beads (tasks with dependencies) and polishing them until they're implementation-ready. The bridge between planning and agent swarm execution. Includes exact prompts used.

Files · 1

View on GitHub

SKILL.md

1	# Beads Workflow — From Plan to Actionable Tasks
2
3	> Core Principle: "Check your beads N times, implement once" — where N is as many as you can stomach.
4	>
5	> Beads are so detailed and polished that you can mechanically unleash a big swarm of agents to implement them, and it will come out just about perfectly.
6
7	---
8
9	## What Are Beads?
10
11	Beads are epics/tasks/subtasks with dependency structure, optimized for AI coding agents. Think of them as Jira or Linear, but designed for machines.
12
13	Key properties:
14	- Self-contained — Never need to refer back to the original markdown plan
15	- Self-documenting — Include background, reasoning, justifications, considerations
16	- Dependency-aware — Explicit structure of what blocks what
17	- Rich descriptions — Long markdown comments, not short bullet points
18
19	---
20
21	## Why Beads Work
22
23	```
24	┌─────────────────────────────────────────────────────────────┐
25	│ MARKDOWN PLAN (~3,500 lines) │
26	│ └─► Fits in context window │
27	│ └─► Models reason about entire system at once │
28	├─────────────────────────────────────────────────────────────┤
29	│ ↓ CONVERT TO BEADS ↓ │
30	├─────────────────────────────────────────────────────────────┤
31	│ BEADS (distributed tasks) │
32	│ └─► Each bead is self-contained │
33	│ └─► Any agent can pick up any bead │
34	│ └─► BV (Beads Viewer) handles prioritization │
35	│ └─► Agent Mail handles coordination │
36	└─────────────────────────────────────────────────────────────┘
37	```
38
39	---
40
41	## Converting Plans to Beads
42
43	### THE EXACT PROMPT — Plan to Beads Conversion (Claude Code + Opus 4.5)
44
45	```
46	OK so now read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md; please take ALL of that and elaborate on it and use it to create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.). The beads should be so detailed that we never need to consult back to the original markdown plan document. Remember to ONLY use the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.
47	```
48
49	Note: Replace `PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md` with your actual plan filename.
50
51	### Alternative Shorter Version
52
53	```
54	OK so please take ALL of that and elaborate on it more and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.) Use only the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.
55	```
56
57	### What This Creates
58
59	- Tasks and subtasks with clear scope
60	- Dependency links (what must complete before what)
61	- Detailed descriptions with:
62	- Background context
63	- Reasoning and justification
64	- Technical considerations
65	- How it serves project goals
66
67	---
68
69	## Polishing Beads
70
71	### Why Polish?
72
73	Even after initial conversion, beads continue to improve with review. You get incremental improvements even at round 6+.
74
75	### THE EXACT PROMPT — Polish Beads (Full Version)
76
77	```
78	Reread AGENTS dot md so it's still fresh in your mind. Then read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md . Use ultrathink. Check over each bead super carefully-- are you sure it makes sense? Is it optimal? Could we change anything to make the system work better for users? If so, revise the beads. It's a lot easier and faster to operate in "plan space" before we start implementing these things! DO NOT OVERSIMPLIFY THINGS! DO NOT LOSE ANY FEATURES OR FUNCTIONALITY! Also make sure that as part of the beads we include comprehensive unit tests and e2e test scripts with great, detailed logging so we can be sure that everything is working perfectly after implementation. It's critical that EVERYTHING from the markdown plan be embedded into the beads so that we never need to refer back to the markdown plan and we don't lose any important context or ideas or insights into the new features planned and why we are making them.
79	```
80
81	###

People who liked this also viewed

6 picks

Type

beads-workflow

87installs13forks

View on GitHub

How to install beads-workflow?

dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow

$npx -y skills add Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill beads-workflow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Beads Workflow — From Plan to Actionable Tasks
2
3	> Core Principle: "Check your beads N times, implement once" — where N is as many as you can stomach.
4	>
5	> Beads are so detailed and polished that you can mechanically unleash a big swarm of agents to implement them, and it will come out just about perfectly.
6
7	---
8
9	## What Are Beads?
10
11	Beads are epics/tasks/subtasks with dependency structure, optimized for AI coding agents. Think of them as Jira or Linear, but designed for machines.
12
13	Key properties:
14	- Self-contained — Never need to refer back to the original markdown plan
15	- Self-documenting — Include background, reasoning, justifications, considerations
16	- Dependency-aware — Explicit structure of what blocks what
17	- Rich descriptions — Long markdown comments, not short bullet points
18
19	---
20
21	## Why Beads Work
22
23	```
24	┌─────────────────────────────────────────────────────────────┐
25	│ MARKDOWN PLAN (~3,500 lines) │
26	│ └─► Fits in context window │
27	│ └─► Models reason about entire system at once │
28	├─────────────────────────────────────────────────────────────┤
29	│ ↓ CONVERT TO BEADS ↓ │
30	├─────────────────────────────────────────────────────────────┤
31	│ BEADS (distributed tasks) │
32	│ └─► Each bead is self-contained │
33	│ └─► Any agent can pick up any bead │
34	│ └─► BV (Beads Viewer) handles prioritization │
35	│ └─► Agent Mail handles coordination │
36	└─────────────────────────────────────────────────────────────┘
37	```
38
39	---
40
41	## Converting Plans to Beads
42
43	### THE EXACT PROMPT — Plan to Beads Conversion (Claude Code + Opus 4.5)
44
45	```
46	OK so now read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md; please take ALL of that and elaborate on it and use it to create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.). The beads should be so detailed that we never need to consult back to the original markdown plan document. Remember to ONLY use the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.
47	```
48
49	Note: Replace `PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md` with your actual plan filename.
50
51	### Alternative Shorter Version
52
53	```
54	OK so please take ALL of that and elaborate on it more and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.) Use only the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.
55	```
56
57	### What This Creates
58
59	- Tasks and subtasks with clear scope
60	- Dependency links (what must complete before what)
61	- Detailed descriptions with:
62	- Background context
63	- Reasoning and justification
64	- Technical considerations
65	- How it serves project goals
66
67	---
68
69	## Polishing Beads
70
71	### Why Polish?
72
73	Even after initial conversion, beads continue to improve with review. You get incremental improvements even at round 6+.
74
75	### THE EXACT PROMPT — Polish Beads (Full Version)
76
77	```
78	Reread AGENTS dot md so it's still fresh in your mind. Then read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md . Use ultrathink. Check over each bead super carefully-- are you sure it makes sense? Is it optimal? Could we change anything to make the system work better for users? If so, revise the beads. It's a lot easier and faster to operate in "plan space" before we start implementing these things! DO NOT OVERSIMPLIFY THINGS! DO NOT LOSE ANY FEATURES OR FUNCTIONALITY! Also make sure that as part of the beads we include comprehensive unit tests and e2e test scripts with great, detailed logging so we can be sure that everything is working perfectly after implementation. It's critical that EVERYTHING from the markdown plan be embedded into the beads so that we never need to refer back to the markdown plan and we don't lose any important context or ideas or insights into the new features planned and why we are making them.
79	```
80
81	###

People who liked this also viewed

6 picks

Type