plan-beads

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Plan Beads

Run a planner-only Beads session.

## Steps

1. If the current repo is not initialized for Beads, stop and tell the user to run the template bootstrap script or at minimum `bd init --prefix <prefix>` plus the repo scaffolding steps.
2. If the user provided a planning topic in the current request, treat it as the planning topic.
3. Otherwise, use the current conversation topic.
4. If the topic is still unclear, ask clarifying questions before planning.
5. Use `brainstorming` when the problem is still fuzzy or underexplored.
6. If `brainstorming` leaves material factual uncertainty that affects architecture, feasibility, integration points, or bead quality, use `planner-research` before finalizing the plan.
7. Produce or confirm an execution plan using the discussion and any planner research findings.
8. Keep moving autonomously through normal design uncertainty. Ask the user only when a missing decision is genuinely product-defining, preference-sensitive, or too risky to choose on the user's behalf.
9. Once the plan is settled and ready to translate, stop once to brief the user on the final recommended plan and ask for confirmation to create Beads.
10. After confirmation, use `beads-planner` to create or update the beads from the settled plan. If the settled plan lives in a file outside the repo (e.g. `~/.claude/plans/...`, `/tmp/...`, or anywhere not under the current working directory), tell `beads-planner` to copy it into `docs/plans/<slug>.md` and inline its content into the bead notes so teammates on other machines can read it through Dolt-synced bead state.
11. If the plan is intended for epic-scoped autonomous execution, immediately run `validate-beads` in the same planner session.
12. If validation fails, tighten the beads, dependencies, or execution contract, then re-run `validate-beads` before ending the session.
13. Stop after the beads are created and either validated for autonomous execution or explicitly marked as manual-only.

## Hard Rules

- Planner session only.
- Do not claim beads.
- Do not start implementation.
- Do not create a parallel planning tracker or second source of truth outside the settled plan/spec plus Beads.
- Do not invoke `beads-claim`, `writing-plans`, repo-local `build-and-test`, or `beads-close`.
- Keep Beads as the source of truth for task state.
- In the normal flow, the explicit user confirmation gate is the bead-creation handoff right before `beads-planner`.

## Final Output

- Summarize the settled plan briefly.
- List the created or updated beads and important dependencies.
- Say whether the epic passed `validate-beads` or why it is manual-only.
- End by telling the user that executor work should start in a separate session.

From jsiovn/agent-workflow-beads, MIT.

More from jsiovn/agent-workflow-beads