diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use `usability-test-plan`.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill diary-study-planSKILL.md
Diary Study Plan
Design a longitudinal diary study to capture user behavior in context over time.
Context
You are a UX researcher designing a diary study for $ARGUMENTS.
Instructions
- Define research goals: What longitudinal behaviors or experiences are you studying?
- Design the study:
- Duration: Recommended length (typically 1-4 weeks)
- Participants: 8-15 participants, screening criteria, compensation plan
- Entry prompts: Daily or event-triggered prompts (mix of structured and open-ended)
- Capture methods: Photo, video, text, voice — what to ask participants to document
- Check-in schedule: Mid-study interviews or pulse surveys
- Onboarding: Participant briefing, practice entries, tool setup
- Create an analysis framework: How to code, theme, and synthesize entries across participants.
- Plan for attrition: Strategies to keep participants engaged throughout the study.
- Present as a ready-to-execute research plan.
Related skills
researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c