feature-strategist

Reclassify features.json audit outputs into PRIMARY/SECONDARY/TERTIARY marketing priorities with marketingHook generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill feature-strategist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-strategist
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/feature-strategist
Command: npx skills add https://github.com/Swear4/agent_rules --skill feature-strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Feature Strategist helps product teams turn raw feature classifications into market-driven priorities, enabling sales enablement and aligned roadmaps.

Core Features & Use Cases

  • Reclassify features by marketing priority (PRIMARY/SECONDARY/TERTIARY) to guide pitches, site messaging, and sales conversations.
  • Enforce quotas, produce a changelog, and generate marketingHook entries for PRIMARY and SECONDARY features.
  • Validate input quality, detect red flags, and safely update features.json with governance and product-stage biases.

Quick Start

Run the feature-strategist on your current features.json to reclassify priorities and generate marketingHook.

Frequently Asked Questions about feature-strategist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize features for marketing and sales pitches?

To prioritize features for marketing pitches, you reclassify raw features from your audit outputs into PRIMARY, SECONDARY, and TERTIARY tiers, generating targeted messaging hooks to drive sales conversations.

How do I generate marketing hooks from a features.json file?

Generating marketing hooks from a features.json file involves reclassifying features by marketing priority and automatically creating marketingHook entries for PRIMARY and SECONDARY features while enforcing quota constraints.

Do I need an existing features.json audit file before feature reclassification?

Yes, feature reclassification requires an existing features.json file typically generated by a prior audit-master run, ensuring raw features exist to classify into marketing priorities with proper codebase map integration.

What's the best way to align product roadmaps with sales enablement messaging?

Aligning roadmaps with sales enablement involves classifying features by marketing priority, enforcing governance and product-stage biases, and producing a changelog to safely update features.json with pitch-ready messaging.

When should I enforce quota constraints during feature prioritization?

Quota constraints are enforced during feature prioritization to limit the number of PRIMARY and SECONDARY classifications, ensuring marketing messaging remains focused and preventing feature overload in sales pitches.

Why does my features.json update require a changelog and red flag detection?

Updating features.json requires a changelog and red flag detection to maintain governance, validate input quality, and ensure priority reclassifications safely integrate with existing codebase maps and product stage biases.