schlenks/plan2beads
skills/plan2beads/SKILL.md
Use when converting a Superpowers-BD implementation plan or Shortcut story into a beads epic with dependency-aware child tasks
$ install --global
skillsauthnpx skillsauth add schlenks/superpowers-bd plan2beadsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 18, 2026, 5:15 AM192.8s3 files scanned
SKILL.md
- name:
- plan2beads
- description:
- Use when converting a Superpowers-BD implementation plan or Shortcut story into a beads epic with dependency-aware child tasks
- effort:
- medium
Plan to Beads
Convert a written plan into beads work: one parent epic, dependency-aware implementation tasks, and one final verification task.
Required Background
Load superpowers-bd:beads first. You need the bd CLI workflow, dependency semantics, and multiline body-file conventions before creating issues.
Quick Start
Read the plan file, create the epic and child issues with bd create, verify dependencies with bd ready/bd blocked, then report the new epic and next execution action.
Platform Routing
- Claude Code:
/superpowers-bd:plan2beads <plan-path | SC-1234 | 1234>loads the Claude command implementation at../../commands/plan2beads.md. - Codex: Follow
references/codex-plan2beads-flow.md. Treat this skill and that reference as the native workflow; do not route Codex through the Claude slash command.
Shared Rules
- Use
temp/*.mdbody files for multiline issue descriptions and comments. - Keep each child issue dependency-aware with clear
Depends on:,Complexity:, andFiles:sections from the source plan. - Verify the dependency shape with
bd ready,bd blocked, andbd show <epic-id>before handing off. - If the plan is incomplete or ambiguous, ask a concise question before creating issues.
Output Contract
End with the epic ID, created child task IDs, ready/blocked summary, and the exact next execution action. Proceed into subagent-driven-development after successful conversion unless the user explicitly asks for conversion-only.
Reference Files
references/codex-plan2beads-flow.md: Codex-native plan-to-beads conversion flow
Related Skills
schlenks/ad-hoc-code-review
development
VerifiedTrustedCommunity
Use when the user asks for /cr-style review of local changes, commits, a branch diff, or a GitHub PR outside subagent-driven development
2SKILL.mdUpdated May 16, 2026
schlenks/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec or requirements for a multi-step task, before touching code
2SKILL.mdUpdated May 16, 2026
schlenks/using-superpowers
tools
VerifiedTrustedCommunity
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
2SKILL.mdUpdated May 16, 2026
schlenks/subagent-driven-development
development
VerifiedTrustedCommunity
Use when user says "execute epic [id]" or when executing beads epics with parallel subagents in the current session
2SKILL.mdUpdated May 16, 2026