tomaszstaniak
UserAgent skills for Claude Code and agentskills.io-compatible agents
Categories
Indexed Skills (8)
continuous-discovery-habits
Product discovery framework based on Teresa Torres' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing assumption tests before committing to a feature, (4) writing or critiquing interview snapshots from customer conversations, (5) generating multiple solution candidates for an opportunity (especially with How Might We), (6) mapping a current-state customer experience or journey to surface unmet needs, (7) diagnosing why a product team is shipping without moving outcomes, (8) running a discovery pre-mortem before committing to a solution branch, (9) building or strengthening a weekly customer-interview habit, (10) connecting business outcomes to product outcomes to opportunities to solutions in a coherent tree.
escaping-build-trap
Product management framework based on Melissa Perri's "Escaping the Build Trap". Use this skill whenever the user is discussing product strategy, roadmap construction, product team maturity, or symptoms of feature-factory behavior — even if they do not explicitly say "build trap" or "outcome-driven." Triggers include: (1) diagnosing whether a team is stuck shipping features without measuring outcomes, (2) shifting from output-driven to outcome-driven product development, (3) evaluating product manager archetypes (Waiter, Project Manager, Mini-CEO, Strategic) or team maturity, (4) designing a strategy deployment cascade from vision to product initiatives to team-level options, (5) converting a feature roadmap into an outcome roadmap, (6) running a pre-mortem against a quarterly plan to detect build-trap patterns before committing, (7) coaching a PM who is acting as an order-taker for stakeholder requests, (8) writing the case for killing a low-adoption feature.
first-90-days
Leadership transition framework based on Michael D. Watkins' "The First 90 Days". Use this skill whenever the user is discussing a role change, onboarding, new team, new boss, promotion, or stepping into leadership — even if they do not explicitly say "transition" or "90 days". Triggers include: (1) planning onboarding for a new leadership or management role, (2) building a 30-60-90 day plan, (3) diagnosing the business situation being entered (STARS model: Start-up, Turnaround, Accelerated growth, Realignment, Sustaining success), (4) planning critical early conversations with a new boss, peers, or team, (5) identifying and avoiding common transition traps, (6) accelerating time to value in a new role, (7) feeling overwhelmed or under pressure in the first weeks/months of a new job, (8) inheriting a team and unsure where to start, (9) being promoted and needing to "let go" of the old role, (10) joining a company in a new industry, function, or geography and needing to adapt fast.
good-strategy
Strategy evaluation and design framework based on Richard Rumelt's "Good Strategy Bad Strategy" and Michael Porter's "What Is Strategy?". Use this skill whenever the user is discussing strategy, plans, priorities, vision, roadmaps, OKRs, or competitive positioning — even if they do not explicitly say "good strategy", "Rumelt", "Porter", or "strategy kernel". Triggers include: (1) evaluating whether a strategy is good or bad, (2) diagnosing the core challenge before proposing solutions, (3) building a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-testing strategic plans with pre-mortem analysis, (5) diagnosing strategy claims that are actually goals, visions, or budgets dressed up as strategy, (6) reviewing a "strategy doc" or "strategic priorities" for fluff and incoherence, (7) applying Porter's five forces or value chain analysis, (8) deciding what to say "no" to and identifying trade-offs, (9) auditing roadmaps or resource allocation for strategic coherence.
para-method
Personal knowledge management framework based on Tiago Forte's "The PARA Method" and "Building a Second Brain". Use this skill whenever the user is discussing personal knowledge management, note-taking systems, digital organization, or how to turn information into output — even if they do not explicitly say "PARA," "Second Brain," "CODE," or "progressive summarization." Triggers include: (1) organizing digital information into Projects, Areas, Resources, and Archives, (2) building a Second Brain for capturing and retrieving knowledge, (3) applying CODE methodology (Capture, Organize, Distill, Express), (4) designing progressive summarization layers, (5) deciding where to file a new piece of information or note, (6) feeling overwhelmed by notes apps, bookmarks, or scattered files, (7) struggling to retrieve insights from past research, customer interviews, or strategy work, (8) setting up or auditing a notes app, knowledge base, or folder structure across multiple tools.
positioning-and-pitch
Framework based on April Dunford's "Obviously Awesome" and "Sales Pitch". Use this skill whenever the user is discussing how to describe, frame, differentiate, sell, or talk about their product — even if they do not explicitly say "positioning," "pitch," or "messaging." Triggers include: (1) defining or evaluating product positioning using the five-component framework, (2) translating positioning into a compelling pitch for execs, boards, partners, or buyers, (3) choosing a market category strategy that shapes what you build and how you compete, (4) developing differentiated value claims, (5) diagnosing why your product story isn't landing with customers or stakeholders, (6) aligning teams around a shared positioning narrative and connecting it to roadmap priorities, (7) writing a launch announcement, website headline, or tagline, (8) deciding which features to highlight in marketing copy, demos, or sales decks, (9) responding when a buyer says "you sound like everyone else."
sales-pitch
Framework based on April Dunford's "Sales Pitch". Use this skill whenever the user is discussing sales conversations, pitch decks, demos, buyer messaging, or stalled deals — even if they do not explicitly say "sales pitch," "positioning," or "Dunford." Triggers include: (1) structuring a B2B sales conversation that builds buyer confidence rather than pushing features, (2) developing a pitch narrative grounded in competitive positioning, (3) diagnosing why deals are stalling or ending in "no decision," (4) training sales teams on a consistent, repeatable pitch structure, (5) translating product positioning into a sales story, (6) creating pitch storyboards with cross-functional teams, (7) drafting a deck for a customer demo or first discovery call, (8) responding to "how are you different from X?", (9) rewriting cold outbound that is getting ignored, (10) preparing a champion to sell internally to their buying committee
working-backwards
Amazon's Working Backwards product development method based on Colin Bryar and Bill Carr's "Working Backwards". Use this skill whenever the user is discussing a new product, feature, pitch, or launch narrative — even if they do not explicitly say "PR/FAQ," "press release," or "working backwards." Triggers include: (1) writing or reviewing a PR/FAQ for a new product or feature, (2) drafting the launch narrative or announcement story for something not yet built, (3) validating an idea by defining the customer experience first, (4) evaluating an internal idea pitched by a teammate or exec, (5) structuring a 6-pager or narrative memo for an exec review, (6) stress-testing a proposal with pre-mortem analysis, (7) aligning stakeholders around a product vision, (8) deciding whether an idea is worth building before writing code, (9) sharpening a fuzzy product concept into a customer-facing story, (10) running a go/no-go decision meeting on a new initiative.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.