feature▌

Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.

Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.

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