AgentStack
SKILL verified MIT Self-run

Decision Tracing

skill-dragoon0x-taste-skills-decision-tracing · by Dragoon0x

Reverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-dragoon0x-taste-skills-decision-tracing

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Decision Tracing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Decision Tracing

Look at a decision. Figure out why it was made.

How to use

  • /decision-tracing Apply decision-tracing analysis to any design in this conversation.

Constraints

Trace Structure

  • MUST follow: Observation > Decision > Probable Reason
  • "The primary font is Inter" > "They chose a geometric sans-serif" > "Data-heavy product needing maximum legibility at small sizes with neutral personality"
  • MUST generate at least 5 traces per design screen
  • SHOULD acknowledge uncertainty: "probable reason" not "the reason"
  • NEVER state intent as fact unless you have insider knowledge

What to Trace

  • Typeface selection and type system
  • Color palette and color role assignments
  • Layout structure and grid decisions
  • Spacing and density choices
  • Navigation architecture
  • What's absent (what they chose NOT to include)

Anti-Patterns

  • Assuming the most flattering interpretation of every decision
  • Tracing only visual decisions and ignoring structural ones
  • Stating reasons as facts without marking them as hypotheses

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.