request-discovery

Identify untracked feature requests from Intercom and validate them against Shortcut, codebase, and PostHog.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulyokota/FeedForward --skill request-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-discovery
Source: https://github.com/paulyokota/FeedForward/tree/main/.claude/skills/request-discovery
Command: npx skills add https://github.com/paulyokota/FeedForward --skill request-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Find untracked feature requests or latent product gaps in Intercom and ensure they are not already tracked, then validate against the codebase and PostHog to prepare a Shortcut card.

Core Features & Use Cases

  • Validate explicit requests and latent gaps across product areas.
  • Cross-check against codebase and PostHog for contextual accuracy.
  • Produce a complete Shortcut card ready for review and backlog integration.

Quick Start

Identify a candidate feature gap from Intercom and generate a Backlog-ready Shortcut card.

Frequently Asked Questions about request-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find untracked feature requests from Intercom to add to my Shortcut backlog?

You can uncover untracked feature requests by analyzing Intercom conversations to discover latent product gaps, then validating those candidates against the codebase and PostHog to confirm relevance before creating a Shortcut card.

What is the best way to validate latent product gaps before creating a Shortcut card?

The best way to validate latent product gaps is by cross-checking candidate feature requests against the codebase and PostHog usage data to ensure contextual accuracy and confirm the gap is not already tracked in Shortcut.

How do I generate a complete Shortcut card draft from customer conversations?

Generate a complete Shortcut card draft by processing validated feature requests into a structured output that includes the title, scope, acceptance criteria, and recommended backlog actions for review.

Can I use PostHog and codebase data to verify feature request relevance?

PostHog and codebase data are used to validate feature request candidates by confirming usage context and checking technical relevance, ensuring that only verified product gaps are prepared for Shortcut backlog integration.

How to check if a feature request is already tracked in Shortcut?

Check if a feature request is already tracked by validating the candidate gap against existing Shortcut entries, ensuring that only untracked requests are processed into new backlog card drafts.