TQ-12

Thin Requirement Brief

Text Quality

Default severity: high
ProcessMetrics

What it detects

Description is empty or very short (≤150 chars) without structured acceptance criteria (Tabuľka 1 #3).

Detection formula

IF issue.type IN ac_required_types AND (description empty OR length ≤150) AND AC empty THEN FLAG

Examples in practice

  • One-line summary with empty AC field on a Story.

Suggested response

Add purpose, context, and three to seven testable acceptance criteria before development.

Coaching playbook

Symptom

Description is empty or very short (≤150 chars) without structured acceptance criteria (Tabuľka 1 #3).

Why it matters

When "Thin Requirement Brief" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.

What you can achieve

Add purpose, context, and three to seven testable acceptance criteria before development.

Facilitation questions

  • What system change would stop "Thin Requirement Brief" from firing again?
  • What do the cited issues have in common — same root cause or same workaround?
  • Who owns the two-week experiment and how will we verify on the next import?

Run this rule against your own tracker data with Flow Analyzer.

Product tourSign in
TQ-12: Thin Requirement Brief — FlowAnalyzer