Results for “feature-importance”

Feature Intake

Prioritize features for an MVP or first release. Use when the team has too many ideas and needs must-have vs later vs never-for-v1 decisions tied to the core value loop, user pain, operational shortcuts, and launch feasibility.

Organizes Flutter code by business features instead of technical layers, with self-contained folders for UI, logic, and data, plus a recommended project structure and dependencies.

Rice

The pitch is often "a central place to store features," which undersells it into

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Influence Functions in Deep Learning

**When:** Not important (contact info)

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

Mede o tamanho estrutural da feature ativa lendo requirements, duvidas, plan e tasks do ciclo forward, e gera size.json mais size.md com T-shirt sizing deterministico baseado em tasks e ajuste de risco. Use quando o usuario digitar "/reversa-pricing-size", "reversa-pricing-size", "dimensionar feature" ou "calcular tamanho da feature". Roda depois de `/reversa-to-do` e antes de `/reversa-pricing-estimate`.

分析故事情节点，识别关键情节与转折点。适用于深度分析情节结构、评估情节发展有效性

Guides a structured feature-development workflow: explore the codebase with subagents, draft a plan for approval, implement step by step, verify with parallel checks, and record conventions.

Rank an existing set of context chunks by relevance, diversity, freshness, and utility. Use when retrieval has already produced candidates that must be scored or reranked; use context-retrieval when the source corpus still needs to be searched.

Multi-dimensional lead qualification scoring. Evaluates leads against BANT criteria, firmographic fit, behavioral signals, and intent indicators. Outputs qualified/disqualified verdict with detailed reasoning.

heath-no-fluff

Plan before implementing - understand scope and approach with detailed guidance

SKILL — Brand Systems

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Evaluate a screen's information density by analyzing cognitive load, content prioritization, scanning patterns, and progressive disclosure, with actionable fixes for each dimension.

Apply core PHP language standards and modern 8.x features. Use when working with PHP 8.x features like enums, fibers, readonly properties, or named arguments.