beads-write

Analyze a codebase to generate Beads tickets with titles, descriptions, and labels.

Updated Aug 27, 2026

Search Tags:#beads #TODOs #project-management #task-breakdown #codebase-analysis #ticketing

Ready to run

npx skills add https://github.com/jjeremycai/claudekit --skill beads-write

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-write
Source: https://github.com/jjeremycai/claudekit/tree/main/skills/beads-write
Command: npx skills add https://github.com/jjeremycai/claudekit --skill beads-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads-write helps teams convert scattered TODOs, notes, and codebase insights into well-defined Beads tickets, enabling structured planning and measurable progress.

Core Features & Use Cases

Generate Beads tickets from codebase findings to capture scope, context, and context-specific acceptance criteria.
Break down large work into epics, tasks, and atomic tickets for focused execution.
Transform TODOs/FIXMEs into ready-to-work items across projects, improving traceability and delivery.

Quick Start

Run beads-write to generate initial tickets from the current project, then use beads-execute to create them and verify changes with verify-changes to ensure alignment with expectations.

Frequently Asked Questions about beads-write

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert TODOs and FIXMEs in my codebase into actionable tickets?▼

Converting TODOs into actionable tickets involves analyzing your codebase to extract scattered notes and generate well-scoped items with clear descriptions, acceptance criteria, and labels. This ensures tasks are traceable and ready for focused execution.

What is the best way to break down large feature planning tasks into atomic tickets?▼

Breaking down large features into atomic tickets requires analyzing the project scope and generating structured epics and tasks. This provides focused execution items with testable outputs and measurable progress for structured planning.

Can I generate project management tickets for codebase auditing across multiple programming languages?▼

Yes, generating project management tickets for codebase auditing works across multiple languages and projects. It captures bugs and tech debt by applying clear scope and actionable acceptance criteria to the findings.

Do I need a specific ticketing system to scope tech debt captured from codebase insights?▼

No specific ticketing system is required to scope tech debt. The process generates well-defined tickets with titles, descriptions, and labels directly from codebase insights, ensuring clear scope and testable outputs.

How do I ensure codebase analysis tickets have clear scope and testable acceptance criteria?▼

To ensure tickets have clear scope and testable acceptance criteria, the analysis process extracts context from codebase findings and generates structured items with specific titles, descriptions, and labels for focused execution.

What are the limitations of converting codebase insights into structured tickets?▼

A limitation of converting codebase insights into tickets is that it focuses on scoping and planning rather than execution. It generates the actionable items, but downstream tools are needed to create and verify the actual code changes.