File a Feature Request

Three identical asks is a Feature Request, not a Pack to build. The DOS team curates Packs. Your job is to notice the pattern and tell them about it.

Why Packs are platform-curated

<!-- brand-voice:exempt — technical interop contract, not marketing claim --> A Pack is a distribution unit with a routing contract, rating surface, upgrade path, and interop guarantees against every other Pack. The Algorithm has to know about it at session start. One Pack renamed by an end user breaks the skills index and every doc link that pointed at it.

The DOS team owns Pack curation so the index stays coherent and upgrades don't strand user work. You get the inverse benefit: describe an outcome and the Algorithm improvises from 26 Packs that all compose.

What counts as a Feature Request

The signal is the three-asks rule. First time you phrase an outcome, it's a one-off. Second time, a coincidence. Third time you phrase the same kind of ask the same way, you've found a workflow worth shipping.

A good Feature Request has three things:

1. Concrete prompt — the actual sentence you typed the third time. Copy-paste it.
2. Expected outcome — what "done" looked like in your head. Format, length, quality bar.
3. Why no existing Pack fits — which Packs you tried, what they got wrong, what was missing.

Without item 3 the DOS team can't tell whether you need a new Pack, an extension to an existing one, or a sharper description field so routing improves.

How to file one

Open a GitHub issue on durante-tech/dos with the feature-request label:

Or use the web template at github.com/durante-tech/dos/issues/new. The body should follow the three-item shape above. Three bullet points is enough. Don't write a design doc — the team writes the design doc.

What happens after

The DOS team triages Feature Requests on a rolling basis and decides between three outcomes:

• New Pack — the pattern is large enough and distinct enough to warrant a new distribution unit. Lands in a future release.
• Extend an existing Pack — the pattern fits an existing domain. The team adds a workflow or routing row. Usually ships within one release. See Extend an existing Pack for what that looks like from the inside.
• Improve routing — the capability already exists and the Algorithm just wasn't finding it. The team sharpens the Pack's description and keywords so the ask routes automatically next time.

Every decision posts back on the issue. The team doesn't silently close Feature Requests.

Next