bead-polishing

Polish task breakdowns into a non-duplicated, converged task set.

2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/vnnkl/agentflywheel --skill bead-polishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bead-polishing
Source: https://github.com/vnnkl/agentflywheel/tree/main/skills/bead-polishing
Command: npx skills add https://github.com/vnnkl/agentflywheel --skill bead-polishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bead polishing helps teams refine task breakdowns across formats (beads, issues, user stories) through structured rounds to reduce duplicates, gaps, and ambiguities, achieving a converged plan ready for execution.

Core Features & Use Cases

  • Structured polishing rounds: run 4–6 rounds with consistent checks (duplicates, coverage, dependencies, description depth, sizing) to converge on a complete task set.
  • Cross-format compatibility: works with beads (.beads/beads.jsonl), GitHub issues, PRD-style user stories, or any structured task list derived from a source plan.
  • Convergence tracking: records changes per round and signals convergence to prevent over-polishing.

Quick Start

Start by identifying your source plan, then run four to six polishing rounds to converge on a final, non-overlapping task set.

Frequently Asked Questions about bead-polishing

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

FAQPage Schema
How do I remove duplicates and gaps in task breakdowns before execution?

Polishing task breakdowns removes duplicates and gaps by applying consistent checks across 4–6 structured rounds. This process validates coverage against your source plan to converge on a precise, non-overlapping task set ready for execution.

What is convergence tracking and how does it prevent over-polishing task lists?

Convergence tracking records changes per polishing round and signals when the breakdown stabilizes. This mechanism prevents over-polishing by stopping the process once a precise, non-duplicated set of tasks is achieved.

Can I refine GitHub issues and PRD user stories using structured polishing rounds?

Yes, structured polishing rounds work with GitHub issues, PRD user stories, and beads formats. The process applies checks for dependency integrity, description completeness, and sizing across these structured task lists.

How do I check dependency integrity and sizing for a structured task list?

You check dependency integrity and sizing by applying structured polishing rounds to the structured task list. These rounds impose specific checks for dependencies, description depth, and task sizing to ensure plan completeness.

When do I need to polish task breakdowns derived from a source plan?

You need to polish task breakdowns when your derived task list suffers from duplicates, gaps, or ambiguities. Running 4–6 focused polishing rounds converges the list into a complete, non-overlapping set ready for execution.