Generate single-file feature documentation with verified test cases. Use for quick feature docs, feature README, any project (not enterprise modules).
Score 70/100
Эксперт feature documentation. Используй для документации функций, release notes, user guides и product documentation.
Score 70/100
Create clear feature documentation for non-professional developers. Use PROACTIVELY when documenting new features, significant code changes, creating technical specifications, or…
Score 70/100
Comprehensive feature engineering for ML pipelines: data quality assessment, feature creation, selection, transformation, and encoding.
Score 70/100
Create and transform features using encoding, scaling, polynomial features, and domain-specific transformations for improved model performance and interpretability
Score 70/100
Techniques de feature engineering pour améliorer les modèles ML. Se déclenche avec "feature engineering", "features", "transformation de données", "encoding", "normalisation",…
Score 70/100
Feature Engineering Helper - Auto-activating skill for ML Training. Triggers on: feature engineering helper, feature engineering helper Part of the ML Training skill category.
Score 70/100
Auto-generate features with encodings, scaling, polynomial features, and interaction terms for ML pipelines.
Score 70/100
Discovers KrakenD features, checks edition availability (CE vs EE), and provides implementation examples
Score 70/100
Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for…
Score 70/100
Implement environment-safe feature flags using Custom Metadata Types for Apex, LWC, and Flow. NOT for user-level entitlements or permission sets.
Score 70/100
Automate the complete lifecycle of feature flags in Saberloop, following Epic 10 hygiene standards
Score 70/100
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
Score 70/100
Integrate feature flagging into the React component lifecycle for safe continuous delivery.
Score 70/100
Concevoir et implémenter un système de feature flags pour des déploiements progressifs, A/B testing, canary releases et kill switches.
Score 70/100
Use when implementing runtime feature toggles, emergency kill switches, or gradual rollout controls in Apex using Custom Metadata Types, Custom Permissions, or Hierarchical Custom…
Score 70/100
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Score 70/100
Database-backed feature flag systems in the Orient. Use when implementing feature flags, debugging flag-related issues, or understanding the flag hierarchy.
Score 70/100
Gestion de feature toggles avec LaunchDarkly, OpenFeature et implémentations custom pour le déploiement progressif et l'A/B testing.
Score 70/100
Guides a user through DDD → BDD → TDD → Git for a single feature, staying code-agnostic and interactive.
Score 70/100
Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation…
Score 70/100
Assemble the command registry so optional modules only load when their feature flag is enabled and the registry is accessed.
Score 70/100
React Native Feature 模块生成指南。当用户提到"创建 feature"、"新建模块"、"生成功能"、"添加功能模块"、"feature 模板"时使用此 skill。
Score 70/100
Helps non-technical Claude users instantly understand any Claude feature or capability.
Score 70/100
Product strategist for scoring and ranking feature ideas using RICE/ICE prioritization frameworks, connecting features to business KPIs (retention, growth, revenue), and…
Score 70/100
New feature implementation. Use for 'add feature', 'implement', 'new feature' requests
Score 70/100
Comprehensive checklist for implementing new features in Ishkul. Ensures all aspects are covered including frontend, backend, tests, E2E tests, infrastructure, and documentation.
Score 70/100
Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.
Score 70/100
Feature Importance Analyzer - Auto-activating skill for ML Training. Triggers on: feature importance analyzer, feature importance analyzer Part of the ML Training skill category.
Score 70/100
Develop features in isolated git worktrees with autonomous testing and iteration. Use when the user asks to develop a feature in a separate worktree, wants isolated feature…
Score 70/100
Investigate and explain how existing features/logic work. READ-ONLY exploration. Triggers: how does, explain, what is the logic, investigate, understand, where is, trace, walk…
Score 70/100
Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works.
Score 70/100
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.
Score 70/100
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and…
Score 70/100
Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship.
Score 70/100
Convert PRD requirements into structured epics, features, and user stories with acceptance criteria and priority rankings
Score 70/100
Implements a single task following the next → implement → check → done workflow with TDD support. Use when working on one specific task, implementing a single feature from the…
Score 70/100
Story orchestration with progress tracking, standardized directory structure, and validation
Score 70/100
Research-backed feature implementation workflow enforcing gap analysis, incremental planning, agent coordination, and continuous integration best practices.
Score 70/100
Plan feature implementation with technical specifications and actionable steps for solo developers
Score 70/100
Creates phase-based feature plans with quality gates and incremental delivery structure. Use when planning features, organizing work, breaking down tasks, creating roadmaps, or…
Score 70/100
Use after research (Z01 files exist) to create implementation plan - follow structured workflow
Score 70/100
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Score 70/100
RICE scoring framework for ruthless feature prioritization. Evaluates features against strategic objectives, customer value, and resource constraints.
Score 70/100
Transform overwhelming client feature wish lists into structured MVP/Phase 2/Phase 3 plans with time estimates, preventing scope creep and creating profitable upsell opportunities.
Score 70/100
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
Score 70/100
Review and prioritize features using RICE, WSJF, or Kano scoring frameworks, then create GitHub issues for suggestions.
Score 70/100
Scoping group skill. Translates the chosen solution direction and top risks into a tight, build-able scope with explicit in/out boundaries per area.
Score 70/100
Apply Feature-Sliced Design (FSD) architecture to frontend projects. Triggers on: FSD, feature slicing, frontend architecture, layer structure, module boundaries, scalable…
Score 70/100
Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.
Score 70/100
Draft detailed engineering specs from an approved PRD. Use when generating or updating the engineering specification for a feature, before implementation begins.
Score 70/100
Review and score engineering specs against a startup-focused quality rubric. Penalize over-engineering and reward simplicity.
Score 70/100
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
Score 70/100
Create feature spec files from project docs, commit and push to main, and create matching feature branches from main.
Score 70/100
Reviews feature specifications for completeness, testability, and implementation readiness. Validates acceptance criteria, edge cases, and technical constraints.
Score 70/100
Creates focused feature specifications with user stories, acceptance criteria, and edge cases. Lighter than PRD, focuses on single feature implementation.
Score 70/100
Count features marked as @failing and write to status JSON file. Used to determine when the autonomous coding loop should end.
Score 70/100
Feature Store Connector - Auto-activating skill for ML Deployment. Triggers on: feature store connector, feature store connector Part of the ML Deployment skill category.
Score 70/100
Plan and communicate a feature or product end-of-life. Use when deprecating features, sunsetting products, or managing migration off legacy systems.
Score 70/100
Feature switch system guide for gating new user-facing features behind feature flags
Score 70/100