byte-iteratelisted
Install: claude install-skill elan6666/your-bytedance-skills
# Byte Iterate
Iterate turns evidence into product improvements. In auto mode it defaults to 3
loops unless the user specifies a positive count. In manual mode it runs the
requested number, or 1 loop if unspecified.
## Inputs
Read available evidence:
```text
.byte-os/reviews/*.md
.byte-os/users/*.md
.byte-os/RESEARCH.md
.byte-os/COMPETITORS.md
.byte-os/BUILD_LOG.md
.byte-os/ROADMAP.md
.byte-os/PRODUCT_SPEC.md
.byte-os/OKRS.md
```
Real user feedback must come from `byte-users` or user-provided materials. If none exists, label the iteration as based on internal review and research, not real users.
Do not use parked entries from `.byte-os/FUTURE.md` as iteration inputs or
unfinished work. Only entries explicitly promoted through the normal workflow
may influence an iteration.
## Iteration Loop
For each loop:
1. Select evidence:
- Review findings
- Test failures
- Real user feedback if available
- Market or competitor changes if researched
2. Diagnose:
- Product issue
- UX issue
- Technical issue
- Growth issue
- Quality issue
3. Prioritize:
- Must fix
- High leverage
- Defer
- Reject
4. Experiment:
- Write the hypothesis.
- Define metric, baseline, expected movement, and confidence.
- Use A/B testing only when there is enough traffic and a measurable outcome.
- Use usability tests, dogfooding, or instrumentation when A/B testing is not suitable.
5. Plan:
- Create or update plan files for the iteration.
- Keep