LogoSkills

dops-handoff

Generate a developer handoff package for a design.

ํ•ญ๋ชฉ๋‚ด์šฉ
Invoke/dops-handoff
argument-hint[screen, feature, or component to hand off]

/dops-handoff โ€” ๊ฐœ๋ฐœ์ž ํ•ธ๋“œ์˜คํ”„ ํŒจํ‚ค์ง€ ๋งŒ๋“ค๊ธฐ#

ํ•œ๋งˆ๋””๋กœ#

๋””์ž์ธ์„ ๊ฐœ๋ฐœ์ž์—๊ฒŒ ๋„˜๊ธธ ๋•Œ ํ•„์š”ํ•œ ๋ชจ๋“  ์ž๋ฃŒ(์น˜์ˆ˜, ๋™์ž‘ ๋ฐฉ์‹, ์—์…‹, ์ฒดํฌ๋ฆฌ์ŠคํŠธ)๋ฅผ ํ•œ ๋ฒˆ์— ๋ฌถ์–ด์ฃผ๋Š” ๋ช…๋ น์ž…๋‹ˆ๋‹ค.

๋ˆ„๊ฐ€ยท์–ธ์ œ ์“ฐ๋‚˜์š”#

  • ํ™”๋ฉดยท๊ธฐ๋Šฅยท์ปดํฌ๋„ŒํŠธ๋ฅผ ๊ฐœ๋ฐœํŒ€์— ์ „๋‹ฌํ•˜๊ธฐ ์ง์ „
  • ํ•ธ๋“œ์˜คํ”„ ์ž๋ฃŒ๋ฅผ ๋น ์ง์—†์ด ์ฑ™๊ฒผ๋Š”์ง€ ํ™•์ธํ•˜๊ณ  ์‹ถ์„ ๋•Œ

๋ฌด์—‡์„ ํ•ด์ฃผ๋‚˜์š”#

  • ์‹œ๊ฐ/์ƒํ˜ธ์ž‘์šฉ ์ŠคํŽ™, QA ์ฒดํฌ๋ฆฌ์ŠคํŠธ, ๋ฆฌ๋ทฐ ์ค€๋น„ ์ƒํƒœ, ๋ฒ„์ „ ์ •๋ณด๋ฅผ ์ •๋ฆฌํ•œ ์™„์„ฑ๋œ ํ•ธ๋“œ์˜คํ”„ ํŒจํ‚ค์ง€๋ฅผ ๋งŒ๋“ค์–ด ์ค๋‹ˆ๋‹ค.
  • ์—์…‹ ๋ชฉ๋ก๊ณผ ๊ตฌํ˜„ ์ฐธ๊ณ  ์‚ฌํ•ญ๊นŒ์ง€ ํ•จ๊ป˜ ์ปดํŒŒ์ผํ•ฉ๋‹ˆ๋‹ค.

โš™๏ธ ์ƒ์„ธ ์˜ต์…˜ยท์‹คํ–‰ ๋ช…์„ธ (๊ฐœ๋ฐœ์ž / AI ์—์ด์ „ํŠธ์šฉ)

/handoff#

Generate a developer handoff package.

Steps#

  1. Visual specs โ€” Document all measurements and tokens using dops-handoff-spec skill.
  2. Interaction specs โ€” Define states and behaviors using dops-handoff-spec skill.
  3. QA criteria โ€” Create implementation checklist using dops-qa-checklist skill.
  4. Review readiness โ€” Verify against review criteria using dops-review-process skill.
  5. Version โ€” Tag the design version being handed off using dops-version-control skill.
  6. Package โ€” Compile all specs, assets, and notes.

Output#

Complete handoff package with visual specs, interaction specs, asset list, QA checklist, and implementation notes. Consider following up with /dops-setup-workflow to establish the ongoing QA process.