Choose a skill

Start with one question:

What decision is blocking correct progress right now?

Unresolved decision	Use
What should the product observably do?	product-design
What must the system own or guarantee?	engineering-design
How should the interface expose the behavior?	design-graph
How should the known contract become code?	design-thinking
How can this behavior be proven faithfully?	test-engineering
How do we know production is healthy and recover it?	production-ops
Is this implementation correct and maintainable?	code-review
Did trust, authority, or sensitive data become unsafe?	security-review
Would bounded delegation materially improve the work?	graph-protocol
Is a known relationship easier to understand visually?	call-graph-output

The important boundary

Do not translate:

large task
→ use every skill

Translate:

large task
→ identify independent unresolved decisions
→ use only the skills that own those decisions

Example: new collaborative editor

behavior unclear
→ product-design

ownership + consistency unclear
→ engineering-design

conflict states in UI unclear
→ design-graph

implementation path unclear
→ design-thinking

race/consistency proof unclear
→ test-engineering

If product behavior was already decided, skip product-design. If the existing architecture already gives clear ownership and contracts, skip engineering-design.