btmoriarty/kochab / skills/roadmap-interview
roadmap-interview
VerifiedRun a short product-discovery interview with a user of Kochab to surface what they actually need, then turn it into structured roadmap input. Use when someone says "interview me about features," "run the roadmap interview," "I have feedback on the tool," "what should this tool do next," or when a maintainer wants to gather feature ideas from a user. Produces per-user notes plus an append to a shared feature backlog, so requests that recur across users rise to the top.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/output_template.md | markdown | 1.4 KB |
references/output_template.md
View on GitHub# Roadmap Input: [Name or ID], [YYYY-MM-DD]
*Interview notes. The need is what feeds the roadmap; the stated want is a clue to it.*
## Who they are
- Search stage and shape: [similar role / change / first job in field / move up]
- What a normal week of their search looks like:
- Anything about them that colors what they need:
## The last real application
- What they did, in order:
- Where it got tedious, confusing, or discouraging:
- Done by hand and wished automated:
- Skipped because it was too much work:
## Current experience of the tool
- Used it for:
- Worked well enough to miss:
- Fell short / annoyed / lost trust:
- Almost-quit moment, if any:
## Requests, paired with the need underneath
| Stated want | Why it matters (the need under it) | How strongly they felt it |
|---|---|---|
| | | |
## Reactions to the planned roadmap
| Planned item | Would use it? | Notes |
|---|---|---|
| | | |
Missing from the roadmap that they expected:
Would not bother with:
## Priorities (their ranking)
1.
2.
3.
Rely-on-daily vs. nice-to-have:
## Trust and dealbreakers
- Would have to do / never do, to be trusted:
- Would make them walk away:
## Verbatim worth keeping
>
## Maintainer's read (written after)
- The one or two needs this interview most clearly surfaced:
- Does it confirm or challenge the current roadmap order:
- New candidate for the backlog (fold into `docs/BACKLOG.md`):
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |