Loading...
Loading...
Found 108 Skills
Estrategista de produto no SynkOS. Use esta skill quando o usuário pedir para criar ou atualizar um PRD (Product Requirements Document), priorizar o backlog por valor de negócio, criar épicos, alinhar decisões com stakeholders, ou fazer perguntas como "atualize o PRD com X", "priorize o backlog", "crie um épico para Y", "quais itens têm maior impacto?", "como comunicar esse tradeoff ao cliente?", "o backlog está alinhado com os objetivos de produto?". Ative também para planejamento estratégico de releases, definição de OKRs ou critérios de sucesso de produto, e para detectar lacunas de escopo que virarão novos itens de backlog.
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of Constraints), prioritized questions and open decisions, a ranked action plan with the critical effort plus follow-ons, risks and pre-mortem, copy/paste prompts for downstream pm-skills, and an evidence map. Builds a source ledger and cites exact input quotes; refuses High-confidence plans for Complex or Chaotic situations. Use when you want the critical next effort and how to execute it.
Guide product managers through creating an Opportunity Solution Tree (OST) by extracting target outcomes from stakeholder requests, generating opportunity options (problems to solve), mapping potentia
Coaches PMs and new Directors through the transition from individual contributor to organizational leader across four situations: preparing, interviewing, newly landed, or recalibrating.
The core mental model for the PM-to-Director transition: altitude (scope) and horizon (time), the waiter-to-operator shift, four transition zones, named failure modes, and the Cascading Context Map.
Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
This skill should be used when the user needs to structure what to build and when by converting discovery opportunities into prioritized bets and roadmaps. Use when organizing product capability blocks, writing solution briefs, planning quarterly cycles, or communicating product direction without false precision.
Structurally deconstruct competitors from four dimensions: strategy, functionality, experience, and growth, and output referenceable points, non-replicable points, and differentiation suggestions. Use this Skill when users say "competitor analysis", "competitor deconstruction", "help me analyze competitors", "take a look at these competitors", "compare with competitors", "benchmarking analysis", "how to do differentiation", or when users provide a list of competitors and require systematic analysis. Also applicable for: users upload competitor screenshots/links/experience reports and require structured deconstruction; users require comparison of gaps between their own products and competitors; users want to find differentiation entry points. Not applicable for: pure requirement document writing (use prd-writer), pure priority sorting (use prioritization-engine), pure user research design (use survey-designer).
Create Product Requirements Documents (PRDs) that define the end state of a feature through iterative design interview. Use when planning new features, migrations, or refactors. Generates structured PRDs with acceptance criteria, testing strategy, and architectural decisions.
This skill should be activated when the user requests to "create PRD", "write product requirements document", "generate PRD", "new PRD" (either in Chinese or English), or mentions "product requirements document" or "PRD template". It automatically generates comprehensive Chinese PRD documents in accordance with 2026 best practices.
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, migrations, performance, documentation, or any other work type. Triggers: spec, requirements, define scope, what to build.