Execute beta refactor TODOs with multi-LLM regression audits and wrap-up gates.
npx skills add https://github.com/Pionpill/retikz --skill flow-beta
Please help me install this Agent Skill. Skill: flow-beta Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/flow-beta Command: npx skills add https://github.com/Pionpill/retikz --skill flow-beta
This Skill prevents beta refactors from silently introducing regressions by enforcing a structured 3-stage workflow with mandatory multi-LLM review, especially for breaking changes.
Use the flow-beta skill to execute one registered beta plan TODO end-to-end from implementation through multi-LLM evaluation to wrap-up with required halting gates.
High-intent search queries and answers about installing and using this skill.
Prevent regressions during beta refactors by enforcing a structured workflow with mandatory multi-LLM regression and equivalence audits. This approach confirms no regressions and verifies the change is actually better before allowing wrap-up.
Multi-LLM regression testing runs independent equivalence and benefit audits to confirm code refactoring introduces no regressions and is actually better. It enforces BLOCKING, WARNING, and INFO convergence from two separate LLM evaluations before passing.
Execute a beta refactor plan TODO through implementation, mandatory multi-LLM regression evaluation, and final wrap-up. The workflow enforces hard gates on test, lint, and tsc success before allowing progression to the next stage.
Breaking changes are allowed during the beta refactor window if they include migration documentation. The workflow enforces stricter requirements for breaking items, requiring changelog BREAKING sections and roadmap check-off completion.
Beta refactoring focuses strictly on implementing plan TODOs with guardrails against scope creep. It explicitly prevents adding new features, IR, or public fields, ensuring changes remain isolated to the registered beta plan.
Two independent LLM audits provide a safety net by cross-validating refactor equivalence and benefits. Requiring convergence on BLOCKING, WARNING, and INFO statuses prevents silent regressions that a single evaluation might miss.
PionpillPublish retikz npm packages with synchronized versions, changelogs, and validated release workflows.
akillnessOrganize changelogs and release notes using Keep a Changelog structure.
entoreneeUpgrade npm dependencies incrementally with validation gates and engineer approval.
deMGoncalvesValidate phase transitions against quality gates and project standards.
