Lisa Tracker Source Artifacts

Canonical, vendor-neutral taxonomy and rules for handling source artifacts (Figma, Lovable, Loom, screenshots, design docs, data samples) when generating or evaluating tracker tickets (JIRA, GitHub Issues, Linear). Defines: (1) artifact domains, (2) classification rules per tool, (3) source precedence (which artifact is authoritative for which question), (4) inheritance from epic to story to sub-task, (5) cross-axis conflict handling. Invoke this skill from any flow that extracts, attaches, or reasons about external design/UX/data artifacts so the rules don't drift across skills.

codyswanngt Updated 5 repo stars

File contents

codyswanngt/advisory-rankings commit e8531c014d

Frequently asked questions

npx get-skill add codyswanngt/lisa-tracker-source-artifacts-2