feature▌

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

Create GitHub issues from specification files using the feature_request.yml template. \n \n Analyzes specification files to extract requirements and automatically generates issue titles and descriptions \n Searches existing issues to prevent duplicates before creating new ones \n Supports both creating new issues and updating existing ones via the GitHub API \n Applies feature and enhancement labels automatically based on specification content \n

Implement feature flags to decouple deployment from release, enable gradual rollouts, A/B testing, and provide emergency kill switches.

Feature engineering creates and transforms features to improve model performance, interpretability, and generalization through domain knowledge and mathematical transformations.

An architectural methodology skill for scaffolding and organizing frontend applications using Feature-Sliced Design principles.

Detailed feature implementation plan generator following Epoch monorepo conventions. \n \n Generates comprehensive markdown implementation plans with system architecture, database schema, and API design specifications \n Includes Mermaid diagrams for system architecture, entity relationships, and component hierarchies with shadcn/ui integration \n Covers frontend component structure, state management patterns, backend service design, and deployment strategies \n Outputs structured plans to /docs

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns. \n \n Provides three file ownership models (by directory, module, or layer) and enforces the cardinal rule: one owner per file to prevent merge conflicts \n Defines interface contracts as read-only coordination points between implementers, allowing shared boundaries without direct file conflicts \n Covers two integration patterns (vertical slice for independent features, ho