53 skills published by itseffi across 1 repository. Together they weigh 26 464 tokens — that is what loading all of them at once would cost you in context.
53 skills 26 464 tokens total
Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.
Generate rigorous stakeholder challenge questions for proposal or meeting preparation.
Analyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.
Identify the pivotal obstacle between current state and desired future. Use when developing strategy.
Define clear decision rights - Decider, Approver, Veto, Consulted, Informed. Use when clarifying who decides.
Create structured records of decisions with expected outcomes, probabilities, and quit conditions. Use for important decisions.
Classify decisions as Hat/Haircut/Tattoo by reversibility. Use to calibrate how much analysis a decision deserves.
Prepare for challenging conversations using Prepare-Listen-Empathize-Clarify-Solve framework.
Improve executive updates for clarity, decision impact, and concise speaking flow.
Design robust experiments to test product hypotheses. Define metrics, sample size, and success criteria.
Design implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.
Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.
Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.
Identify potential hidden agendas of stakeholders. Use before high-stakes meetings with complex motivations.
Formulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.
Summarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.
Generate influence strategies using Cialdini's seven principles. Use when you need to influence toward an outcome.
Clean up raw interview transcripts while preserving meaning and speaker voice. Use after conducting interviews.
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
Cluster forces from multiple JTBD interviews to identify patterns. Use after extracting from multiple interviews.
Analyze interviews using Jobs to Be Done framework. Extract push, pull, anxiety, and habit forces.
Develop a limit-based product strategy with convergence milestones, acceleration levers, assumptions, and phased execution.
Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.
Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.
Behavioral guardrails to reduce common LLM coding mistakes with a caution-first approach.
Structure thinking using Mutually Exclusive, Collectively Exhaustive categories. Use when breaking down problems or ensuring complete coverage.
Map meeting-specific power dynamics, influence ranking, and tactical recommendations.
Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.
Design audience-specific framing, drafts, and communication sequence for stakeholder updates.
Transform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.
Normalize and collect complete Opportunity Solution Tree inputs before OST synthesis.
Select one target opportunity from an OST using evidence-based weighted scoring and tie-breakers.
Map stakeholders by power and interest to plan engagement strategy. Use when starting multi-stakeholder initiatives.
Write a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.
Break down complex problems into actionable recommendations using deductive and inductive analysis.
Uncover root causes through recursive Why questioning and consequence exploration. Use before acting on problems.
Design efficient early signals to validate assumptions. Find the fastest way to learn if you're right.
Check Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.
Check Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.
Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.
Review a feature or PRD for stakeholder and political risk before broad circulation.
Build a complete product strategy from context, including objective, users, superpowers, vision, pillars, impact, and roadmap.
Four-phase debugging process - root cause first, then fix. Use when encountering bugs or unexpected behavior.
Test-driven development - write failing test first, then minimal code. Use before implementing any feature or bugfix.
Map end-user needs to the full value chain, identify core value generators, and highlight vulnerabilities.
Verify before claiming completion. No claims without fresh verification evidence. Use before marking work done.
Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.