Summary

Parent tracker for consolidated enhancement planning, ordered by ease of development/workflow so execution can run top-down with minimal dependency churn.

Recommended Execution Order

1. Warn when target directory already exists and is not empty (from issue 198)
2. Make initialize git optional (from issue 147)
3. Remove the count demo for Start (from issue 137)
4. Starters documentation (from issue 102)
5. Custom add-on documentation (from issue 99)
6. Prompt to remove demo pages (from issue 136)
7. Fix up the examples (from issue 138)
8. Use add-on variables to seed .env (from issue 135)
9. Custom add-on protected files (from issue 100) - deferred for now
10. Add versioning to add-on metadata (from issue 139)
11. Add oxlint as option (from issue 166) - deferred for now
12. Add option for Zephyr (from issue 160) - deferred for now
13. Pipeclean add-on creation process (from issue 132)
14. Upgrade existing add-ons (from issue 129)
15. Add-on upgrade strategy (from issue 131)
16. Remote package management for add-ons (from issue 130)
17. Documentation site (from issue 134)
18. Anonymous telemetry (from issue 133)

Notes

• New design conversation should happen in Discussions.
• This issue tracks planning and sequencing; implementation can happen in focused child issues/PRs.