Plugins

7 plugins

Planning & Product

PRDs, roadmaps, OKRs, discovery and product strategy.

23 skills · plugin

Create Product Strategy

Create a product strategy by analyzing market, defining vision, and generating a strategic plan.

3 skills · plugin

PRD to Implementation Plan

Transform a raw product idea into a structured PRD and then into a technical implementation plan with issues.

11 skills · plugin

Product Idea Validation

Install this pack to transform a raw product idea into clarifying questions, deep research, a PRD, and a phased execution plan with kill criteria.

6 skills · plugin

Multi-Channel Campaign Launch

Research audience, plan campaign, create content, and publish across channels for a product launch.

8 skills · plugin

Safe Production Deployment

Deploy a web application safely with pre-deployment audit, rollout plan, canary monitoring, and rollback strategy.

9 skills · plugin

Redpanda Data Skills

Agent Skills for Redpanda's five products — Streaming (Kafka-compatible engine), SQL (Oxla), Connect (incl. CDC connectors), Cloud (Serverless, BYOC, Dedicated), and the Agentic Data Plane — plus the rpk CLI. Grounded in Redpanda source, docs, and APIs.

32 skills · plugin

Results for “product-plan”

9 skills

Interface Designer

Plans interface structure, component layout, and interaction details for product flows before implementation.

Product Builder Orchestrator

Use when the request is broad and spans idea evaluation, MVP planning, UX, frontend, backend, database, auth, integrations, and launch strategy. Trigger on asks like "build this app", "turn this idea into a product", "design the whole system", or "plan everything end to end".

Responsive Design Planner

Use when a web product or component needs responsive layout planning across mobile, tablet, and desktop. Trigger on requests about breakpoints, layout adaptation, content priority, or mobile-first UI behavior.

Frontend Scaffold Planner

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

More results

Plan screens, views, and page responsibilities for a product flow. Use when user journeys already exist and the team needs a screen inventory, screen purpose, key states, and component-level responsibilities without jumping into visual styling too early.

Plans, builds, and deploys a complete Ethereum dApp using a three-phase build system with local fork, testnet, and production stages, plus a secret safety protocol and ERC-8004/x402 commerce flow.

App Store Optimization for mobile launches (iOS App Store, Google Play). Use when preparing a mobile app launch, optimizing app store listings, planning screenshot sequences, writing app store copy, doing keyword research for app stores, planning preview videos, managing reviews, or A/B testing app store assets. Relevant for Expo/React Native apps going to stores. Not for web-only products.

Design finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "implement this design", or after any planning skill. Proactively suggest when user has approved a design or has a plan ready. (gstack) Voice triggers (speech-to-text aliases): "build the design", "code the mockup", "make it real".

Conduct a design interview, generate 5 distinct UI variations in a temporary route, collect real click-to-comment feedback on the live rendered variants via human-review, and produce an implementation plan. Use when the user wants to explore UI design options, redesign an existing component/page, or create new UI with multiple genuinely different approaches to compare — before writing production code or committing to a direction. For a lighter, single-component variant picker with no interview, use `prototype` instead. For reviewing a UI that's already real (not exploring new directions), use `visual-review`. Source: adapted from github.com/0xdesign/design-plugin's design-lab skill (interview + 5-variant structure), with feedback collection replaced by this repo's own `visual-review` skill (human-review) instead of a bespoke overlay component.