Skill

manage

Use when you need to close, reopen, defer, or verify a filed issue — 'close this issue', 'reopen that bug', 'defer this to later', 'is this actually done'.

From dp-cab

Install

Run in your terminal

npx claudepluginhub raisedadead/dotplugins --plugin dp-cab

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/manage-protocol.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

dp-cab:manage -- Issue Lifecycle Management

Read ${CLAUDE_SKILL_DIR}/references/manage-protocol.md for full protocol details.

Pre-check

bash -c '
source ${CLAUDE_PLUGIN_ROOT}/lib/dp-beads.sh
if ! command -v bd >/dev/null 2>&1; then echo "NO_BD"; exit 0; fi
if ! test -d .beads; then echo "NO_DB"; exit 0; fi
echo "OK"
'

If NO_BD: "bd CLI not found. Install beads to use /dp-cab:manage." and STOP. If NO_DB: "No beads database found." and STOP.

Parse Arguments

If no action is provided, present this menu:

What would you like to do?

Close an issue

Reopen an issue

Defer an issue

Verify acceptance criteria

Audit for ghost-closes

Wait for the user to choose before proceeding.

Ownership Check

Before any mutation (close, reopen, defer), read the target issue's labels:

bash -c 'source ${CLAUDE_PLUGIN_ROOT}/lib/dp-beads.sh && dp_beads_show "[ISSUE_ID]"'

Check the labels in the output:

If dp-cto:running, dp-cto:planning, or dp-cto:reviewing: show "This item has {label} -- it may be actively worked. Continue?" and wait for confirmation.
If dp-cto:agent-spawning: show "Agent dispatched on this item. Continue?" and wait for confirmation.
If no dp-cto labels: proceed normally.

Dispatch

For close as completed: dispatch the triager agent to verify acceptance criteria against the codebase before closing. Do not close without verified criteria.

For all other actions (close with other reasons, reopen, defer, audit): execute directly using beads wrapper functions per the protocol in references/manage-protocol.md.

Post-action

Report the result to the user:

{issue-id}: {action} -- {result}
  Reason: {reason}
  Evidence: {file:line or bd output}

NEVER

NEVER close as completed without acceptance criteria verification
NEVER mutate an issue without the ownership check
NEVER auto-select from the menu -- wait for user choice
NEVER modify code files -- this skill manages beads state only
NEVER call bd directly -- always use wrapper functions via bash -c 'source ${CLAUDE_PLUGIN_ROOT}/lib/dp-beads.sh && ...'