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
Securityby
Passed
No known issues
categorization-decision-tree.mdmoscow-prioritization/references/
Categorization Decision Tree
Use these questions in order for every requirement.
- Is it legally or contractually required?
- Does the product fail to deliver core value without it?
- Does absence block release approval or market entry?
- Can it be deferred one release with acceptable risk?
Mapping Rules
- If 1-3 are
yes, classify asMust. - If 4 is
yesand value is high, classify asShould. - If value is moderate or low and deferrable, classify as
Could. - If out of scope now, classify as
Won'twith revisit trigger.
Must Challenge Questions
- "What breaks on release day if this is missing?"
- "Can a temporary workaround cover this release?"
- "Is the impact legal, security, revenue-critical, or reputation-critical?"
If answers are vague, downgrade from Must and document rationale.