continuous-user-research
SKILL.md
Automatically run a lightweight diary study and turn it into weekly product signals and experiment-ready recommendations.
When to use
- The team must decide what to build, fix, or prioritize and needs behavior evidence over time, not one-off opinions.
- A founder or PM asks for scoped weekly learning (for example, onboarding drop-off causes this week).
- You need to compare what people report with what they actually do across days or touchpoints.
- You need low-overhead, repeatable diary loops tied to one explicit research goal.
- You need actionable weekly outputs with direct experiment plans.
When not to use
- The request is only broad brand sentiment with no product decision attached.
- The team needs statistically representative market sizing instead of qualitative behavior understanding.
- The study context is high-risk regulated or sensitive (medical, legal, minors, government) without dedicated compliance design.
- The required data can be answered with existing telemetry alone and no user context is needed.
- You cannot secure participant consent, secure storage, and redaction safeguards.
Security & Permissions
- Minimize access: only access participant contact data, diary entries, and tool scopes required for this study.
- Redact by default: remove names, emails, phone numbers, handles, account IDs, exact addresses, and direct identifiers from all synthesized outputs.