Product Direction: What Should Dooma Improve Next?

[im-anishraj]

This discussion is for product-level ideas before they become scoped implementation issues.

Dooma should stay fast, local, and focused. Strong proposals usually improve one of these areas:

• Faster practice decisions.
• Better company or pattern discovery.
• More reliable local progress tracking.
• Higher-quality dataset coverage.
• Better contributor workflows.
• Cleaner terminal UX.

Proposal Format

Problem:
Who benefits:
Proposed behavior:
Alternatives considered:
Why this fits Dooma:
Possible risks:

Current High-Impact Themes

• Completing pattern tags across questions.
• Filling NeetCode 150 and Striver SDE mappings.
• Improving CLI filters and export/import workflows.
• Adding CI and packaging safeguards.
• Making docs and contribution paths easier for newcomers.

Ideas that become clear and scoped can be converted into GitHub Issues with acceptance criteria.