Analyze a codebase to generate Beads tickets with titles, descriptions, and labels.
npx skills add https://github.com/jjeremycai/claudekit --skill beads-write
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
Beads-write helps teams convert scattered TODOs, notes, and codebase insights into well-defined Beads tickets, enabling structured planning and measurable progress.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
mec07Create Jira tech debt tickets from brief notes with duplicate checks.
menoncelloOrchestrate subagents, commands, MCP servers, and skills with parallel execution.
elihunter173Automate Jira ticket workflows from analysis to draft pull requests.
levnikolaevichAudit test suites across six quality categories with five specialized workers.
