| id | DEV-210 | |
|---|---|---|
| title | Route Discussion to the Right Channel | |
| status | active | |
| enforcement | manual | |
| severity | warning | |
| depends_on |
|
When scope debates and status updates land in Goal issues, they bury the Goal-to-Problem-to-PR chain in noise, and scope decisions drift away from the Spec that is supposed to hold them.
Direct each discussion to its channel.
- Spec file: clarifications about Goal scope or business context. Propose changes via a PR against the spec, or review comments on an open Spec PR.
- Problem issues: tracking the obstacles that prevent achieving the Goal.
- Goal issues: linking Specs, tracking Problems, and monitoring progress only. Do not post Problem status updates, PR notifications, or progress updates here.
If you spot a potential new problem but are unsure it is planned: check for an existing Problem issue; if none, open a PR against the Spec (or a review comment if the Spec PR is open); if needed, create a new Problem issue and discuss it there. When someone must act to unblock progress, assign them to the Goal issue so the dependency is visible.
- Scope and business clarifications go to the Spec, not Goal comments
- Goal issues carry only Spec links, Problem tracking, and progress
- No status updates or PR notifications are posted in Goal issues
- Blocking dependencies are surfaced by assigning the person to the Goal