feature▌
27 indexed skills · max 10 per page
bdd-feature-generator
moxa/sw · Productivity
bdd-feature-generator
create-github-issue-feature-from-specification
github/awesome-copilot · Productivity
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
feature-flag-system
aj-geddes/useful-ai-prompts · Productivity
Implement feature flags to decouple deployment from release, enable gradual rollouts, A/B testing, and provide emergency kill switches.
feature-engineering
aj-geddes/useful-ai-prompts · Productivity
Feature engineering creates and transforms features to improve model performance, interpretability, and generalization through domain knowledge and mathematical transformations.
feature-sliced-design
aiko-atami/fsd · Frontend
An architectural methodology skill for scaffolding and organizing frontend applications using Feature-Sliced Design principles.
breakdown-feature-implementation
github/awesome-copilot · Productivity
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
parallel-feature-development
wshobson/agents · Productivity
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