bead-forge

Feature decomposition breaks feature descriptions, source files, and existing epics into actionable beads with priorities, estimates, acceptance criteria, and dependency ordering. This front-loads scope clarification to reduce revision churn and implementation back-and-forth.

Checkpointing preserves decisions, discoveries, reviews, and memory-worthy conclusions into persistent memory records and beads before conversation compaction loses them. This captures both the rationale and the next implementation steps for future reference.

Dependency mapping identifies and orders work item relationships during migration breakdowns or feature planning. It ensures correct bead wiring by structuring titles, priorities, estimates, and design notes so bounded work items execute in the proper sequence.

Yes, acceptance criteria define specific conditions for task completion during implementation scoping. Structured bead drafting applies granularity rules and self-check criteria to ensure work items are bounded, testable, and immediately ready for execution.

Task decomposition accepts feature descriptions, source files, existing epics, and accumulated discussion context as input. It processes this mixed context to produce structured beads with category labeling and memory index maintenance.

Work planning with beads requires structured drafting with titles, priorities, estimates, and design notes, which adds upfront effort. However, built-in quality gates apply challenge steps for multi-bead plans to maintain granularity and correct labeling conventions.