skills.rest
beesyst
beesystCOMMUNITY
Explore all skills by this author →
GitHub

beeui-plan-iteration

Validates BeeUI roadmap items and prepares copy-ready Issues through read-only repository inspection.

Updated May 30, 2026
Search Tags:#mcp#roadmap planning#issue generation#repository inspection#read-only workflow#ownership analysis#iteration validation
One-click install
npx skills add https://github.com/beesyst/beeui --skill beeui-plan-iteration-beesyst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beeui-plan-iteration
Source: https://github.com/beesyst/beeui/tree/main/.agents/skills/beeui-plan-iteration
Command: npx skills add https://github.com/beesyst/beeui --skill beeui-plan-iteration-beesyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning BeeUI framework work often suffers from unverified assumptions, unclear ownership between BeeUI and product repositories, and roadmap drift. This Skill inspects the current implementation through Bee Dev MCP, validates whether proposed work is actually necessary, and produces a reconciled roadmap item plus complete Issues without modifying any repository. ## Core Features & Use Cases - Evidence-based validation: Treats proposed tasks and roadmap references as hypotheses and verifies them against current code, templates, contracts, and tests before agreeing. - Ownership and roadmap reconciliation: Decides whether work belongs to BeeUI, a product repository, or a domain module, and selects reuse, refine, replace, insert, standalone, or reject decisions with correct iteration numbering. - Copy-ready outputs: Produces a compact roadmap iteration fragment (Russian body, English titles) and complete per-repository Issues following the actual issue template, plus a structured planning handoff. - Use Case: A product team proposes a new BeeUI widget. The Skill inspects the current adapter contract, finds the gap is product-side only, rejects the BeeUI iteration, and documents the simpler product-side alternative. ## Quick Start Ask the AI to run the BeeUI planning workflow for a proposed task or roadmap iteration, providing the worktree, mode, roadmap context, and task description.

Frequently Asked Questions about beeui-plan-iteration

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

FAQPage Schema
How do I validate a BeeUI roadmap iteration before implementation?▼

Run the planning workflow with the roadmap context and task description. It inspects the referenced iteration, neighbouring items, current implementation, and public contracts through Bee Dev MCP, then returns a necessity verdict and a planning decision such as reuse, refine, insert, or reject.

How do I decide whether work belongs in BeeUI or a product repository?▼

The workflow applies the boundary that BeeUI owns generic rendering, routes, adapters, and package assets, while products own read-models, labels, and actions. It inspects both repositories when supplied and assigns separate Issues per implementation repository.

Can this planning workflow modify files or create Issues automatically?▼

No. The workflow is strictly read-only: it cannot modify files, switch branches, run tests, or create Issues, branches, or PRs. It only returns copy-ready roadmap fragments and Issue text for manual use.

What happens if the referenced roadmap iteration is already done?▼

Completed history is preserved: the item is never returned to PLANNED and its ID is never reused. The workflow checks whether the request is already implemented and only creates a new unique ID for genuine follow-up work.

When should a task be classified as standalone instead of a numbered iteration?▼

Standalone applies only to narrow local work with no reusable capability, public contract, or cross-repository impact, such as typo fixes or small test corrections. Substantial changes to components, routes, schemas, or assets require a numbered iteration.

What are the limitations of this planning workflow?▼

It cannot execute implementation, prepare implementation or verification prompts, or write PR bodies; those belong to separate prompt stages. If mandatory repository evidence cannot be retrieved, it returns PLANNING INCOMPLETE instead of guessing.

Related Skills

Explore More Software Engineering Skills→
getcrew44getcrew44
358

roadmap-planning

Produce outcome-driven product roadmaps with prioritized, dependency-aware epics.

Official
Intermediate
astrosteveoastrosteveo

finishing-a-development-branch

Run project tests, update documentation, and create a PR-ready summary.

Community
Intermediate
zxyycomzxyycom

api-and-interface-design

Design and audit observable public API contracts with compatibility strategies.

Community
Intermediate
kirillshilinkirillshilin

requirements-prioritization

Prioritize product requirements using MoSCoW, RICE, or Kano frameworks.

Community
Intermediate