What does dspec get wrong?

[tuna781]

Genuinely — where does this get in your way?

dspec is built on a few decisions that are not obviously right, and the ones that are wrong will
show up in use long before they show up in my head:

• code: and uses: are written by a person, never inferred from imports. That is what stops
  a confident wrong answer, and it is also the tedious part.
• One markdown file per feature. Fine at forty features. At four hundred?
• Report, never block. Nothing exits non-zero unless you ask. If that means everyone ignores
  the report, the design is wrong.
• A description is stale when the files it names change. File-level fingerprints are coarse on
  purpose. If yours go stale on every unrelated edit, say so — that is the failure mode I most want
  to hear about.

Concrete beats polite. "I stopped using it after a week because X" is the most useful thing you
can post here.