CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/issue-tracker-toolkit

Toolkit for writing, refining, and prioritizing tickets on issue-tracking systems (Jira and equivalents). Covers three concerns: writing clear acceptance criteria for user stories; applying MoSCoW prioritization to requirements and backlogs; and readying sparse backlog tickets for refinement by gathering incident context, applying a YAML template, and generating a validated structured document.

93

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

effort-balancing-and-tradeoffs.mdmoscow-prioritization/references/

Effort Balancing and Tradeoffs

Use this guide after initial categorization.

Target Distribution

  • Must: 50-60% effort
  • Should: 20-30% effort
  • Could: 10-20% effort
  • Won't: explicit exclusions

Rebalance Rules

  1. If Must > 60%, downgrade lowest-impact Must items.
  2. If Could is empty, force explicit enhancement candidates.
  3. If Won't is empty, add at least 3 deferred items.

Tradeoff Examples

  • Move advanced analytics from Must to Should to protect launch date.
  • Move custom theming from Should to Could when staffing drops.
  • Move legacy export format from Could to Won't when demand is low.

Verification

Review the final mix with stakeholders and capture sign-off date.

tile.json