Scaffold or update a structured feedback interview log with an NC firearms instructor. Use before or after the user talks to an instructor and needs a consistent template for capturing what was said and what it means for the platform.
When the user runs /instructor-interview (with an optional argument for the instructor's name), create or update an interview log.
The argument is the instructor's name or call sign. If none is provided, ask who the interview is for before writing anything.
Create interviews/YYYY-MM-DD-<slug>.md where:
YYYY-MM-DD is today's absolute date<slug> is the instructor's name lowercased, with spaces → dashes (e.g., "John Smith" → john-smith)If the file already exists, open and extend it rather than overwriting.
# Interview: [Name]
- **Date**: YYYY-MM-DD
- **Medium**: phone | in-person | video
- **Instructor profile**:
- Years certified:
- NC DOJ cert status:
- Typical class volume (students/month):
- Specializations: (concealed carry, tactical, hunter safety, etc.)
- Current business size: (solo / small school / multi-instructor)
- **Current tools**: what they're using today for scheduling, rosters, payments, marketing, waivers
## Questions asked
1. ...
## Answers captured
Quote the instructor's own phrasing when it's distinctive. Paraphrase only when the original isn't verbatim-available.
## Pain points
- ...
## Feature signals
- Which capabilities resonated?
- Which felt like solutions looking for a problem?
## Pricing sensitivity
- Reaction to Solo $49/mo and Pro $89/mo tiers
- Willingness to pay for: ...
- Dealbreakers: ...
## 2A / payments / compliance concerns
- Any reaction to TacticalPay / Authorize.net vs. Stripe?
- Concerns about debanking, data privacy, or state regs?
## Interpretation
(Your read on what this interview means — kept separate from what was actually said.)
## Followups
- [ ] ...
## Interpretation section is for the latter.n/a or leave blank — never fabricate a quote.