itseffi/agentic-os
52 skills
$npx skills add itseffi/agentic-osSkillInstalls
assumption-mappingSurface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.assumption-prioritizationPrioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.atlassian-jira-syncSync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.backend-designDesign backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.brainstormingTurn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.challenging-stakeholder-questionsGenerate rigorous stakeholder challenge questions for proposal or meeting preparation.competitor-analysisAnalyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.crux-diagnosisIdentify the pivotal obstacle between current state and desired future. Use when developing strategy.davciDefine clear decision rights - Decider, Approver, Veto, Consulted, Informed. Use when clarifying who decides.decision-journalCreate structured records of decisions with expected outcomes, probabilities, and quit conditions. Use for important decisions.decision-reversibilityClassify decisions as Hat/Haircut/Tattoo by reversibility. Use to calibrate how much analysis a decision deserves.difficult-conversationsPrepare for challenging conversations using Prepare-Listen-Empathize-Clarify-Solve framework.executive-update-reviewImprove executive updates for clarity, decision impact, and concise speaking flow.experiment-designDesign robust experiments to test product hypotheses. Define metrics, sample size, and success criteria.frontend-designDesign implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.google-calendar-schedule-checkCheck Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.granola-meeting-syncSync 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.hidden-agendasIdentify potential hidden agendas of stakeholders. Use before high-stakes meetings with complex motivations.hypothesis-designFormulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.ideas-summarySummarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.influence-strategiesGenerate influence strategies using Cialdini's seven principles. Use when you need to influence toward an outcome.interview-cleanupClean up raw interview transcripts while preserving meaning and speaker voice. Use after conducting interviews.issue-syncSync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.jira-syncSync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.jtbd-clusteringCluster forces from multiple JTBD interviews to identify patterns. Use after extracting from multiple interviews.jtbd-extractionAnalyze interviews using Jobs to Be Done framework. Extract push, pull, anxiety, and habit forces.limit-based-strategyDevelop a limit-based product strategy with convergence milestones, acceleration levers, assumptions, and phased execution.linear-issue-syncSync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.llm-coding-guardrailsBehavioral guardrails to reduce common LLM coding mistakes with a caution-first approach.mece-analysisStructure thinking using Mutually Exclusive, Collectively Exhaustive categories. Use when breaking down problems or ensuring complete coverage.meeting-power-dynamicsMap meeting-specific power dynamics, influence ranking, and tactical recommendations.meeting-syncSync 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.message-checkCheck Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.message-framing-commsDesign audience-specific framing, drafts, and communication sequence for stakeholder updates.opportunity-solution-treeTransform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.ost-intakeNormalize and collect complete Opportunity Solution Tree inputs before OST synthesis.ost-target-selectionSelect one target opportunity from an OST using evidence-based weighted scoring and tie-breakers.power-mapprd-writingWrite a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.problem-structuringBreak down complex problems into actionable recommendations using deductive and inductive analysis.root-cause-analysisUncover root causes through recursive Why questioning and consequence exploration. Use before acting on problems.schedule-checkCheck Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.signal-identificationDesign efficient early signals to validate assumptions. Find the fastest way to learn if you're right.slack-message-checkCheck Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.spec-writingConvert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.stakeholder-risk-reviewReview a feature or PRD for stakeholder and political risk before broad circulation.structured-product-strategyBuild a complete product strategy from context, including objective, users, superpowers, vision, pillars, impact, and roadmap.systematic-debuggingFour-phase debugging process - root cause first, then fix. Use when encountering bugs or unexpected behavior.tddTest-driven development - write failing test first, then minimal code. Use before implementing any feature or bugfix.value-chain-mappingMap end-user needs to the full value chain, identify core value generators, and highlight vulnerabilities.verificationVerify before claiming completion. No claims without fresh verification evidence. Use before marking work done.writing-plansCreate comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.