القائمة
Designs user behavior events, state change logs, operational records, KPI links, privacy cautions, and information that should not be recorded.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Writes testable acceptance criteria using Given/When/Then, linking each AC to requirement, priority, operating intent, scalability, screen data-req-id, policy ID, and measurement/logging ID.
Extracts reusable patterns from competitor or reference examples without copying them, then rates Must-have/Nice-to-have fit as Green, Yellow, or Red.
Records why product decisions were made, including question, choices, user selection, recommendation, deferred alternatives, policy links, measurement links, and AC links.
Writes Claude Design handoff briefs and prototype prompts from confirmed product decisions, including screens, actions, states, policies, measurement requirements, Must-have/Nice-to-have priority, operating intent, scalability, and unresolved items.
Extracts permission policies, state policies, input policies, restrictions, notification rules, search/filter policies, operating policies, exceptions, and retention rules.
Writes PRD sections from confirmed product decisions, including problem, goals, users, journey, feature requirements with Must-have/Nice-to-have priority, operating intent, scalability, policies, measurement, risks, and unresolved items.
| name | measurement-designer |
| description | Designs user behavior events, state change logs, operational records, KPI links, privacy cautions, and information that should not be recorded. |
Design user behavior events, state change logs, operational records, and KPI links.
Use the Core User Flow when deciding what to measure:
Ask whether key actions should be recorded.
Example:
이 버튼을 눌렀다는 기록을 남겨야 하나요?
A. 기록하지 않는다
B. 클릭 여부만 기록한다
C. 클릭, 결과, 실패 사유까지 기록한다
D. 잘 모르겠음
내 추천:
B. 클릭 여부만 기록한다.
추천 이유:
첫 버전에서는 핵심 기능이 실제로 쓰이는지 먼저 확인하는 것이 좋다.
data-req-id