What problem does it solve? Planning a BeeSDK iteration often relies on stale roadmaps, unverified assumptions, or unclear ownership between BeeSDK and consumer repositories. This Skill inspects the actual implementation through Bee Dev MCP, validates whether work is truly necessary, and produces a reconciled roadmap item plus complete, copy-ready Issues without modifying any repository. ## Core Features & Use Cases - Evidence-based validation: Treats tasks and roadmap references as hypotheses and verifies them against current code, tests, contracts, and package metadata via Bee Dev MCP. - Roadmap reconciliation: Chooses exactly one planning decision (reuse, refine, replace, insert, standalone, or reject) while preserving completed history and numbering rules. - Ownership and cross-repository planning: Determines whether work belongs to BeeSDK, a consumer, a domain module, or BeeUI, and defines implementation and release order per repository. - Use Case: A user proposes "Iteration SDK-4" for a new public contract. The Skill inspects the repo, finds the capability already exists, rejects the work as unnecessary, and explains the simpler alternative with evidence. ## Quick Start Ask the assistant to run the BeeSDK planning workflow for your task or idea, providing the main worktree path, mode, roadmap context, and any additional repositories.
