iterate

Analyze post-launch product data and convert it into prioritized iteration actions.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill iterate-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/iterate
Command: npx skills add https://github.com/lalulali/vespyr --skill iterate-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams improve a product after launch by turning real user data, feedback, and experiment results into clear iteration decisions instead of guessing what to build next.

Core Features & Use Cases

  • Post-launch analysis: Reviews adoption metrics, drop-offs, errors, support tickets, and qualitative feedback.
  • Opportunity prioritization: Converts insights into ranked improvements using RICE and separates quick wins from strategic bets.
  • Design, architecture, and execution planning: Coordinates product design updates, architecture impact checks, task breakdowns, implementation, review, QA, deployment, and measurement.
  • Use case: A feature is live but underperforming, and this Skill helps decide whether to tweak the UX, adjust the architecture, or roll back and rethink the hypothesis.

Quick Start

Use the iterate skill to analyze post-launch feedback and build the next iteration plan for the feature.

Frequently Asked Questions about iterate

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

FAQPage Schema
How do I prioritize product iterations after a feature launch?

Prioritize product iterations by analyzing post-launch performance data, user feedback, and A/B test results, then ranking improvements using the RICE framework to separate quick wins from strategic bets.

What is the best way to analyze post-launch product performance data?

Analyze post-launch product performance by reviewing adoption metrics, drop-off rates, errors, support tickets, and qualitative feedback to convert real user insights into clear iteration decisions.

How do I decide whether to tweak UX or adjust architecture for an underperforming feature?

Decide whether to tweak UX or adjust architecture by analyzing live feature data to determine if drop-offs stem from design friction or architectural limits, guiding whether to iterate or roll back.

Can I use A/B testing results for release planning and ongoing product optimization?

Use A/B testing results for release planning by applying experiment outcomes to prioritize UX improvements, coordinate architecture impact checks, and plan deployment for the next product optimization cycle.

Does post-launch iteration planning require coordination across development and QA?

Post-launch iteration planning requires coordination across analytics, product management, design, architecture, development, QA, deployment, and impact measurement to execute ranked improvements effectively.

When should I not use RICE prioritization for product iteration?

Avoid using RICE prioritization for product iteration when post-launch data is insufficient or qualitative feedback contradicts adoption metrics, requiring a roll back and hypothesis rethink instead of forced ranking.