skills.rest
ArchaonHW
ArchaonHWCOMMUNITY
Explore all skills by this author →
GitHub

wds-8-product-evolution

Guides incremental brownfield product improvements through analyze, scope, design, implement, test, and deploy cycles.

Updated Mar 14, 2026
Search Tags:#pull request#continuous improvement#ux design#brownfield#kaizen#acceptance testing#product evolution
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill wds-8-product-evolution-archaonhw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wds-8-product-evolution
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/wds-8-product-evolution
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill wds-8-product-evolution-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Improving an existing product often lacks structure: teams jump straight to code without analysis, skip acceptance testing, or let scope creep turn small fixes into redesigns. This Skill provides a disciplined, menu-driven workflow for making one focused improvement at a time on an existing product. ## Core Features & Use Cases - Six-Activity Pipeline: Analyze Product, Scope Improvement, Design Solution, Implement, Acceptance Test, and Deploy — each a compressed version of a full design phase. - Branch-Based Delivery: Every improvement lives in its own evolution/ branch and ships as a pull request with linked analysis, specification, and test report artifacts. - Kaizen Templates: Includes reference templates for context gathering, design specs, delivery packaging, monitoring, and impact measurement. - Use Case: A product has a feature with 15% usage and 40% drop-off. Use this Skill to analyze the problem, scope an onboarding improvement, write a specification with acceptance criteria, implement it in a branch, test against the spec, and deliver a PR with monitoring guidance. ## Quick Start Ask the agent to analyze the current product and propose a prioritized list of improvement targets to start an evolution cycle.

Frequently Asked Questions about wds-8-product-evolution

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

FAQPage Schema
How do I structure a small product improvement from analysis to deployment?▼

Follow the six-activity menu: Analyze Product to find targets, Scope Improvement to define one scenario, Design Solution to write a specification, Implement in an evolution branch, Acceptance Test against the spec, then Deploy as a pull request with a delivery summary.

What is the difference between kaizen and kaikaku in product improvement?▼

Kaizen means small, low-risk incremental changes shipped continuously in one-to-two-week cycles, which is what this workflow uses. Kaikaku means large, revolutionary redesigns done as a one-time transformation, suited to new product development instead.

Does this workflow work for brownfield projects with an existing codebase?▼

Yes, it is designed specifically for brownfield products. The Implement activity instructs you to read existing code, follow current patterns and conventions, make minimal changes, and commit incrementally in a dedicated evolution branch.

How are acceptance criteria tested before deploying an improvement?▼

The Acceptance Test activity extracts criteria from the specification into a checklist table, then verifies each one plus responsive behavior, edge cases, and regressions. Results are documented in a test report with a pass, pass-with-notes, or fail recommendation.

What artifacts does each improvement cycle produce?▼

Each cycle produces an analysis document, a scenario, a specification with acceptance criteria, a test report, and a delivery summary linked to the pull request. All artifacts are stored under the configured output folder in evolution subdirectories.

When should I not use this incremental improvement workflow?▼

Avoid it for complete redesigns, new product builds, or major strategic pivots, which need a full greenfield workflow instead. It is also unsuitable when scope cannot be limited to one focused change per cycle.

Related Skills

Explore More Product & Management Skills→
propane-aipropane-ai
4

churn-prediction

Analyze CRM and support data to identify and prioritize at-risk customers.

Official
Intermediate
aicodeproaicodepro

canary

Monitors deployed applications for console errors, performance regressions, and page failures.

Official
Advanced
SoSoBurnerSoSoBurner

ship

Automate code deployment by running tests, reviewing diffs, and creating a pull request.

Community
Advanced
GenEducationGenEducation

wds-1-project-brief

Capture vision, positioning, users, and constraints into a product brief.

Official
Advanced