Loading...
Loading...
Found 19 Skills
Articulate a compelling north-star product vision that aligns teams and inspires strategic design decisions.
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohes
Help users create compelling product visions. Use when someone is writing a vision statement, defining a long-term product direction, aligning teams on the future state, or distinguishing vision from strategy.
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
Skill for defining terminology and data structures used throughout the project. Covers domain terminology, entities, relationships, and schema design. Use proactively when starting a new project or when data structures are unclear. Triggers: schema, terminology, data model, entity, 스키마, 用語, データモデル, 数据模型, esquema, terminología, modelo de datos, schéma, terminologie, modèle de données, Schema, Terminologie, Datenmodell, schema, terminologia, modello dati Do NOT use for: UI-only changes, deployment, or when schema is already defined.
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
Use to link segments and insights to GTM plays, owners, and measurement plans.
Use when teams need shared direction and decision-making alignment. Invoke when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or setting behavioral standards. Use when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.
Clarify the outcome you want - a change in user behavior, not a feature shipped. Use at the start of any work to ground the session in strategic intent.