Weekly Feedback Template¶

Pilot Program - Week [NUMBER] Feedback¶

Your Name: ___________________________
Company/Project: ___________________________
Date: ___________________________
Week of Program: Week ___ of 24

1. Progress This Week¶

What Did You Accomplish?¶

• Feature/milestone completed:
• Lines of USL code written: ___
• Tests added: ___
• Deployment status: ☐ Dev ☐ Staging ☐ Production

Key Achievements¶

Code Samples (Optional)¶

// Your code here

2. Blockers Encountered¶

Critical Blockers¶

Priority: 🔴 High / 🟡 Medium / 🟢 Low

1. Issue:
2. Impact:
3. What I've Tried:

4. Need Help With:

5. Issue:

6. Impact:
7. What I've Tried:
8. Need Help With:

Minor Issues¶

-¶

3. Feature Requests¶

Must-Have Features¶

Priority: 🔴 Critical / 🟡 Important / 🟢 Nice-to-Have

1. Feature:
2. Use Case:
3. Current Workaround:

4. Priority:

5. Feature:

6. Use Case:
7. Current Workaround:
8. Priority:

Nice-to-Have Features¶

-¶

4. Bug Reports¶

Bugs Found This Week¶

Bug #1 - Severity: 🔴 Critical / 🟡 Major / 🟢 Minor - Description: - Steps to Reproduce: 1. 2. 3. - Expected Behavior: - Actual Behavior: - Environment: USL v___, OS ___, Database ___ - Error Message (if any):

Bug #2 - Severity: - Description: - Steps to Reproduce: - Expected vs Actual:

5. Documentation Feedback¶

Documentation Gaps¶

• Topic:
• What's Missing:
• Would Help If:

Documentation Improvements¶

• Page/Section:
• Issue:
• Suggestion:

6. Developer Experience¶

What Worked Well This Week?¶

-¶

What Was Frustrating?¶

-¶

Tool/IDE Experience¶

• IDE Used: ☐ VSCode ☐ IntelliJ ☐ Vim ☐ Other: ___
• USL Extension Working Well?: ☐ Yes ☐ Mostly ☐ No
• Issues with Tooling:

7. Performance & Quality¶

Build Times¶

• Average compile time: ___ seconds
• Is this acceptable?: ☐ Yes ☐ No

Runtime Performance¶

• API response times: ___ ms (p95)
• Database query performance: ☐ Good ☐ Acceptable ☐ Slow
• Any performance issues?:

Code Quality¶

• Test coverage: ___%
• Using USL best practices?: ☐ Yes ☐ Mostly ☐ Need guidance

8. Support Experience¶

Office Hours Attendance¶

• Attended this week?: ☐ Yes ☐ No
• If Yes, was it helpful?: ☐ Very ☐ Somewhat ☐ Not really
• Topics you'd like covered:

Discord Support¶

• Used Discord for help?: ☐ Yes ☐ No
• Response time satisfaction: ☐ Excellent ☐ Good ☐ Slow
• Got your question answered?: ☐ Yes ☐ Partially ☐ No

1-on-1 Support¶

• Requested 1-on-1 this week?: ☐ Yes ☐ No
• If Yes, was it valuable?: ☐ Very ☐ Somewhat ☐ Not much

9. Overall Satisfaction¶

This Week's Rating: ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5 ☐ 6 ☐ 7 ☐ 8 ☐ 9 ☐ 10¶

1 = Very Unsatisfied, 10 = Very Satisfied

Why This Rating?¶

Program Satisfaction Trend¶

• Compared to last week: ☐ Better ☐ Same ☐ Worse
• Overall program satisfaction: ☐ 1-3 ☐ 4-6 ☐ 7-8 ☐ 9-10

10. Looking Ahead¶

Next Week's Goals¶

Anticipated Challenges¶

-¶

Support Needed¶

-¶

11. Additional Comments¶

Suggestions for Program Improvement¶

Shout-outs¶

Anything Else?¶

12. Metrics (Auto-collected where possible)¶

Please provide if not auto-collected:

• Total USL code lines: ___
• Number of entities defined: ___
• Number of API endpoints: ___
• Test coverage: ___%
• Deployment frequency: ___ times this week
• Build success rate: ___%

Submission¶

How to Submit:

1. Via Discord: Post in #feedback channel (preferred)
2. Via GitHub: Create issue with label weekly-feedback
3. Via Email: Send to early-adopters@usl.dev

Due Date: Every Friday by 5 PM ET

Thank you for your feedback! Your input directly shapes USL's development. 🙏

Template Version 1.0 - January 15, 2026