app-evolver

1# App Evolver
2 
3Improve the application's actual user result. Extract transferable mechanisms,
4resolve their fit with the current product, implement authorized improvements,
5and verify them through the application's consuming surface.
6 
7Use this as an orchestration Skill. Keep repository engineering, research,
8history access and release operations with their existing owners. For a Skill
9target use `skill-evolver`; for competitor intelligence alone use
10`competitors-analysis`; for a new product specification use the available
11requirements workflow. Do not replace those owners with another execution engine.
12 
13## 1. Bind the application and unfinished result
14 
15Before research or edits, establish:
16 
17- Exact application, repository/ref, platform and runtime or deployment identity.
18- Original user request, current product contract and active stage; distinguish
19  long-term positioning from the work selected now.
20- User-visible improvement, falsifiable acceptance evidence, authorized
21  deliverables, protected behavior/data and stopping condition.
22- Analysis-only versus implementation authorization, and any unresolved
23  product choice whose answer changes the outcome.
24- Scope of the learning task. For a broad product or competitor learning
25  effort, let the bound device and operator roles and the complete intended
26  user result, with its impact judgments, constrain the research questions
27  before selecting any single technical scenario for study. Keep a task about
28…