Create an evolution plan from source plan artifacts without rewriting code.
npx skills add https://github.com/Honigbart/honeyflow --skill evolve-honigbart
Please help me install this Agent Skill. Skill: evolve Source: https://github.com/Honigbart/honeyflow/tree/main/evolve Command: npx skills add https://github.com/Honigbart/honeyflow --skill evolve-honigbart
Evolve helps teams extend an already implemented feature, module, workflow, MVP, or product into a more capable v2 without starting from scratch, preserving working parts and learning from what exists.
Create a new evolution plan slug referencing the source plan and generate an evolution_plan.md with a grounded, phased roadmap.
High-intent search queries and answers about installing and using this skill.
To plan feature improvement without a rewrite, you need an evolution plan that reads existing source artifacts and generates a phased roadmap. This approach preserves working implementation parts while targeting high-leverage upgrades for your next version.
Creating a v2 roadmap from existing plans involves grounding the evolution in source artifacts like final plans and execution states. This produces a new project-aware evolution plan with concrete next steps rather than starting development from scratch.
Yes, you can evolve an implemented module without triggering execution. The evolution process keeps the source plan intact and only generates a new evolution_plan.md document, ensuring no automated execution occurs during the planning phase.
Yes, source plan artifacts are required to ground your product evolution roadmap. The process reads files like final_plan.md, execution_state.md, and brainstorm documents to ensure the v2 evolution plan is based on the actual implemented reality.
Generating an evolution plan helps MVP feature development by assessing the current implementation and identifying high-leverage improvements. It outputs a phased roadmap document that maintains traceability to the original source plan for your v2 upgrade.
You should not use an evolution plan when a complete system rewrite is necessary. This approach is designed to extend and improve already implemented features, modules, or workflows by preserving working parts rather than replacing the entire architecture.
HonigbartReview one completed execution phase against a plan with Claude-Codex.
eng-ccIdentify 10x product opportunities and prioritize high-leverage improvements for strategic planning.
haidonglethqbCoordinate AI agents and visualize plans with a dashboard UI.
ljucaskCreate and update product roadmaps with versioned, phase-based delivery plans.
