Plugins

3 plugins

Feature Development Pipeline

Plan, execute, and verify a feature using structured planning, gated pipeline, and issue tracking.

10 skills · plugin

TDD Feature Development

Drive feature development by writing tests first, implementing, verifying, and committing via a gated pipeline.

10 skills · plugin

Code-writing and execution skills for the Han suite. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate. Depends on han-core and han-communication; bundled by the han meta-plugin.

11 skills · plugin

Results for “feature-gate”

3 skills

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

More results

srednoff888-art

SEO CI Quality Gate

Use this skill for SEO checks in CI, metadata, canonicals, links, robots, sitemap, noindex regressions. Trigger when the task involves seo work related to SEO CI Quality Gate, implementation, audits, debugging, strategy, or validation.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.