Learn-skills.dev raise

Name: raise
Author: NeverSight

Turns a Plan into dependency-aware beads issues. Use after 'plan' and before 'ship'. Use when the user has a completed Plan and wants to create trackable issues.

install

source · Clone the upstream repo

git clone https://github.com/NeverSight/learn-skills.dev

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/a1exmozz/skills/raise" ~/.claude/skills/neversight-learn-skills-dev-raise && rm -rf "$T"

manifest: data/skills-md/a1exmozz/skills/raise/SKILL.md

source content

Follow these steps in order, one at a time.

Input

Ask for the completed
```
Plan
```
.
After receiving the
```
Plan
```
, read the cheat sheet to understand how beads works.
Read the rules below for how we will convert the
```
Plan
```
into beads issues.

Rules

Convert each slice from 'Section 4: Slice Breakdown' into an epic.

br create "<Slice Name>" --type epic --priority <P> --labels "<context labels>"

Create child issues under each epic using
```
--parent <epic-id>
```
.
Each child issue must represent one smallest executable observable behavior that can be implemented and proved through the supported entry points.
Write each child issue description using the issue template.
Order child issues so the simplest happy-path behaviour comes first.
Child issues must be suitable for TDD red-green-refactor execution.
Add blocking dependencies with:
```
br dep add <blocked-id> <blocking-id>
```
Use 'Section 5: Delivery Sequence Summary' to add dependencies between epics in execution order.
Use labels to encode bounded context and issue category.

Output

Turn the
```
Plan
```
into beads issues starting with:

cd my-project
br init

After turning the entire plan into beads issues tell the user to proceed to the 'ship' skill.