bd-modify-product-description-and-tasks_skill

Overview

This skill lets you create, edit, update, and manage product descriptions and tasks using the bd (beads) issue tracker. It focuses on producing well-formed issues, maintaining proper metadata, and handling dependencies and state transitions so tasks stay actionable and traceable. The workflow uses Git + JSONL for distributed, version-controlled issue management.

How this skill works

The skill operates by reading and writing issues stored in a .beads/issues.jsonl file that git tracks. It exposes commands to create issues (single or bulk), edit fields, set states, manage dependencies, add labels and comments, and move issues between rigs. All changes are regular git commits, so syncing is done via git pull/push and merge conflicts are handled like code changes.

When to use it

• Create a new task, bug, feature, or epic with full context and acceptance criteria
• Update an existing issue’s title, description, type, or state
• Add or remove dependencies before work begins or as plans change
• Label, categorize, or comment on issues to provide status and context
• Move work items between rigs or reorganize/split tasks
• Quickly capture a task from scripts or editor with minimal friction

Best practices

• Write clear, descriptive titles that convey outcome and scope
• Include context, acceptance criteria, and relevant links in descriptions
• Set dependencies early to prevent duplicate or blocked work
• Keep issue states current to reflect real progress
• Use consistent labels for filtering and reporting
• Add concise comments for decisions, blockers, or handoffs

Example use cases

• Create a feature issue from markdown to onboard a scoped project deliverable
• Update an in-progress task description to reflect changed acceptance criteria
• Add dependencies to a deployment task so prerequisite work is tracked and blocked appropriately
• Move a component bug to another rig and automatically remap its dependencies
• Quick-capture a one-line task from a script and get back the new issue ID for automation