feature▌

Source: fsd.how | Strictness can be adjusted based on project scale and team context.

Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach:

Categorize, evaluate, and prioritize customer feature requests against product goals.

Structured dialogue tool for collaboratively designing features, APIs, and architecture through phased information gathering and validation. \n \n Guides through six phases: context discovery, requirements gathering, approach exploration, design presentation, documentation, and execution handoff \n Uses batched multi-question prompts to efficiently collect requirements across core goals, technical layers, quality attributes, integrations, and dependencies \n Generates 2-3 design approach options

Extract product features from UI screenshots using a coordinated multi-agent analysis pipeline.

sentry-feature-setup

Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value. \n \n Guides product managers through a structured 4-step assessment: revenue connection (direct monetization, retention, conversion, expansion), cost structure (dev + COGS + OpEx), constraint evaluation, and ROI calculation \n Delivers one of four recommendation patterns: build now (strong ROI), build for strategic reasons (marginal ROI but competitive/platform value), don't build (poor ROI), or build l

Manage React feature flags across channels, gate tests conditionally, and debug flag-specific test failures. \n \n Four flag files control defaults and channel-specific overrides (canary, www, React Native, test renderer) with __VARIANT__ flags simulating gatekeepers tested in both states \n Use @gate flagName pragma to skip tests entirely when a flag is unavailable, or inline gate() to branch assertions when behavior differs \n Adding a new flag requires entries in the main file plus all fork f

Structured requirements workshops that produce EARS-format specifications, user stories, acceptance criteria, and implementation checklists. \n \n Conducts systematic discovery interviews from both product and engineering perspectives, using structured questioning to elicit requirements before writing specifications \n Outputs comprehensive specifications including functional requirements in EARS format, non-functional requirements, Given/When/Then acceptance criteria, error handling tables, and

Stay focused on core problems, ship faster, and avoid bloated products through disciplined scope management. \n \n Provides a five-step decision framework (validate problem, check alignment, measure impact, assess complexity, gut check) to evaluate every feature request before building \n Includes scope management rules: define your MVP upfront, track scope changes like code, apply a 48-hour waiting period for new requests, and use budget-based trade-offs to prevent additions \n Offers templates