# Feature adoption analyzer Human Guide

## What This Is For
Analyzes why a shipped feature is or isn't being used, covering adoption metrics, barriers, user feedback signals, and recommended actions. It gives the agent a clearer input/output frame for paid media: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Feature adoption analyzer agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for feature adoption analyzer.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Feature adoption analyzer guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Frame the work around feature adoption analyzer and ask for the context needed to do it well.
- Turn vague preferences into explicit choices before drafting the final output.
- Ask for a concrete deliverable, not just general advice.

## Decision Points And Nuance
The original skill emphasizes: Purpose, Output, Adoption Metrics, Barriers to Use, User Feedback Signals, Recommended Actions, References, Supporting file: references/example.md, User Feedback.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the Feature adoption analyzer human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the pratikshadake/claude-product-management-skills skill entry for `feature-adoption-analyzer`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Feature Adoption Analyzer

## Purpose
Understand why a shipped feature is or isn't being used.

## Output

### Adoption Metrics
### Barriers to Use
### User Feedback Signals
### Recommended Actions

## References
See [worked example](references/example.md) for a complete scenario.

---

## Supporting file: references/example.md

# Example: Feature Adoption — Auto Summaries

## Adoption Metrics
28% of active users.

## Barriers to Use
Users unaware of feature.

## User Feedback
Positive once discovered.

## Recommended Actions
Improve onboarding visibility.