FS-05
Commit after Done
Flow Story
Default severity: medium
ProcessMetrics
What it detects
commits after issue reached Done; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows commits after issue reached done; tests; catalogue during analysis.
- Example signal: commits after issue reached Done; tests; catalogue.
Suggested response
Review the observation details with the team and agree one concrete next step to reduce recurrence.
Coaching playbook
Symptom
The "Commit after Done" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Commit after Done" 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
Review the observation details with the team and agree one concrete next step to reduce recurrence.
Facilitation questions
- What system change would stop "Commit after Done" 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.