atomic-bead-filing

Code smell tracking works by creating actionable beads grounded in specific files and line numbers, capturing observations as defined tasks for future agents to execute without interrupting your current development workflow.

An executable bead is a well-defined task generated from code review observations, featuring descriptions, priorities, and acceptance criteria grounded in specific codebase locations for future agents to execute.

To file a bead, capture the code smell observation from your current context, which automatically grounds the insight in specific files and line numbers while allowing you to define priority and detailed descriptions.

Yes, you can flag ambiguous code review issues using the human-needed label, which clearly outlines decision points where multiple approaches exist and human input is required before proceeding.

Yes, the bead creation process supports priority setting for development tasks, allowing you to assign priority levels alongside detailed descriptions and acceptance criteria when filing observations about workarounds or design flaws.

You should avoid using beads for code quality observations requiring immediate resolution, as beads are designed to define actionable tasks for future agents rather than executing fixes instantly within your current session.