Agent skill

Plan Release

by danielvm-git in danielvm-git/bigpowers

RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines.

MITAuto-check passedProduct & Project Management

Install Plan Release

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-release .claude/skills/plan-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .claude/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-release .agents/skills/plan-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .agents/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-release .cursor/skills/plan-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .cursor/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/plan-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-release .gemini/skills/plan-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .gemini/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-release .github/skills/plan-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .github/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill plan-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers plan-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-release .opencode/skills/plan-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "plan-release" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/plan-release into .opencode/skills/plan-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: plan-release
GitHub stars: 257
Token cost: ~1.5k tokens
SKILL.md length: 491 words
Files: 1
Skills in repo: 39
Repo updated: Sep 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines.

Works in 10 steps: Draft epics and stories → Write acceptance criteria (Gherkin) → Write tasks with verify commands → …
Wants a versioned release index of epics
SKILL.md covers Outputs, Epic Capsule Structure and Process
Calls bash and gh

What it does

Plan Release is an agent skill from danielvm-git/bigpowers. RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories and Feature launches and release readiness. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

Wants a versioned release index of epics
Tasks that involve User stories
Tasks that involve Feature launches and release readiness

Example prompts

“/plan-release”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

Draft epics and stories
Write acceptance criteria (Gherkin)
Write tasks with verify commands
Save specs/release-plan.yaml
Save epic manifest (epic.yaml)
Save story specs (countable-story-format .md)
Save decoupled task files (-tasks.yaml)
Sync execution status
Snapshot on planning close (optional)
Suggest next steps

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plan Release loads about 1.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 491 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~78
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 491 words, ~1,503 tokens.

Download SKILL.mdSave it as .claude/skills/plan-release/SKILL.md (or your agent's skills folder).

name: plan-release
description: RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.
model: sonnet
effort: standard

Plan Release

HARD GATE — Do NOT run this skill unless elaborate-spec has produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, run elaborate-spec first. HARD GATE — specs/product/SCOPE_LATEST.yaml (or legacy specs/product/SCOPE_LATEST.yaml) must exist. If missing, run scope-work first.

Synthesize the conversation context into specs/release-plan.yaml (index) and shard detail under specs/epics/. No new interview — only clarify if something is genuinely ambiguous.

Outputs

File	Content
`specs/release-plan.yaml`	`release.version`, semver bump hint, WSJF-ordered epic list with `id`, `capsule_dir`, `wsjf`, `bcps` — no story status
`specs/epics/eNN-<slug>/epic.yaml`	Epic manifest: `id`, `title`, `wsjf`, `total_bcps`, `status`, `stories[]` list
`specs/epics/eNN-<slug>/eNNsYY-<slug>.md`	Story spec in countable-story-format.md with 20 sections and Gherkin acceptance criteria
`specs/epics/eNN-<slug>/eNNsYY-tasks.yaml`	Decoupled task checklist with `verify:` commands per task
`specs/execution-status.yaml`	Flat key-value store for story status (`eNNsYY: todo`)

Epic Capsule Structure

All epics use capsule directories (no flat/folder distinction):

specs/epics/e01-auth-system/
├── epic.yaml              # Epic manifest
├── adr/                   # Epic-local ADRs (created lazily)
├── e01s01-login.md        # Story spec (countable-story-format)
├── e01s01-tasks.yaml      # Decoupled task checklist
├── e01s02-jwt.md          # Story spec
└── e01s02-tasks.yaml      # Decoupled task checklist

Rationale: Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec .md from execution -tasks.yaml (C1).

Process

1. Draft epics and stories

From the conversation context, define:

Epics — e01, e02, … (stable IDs; WSJF order in release-plan.yaml only)
Stories — e01s01, e01s02, … with Gherkin acceptance criteria

WSJF-sort epics: score = (Business Value + Time Criticality + Risk Reduction) / Job Size. Highest score first.

Security risk boost: If an epic's specs/security/epics/<id>/THREAT_MODEL.md identifies HIGH or CRITICAL risk, add +2 to the WSJF numerator (BV + TC + RR + 2) to reflect the urgency of addressing security concerns before they ship. Document the boost in the epic's note field in release-plan.yaml.

2. Write acceptance criteria (Gherkin)

For each story, write at least one happy-path and one edge-case scenario (countable format §17 if maturity ≥ 3).

3. Write tasks with verify commands

Every task must have a verify: command. No verify command = not a task.

Show full SKILL.md (202 more words)Show less

4. Save specs/release-plan.yaml

Do NOT hand-track the real version. semantic-release decides it at merge. version here is a non-authoritative mirror/label only — read the real number with gh release view. Set bump_hint (the expectation), not a number you intend to enforce.

yaml

release:
  version: "2.29.0"         # mirror of next expected tag, NOT authoritative — gh release view wins
  codename: "Feature Name"
  status: planning          # planning | in_progress | released
  semantic_release: true
  bump_hint: minor          # patch | minor | major — CI decides at merge
epics:
  - id: e01
    title: Auth System
    wsjf: 4.5
    capsule_dir: epics/e01-auth-system
  - id: e02
    title: User Profile
    wsjf: 3.8
    capsule_dir: epics/e02-user-profile

5. Save epic manifest (`epic.yaml`)

Each epic capsule directory contains an epic.yaml manifest:

yaml

id: e01
title: Auth System
wsjf: 4.5
total_bcps: 8
status: in_progress
stories:
  - id: e01s01
    title: Login
    bcps: 3
    status: todo
    spec: e01s01-login.md
    tasks: e01s01-tasks.yaml
  - id: e01s02
    title: JWT Token Management
    bcps: 5
    status: todo
    spec: e01s02-jwt.md
    tasks: e01s02-tasks.yaml

6. Save story specs (countable-story-format .md)

Each story becomes a standalone .md file following countable-story-format.md. Minimum: maturity 3 (Countable) with all 20 sections present. Acceptance criteria in §17 use Gherkin scenarios.

7. Save decoupled task files (`-tasks.yaml`)

Each story has a decoupled -tasks.yaml with implementation steps:

yaml

story_id: e01s01
title: Login
status: todo
bcps: 3
tasks:
  - id: 1
    description: "Add login form component tests"
    verify: "npm test -- login-form.test.tsx"
    status: todo
  - id: 2
    description: "Implement login form with validation"
    verify: "npm test -- login-form.test.tsx"
    status: todo

HARD GATE — Every task MUST have a runnable verify: command. No verify: = not a task.

→ verify: bash scripts/validate-specs-yaml.sh

7b. Generate bug registry summary

Read specs/bugs/registry.yaml and add a bugs: section to release-plan.yaml with totals by status (fixed, deferred, wontfix, open): bugs: { total: N, fixed: N, deferred: N, wontfix: N, registry: specs/bugs/registry.yaml }.

8. Sync execution status

bash

bash scripts/sync-status-from-epics.sh

9. Snapshot on planning close (optional)

Copy to specs/product/snapshots/release-<version>/ when the user approves the plan.

10. Suggest next steps

Run assess-impact before plan-work for any story touching existing modules.
Run plan-work per story for detailed steps inside the epic shard.
Run change-request if a new requirement arrives mid-flight.

Files

Just SKILL.md in skills/plan-release of danielvm-git/bigpowers.

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Plan Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plan Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plan Release this skilldanielvm-git/bigpowers	257	—	~1.5k	Automated safety check: Pass	MIT	16 days ago
Refactor Design Reportpenwyp/ClaudePreference	136	—	~1.4k	Automated safety check: Pass	MIT	4 mo ago
Verification Gatesrohitg00/skillkit	1.5k	—	~1.7k	Automated safety check: Pass	Apache-2.0	4 mo ago
Pm Specsanqiufong/slides-from-anything	132	1 repos	~383	Automated safety check: Pass	Apache-2.0	yesterday
User Story Writerdeanpeters/Product-Manager-Skills	7.2k	2 repos	~2.9k	Automated safety check: Pass	Custom licence	1 mo ago
Ralph Tui Create Beadssubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Refactor Design Report
penwyp/ClaudePreference
Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…
136 GitHub stars~1.4k tokensUpdated 4 mo ago
Product & Project ManagementAuto-check passed
Verification Gates
rohitg00/skillkit
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding.
1.5k GitHub stars~1.7k tokensUpdated 4 mo ago
Product & Project ManagementAuto-check passed
Pm Spec
sanqiufong/slides-from-anything
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions.
132 GitHub starsUsed in 1 repo~383 tokens
Product & Project ManagementAuto-check passed
User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
7.2k GitHub starsUsed in 2 repos~2.9k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
28k GitHub starsUsed in 3 repos~3.2k tokens
Product & Project ManagementAuto-check passed

Questions about Plan Release

What does Plan Release do?

RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. Plan Release is an agent skill from danielvm-git/bigpowers.yaml with WSJF ordering and BCP baselines.

When should I use Plan Release?

Plan Release fits situations like: wants a versioned release index of epics; tasks that involve User stories; tasks that involve Feature launches and release readiness.

How do I install Plan Release in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill plan-release -a claude-code`. Or copy the skill folder (skills/plan-release in danielvm-git/bigpowers) into .claude/skills/plan-release in your project. Claude Code loads it when a task matches its description.

How do I install Plan Release in Codex?

Run `npx skills add danielvm-git/bigpowers --skill plan-release -a codex`. Or copy the skill folder (skills/plan-release in danielvm-git/bigpowers) into .agents/skills/plan-release in your project. Codex loads it when a task matches its description.

Can I use Plan Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill plan-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-release, .gemini/skills/plan-release, .github/skills/plan-release and .opencode/skills/plan-release in your project.

What does Plan Release need to run?

Going by SKILL.md and its folder, Plan Release needs the command-line tools its instructions call (bash and gh).

Does Plan Release access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Plan Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plan Release use?

Plan Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan Release use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan Release?

Skills that share tags, products or a category with Plan Release: Refactor Design Report (penwyp/ClaudePreference, 136 stars), Verification Gates (rohitg00/skillkit, 1.5k stars), Pm Spec (sanqiufong/slides-from-anything, 132 stars) and User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Release?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 257 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Plan Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plan Release

Outputs

Epic Capsule Structure

Process

1. Draft epics and stories

2. Write acceptance criteria (Gherkin)

3. Write tasks with verify commands

4. Save specs/release-plan.yaml

5. Save epic manifest (epic.yaml)

6. Save story specs (countable-story-format .md)

7. Save decoupled task files (-tasks.yaml)

7b. Generate bug registry summary

8. Sync execution status

9. Snapshot on planning close (optional)

10. Suggest next steps

Files

Compare with similar skills

Similar skills

More from danielvm-git/bigpowers

Related

Questions about Plan Release

5. Save epic manifest (`epic.yaml`)

7. Save decoupled task files (`-tasks.yaml`)