julianoczkowski

@julianoczkowski source repo

39 skills
0 followers
5 hours ago last updated

▌
Run Lint Checks 2 · julianoczkowski
Run comprehensive lint checks for Angular + Vite project to ensure design system compliance, type safety, and code quality. Use when making code changes, before completing tasks, or when the user requests lint checks.

0
installs
▌
Run Lint Checks 3 · julianoczkowski
Run comprehensive lint checks for SolidJS + Vite project to ensure design system compliance, type safety, and code quality. Use when making code changes, before completing tasks, or when the user requests lint checks.

0
installs
▌
Integrate Modus Icons 2 · julianoczkowski
Help with correct Modus icon usage patterns including naming conventions, sizing, and accessibility

0
installs
▌
Create Modus Form Component 2 · julianoczkowski
Scaffold form components with proper Modus input integration, event handling, validation, and checkbox bug handling

0
installs
▌
Set Up Modus Event Listeners 2 · julianoczkowski
Properly set up and clean up event listeners for Modus web components using createEffect and onCleanup patterns

0
installs
▌
Create Modus Wrapper Component 2 · julianoczkowski
Scaffold a new Modus wrapper component following established SolidJS patterns with proper TypeScript interfaces, event handling, and cleanup

0
installs
▌
Handle Modus Checkbox Value Bug 2 · julianoczkowski
Apply the critical checkbox value inversion workaround when working with ModusCheckbox components

0
installs
▌
Implement Modus Modal With Refs 2 · julianoczkowski
Create Modus modals using the callback ref pattern for programmatic control

0
installs
▌
Fix Modus Component Event Issues 2 · julianoczkowski
Debug and fix common event handling problems with Modus web components

0
installs
▌
Style Modus Components With Tailwind 2 · julianoczkowski
Use ModusDropdownMenu instead of ModusSelect for reliable event handling

0
installs
▌
HTML · julianoczkowski bundle
Produce a single self-contained .html file instead of a markdown wall when the answer has shape — side-by-side comparisons, a timeline, a diagram, a sortable list, or a deck. This skill should be used when the user invokes /html or any of its patterns (options, plan, pr, codemap, tokens, motion, diagram, deck, explainer, status, editor), and when a request implies a structured artifact — phrases like "show me my options for X", "write the plan", "do a post-mortem", "make a deck from these notes", "let me triage these", "render the design system", "explain how X works", "diagram the flow". Prefer this skill even when the user says "write me a doc" or "summarize" — HTML is often the better surface, and the user can always ask for markdown if they prefer.

0
installs
▌
Pm Prd · julianoczkowski
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.

0
installs
▌
Pm Copilot · julianoczkowski bundle
Product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Use this as the entry point whenever a product manager wants to work through building a product or feature the market-driven way — e.g. "I want to build a feature", "help me plan this product", "where do I start", "I have an idea for X". It figures out where the PM is in the Pragmatic journey, guides them through the right stages (market research, personas, positioning, strategy, requirements, roadmap, launch), and produces a client-ready artifact (Markdown or Word .docx) at every stage. Also use it to explain the Pragmatic Framework or choose which PM artifact to create.

0
installs
▌
Pm Personas · julianoczkowski
Create Pragmatic Institute buyer and user personas — archetypes grounded in real market evidence, written so the team stays connected to real people. Use when the PM asks about personas, "who is the buyer", "who is the user", target audience, ICP, or wants to make a persona come alive. Distinguishes the buyer (makes/influences the purchase) from the user (uses it daily). Produces a Buyer Persona and a User Persona as a Markdown or Word .docx artifact.

0
installs
▌
Pm Launch Plan · julianoczkowski
Build a Pragmatic go-to-market launch plan and readiness checklist. Use when the PM asks to plan a launch, GTM, go-to-market, launch readiness, launch checklist, release announcement, or "get sales and marketing ready". Coordinates the Programs and Enablement columns of the framework around a market window. Produces a Launch Plan as a Markdown or Word .docx artifact.

0
installs
▌
Pm Positioning · julianoczkowski
Create a Pragmatic Institute Positioning Document — describe a product by the market problems it solves (not features), for one persona in one segment. Use when the PM asks for positioning, messaging, "how do we describe/pitch this", an internal positioning doc, or a positioning statement. Produces a Positioning Document plus a Problem-Oriented Capabilities (POC) worksheet as a Markdown or Word .docx artifact.

0
installs
▌
Pm Gap Analysis · julianoczkowski
Run a Pragmatic Institute Gap Analysis — a market-driven self-assessment of how well the team performs the 37 activities of the Pragmatic Framework, who owns each, and where the biggest gaps are. Use when the PM asks "where do we stand", "how are we doing on the framework", a product-org self-assessment, a maturity check, or where to focus. Produces a Gap Analysis table plus a top-3-gaps action plan as a Markdown or Word .docx artifact.

0
installs
▌
Pm Release Plan · julianoczkowski
Turn a prioritized set of requirements into a committed Pragmatic release plan — themed, sized, and signed. Use when the PM asks to plan a release, define MVP scope, commit a date, build a release charter, or "what goes in this release". Covers MVP done right, themes, the estimation ladder, the market window, and the scope/schedule/resources change levers. Produces a Release Charter as a Markdown or Word .docx artifact.

0
installs
▌
Pm Requirements · julianoczkowski
Write market-driven, prioritized product requirements (a Market Requirements Document / MRD) the Pragmatic Institute way. Use when the PM asks for "requirements", "an MRD", "what should we build", "prioritize features", "market requirements", or wants development to stop saying "requirements aren't specific enough". Articulates each requirement as a persona's problem, prioritizes with Market Evidence × Impact, and groups them for delivery. Produces a Market Requirements Document as a Markdown or Word .docx artifact.

0
installs
▌
Pm Use Scenarios · julianoczkowski
Write Pragmatic Institute use scenarios — short stories that put a market problem in context from the persona's point of view (a component of requirements). Use when the PM asks for "use scenarios", "a day in the life", "user story context", "problem statements", or needs to reframe a feature request as a real problem so development understands the WHAT (not the HOW). Produces a Use Scenarios document as a Markdown or Word .docx artifact.

0
installs
▌
Pm Product Canvas · julianoczkowski
Build a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to "make the business case", "justify this to leadership", "size the market", "should we buy, build or partner", "what's the ROI", "build a product canvas", or "get buy-in for this idea". Frames the opportunity as Value Proposition, Value Creation and Value Capture, sizes the market, runs the Buy/Build/Partner decision, and ends in a go/no-go recommendation with quantified risk. Produces a Product Canvas / Business Case as a Markdown or Word .docx artifact.

0
installs
▌
Pm Market Problems · julianoczkowski
Run Pragmatic Institute market discovery and validate real market problems before anything gets built. Use when a PM says "I want to build a feature", "do market research", "talk to customers", "discovery", "validate this idea", "is this problem real", "NIHITO", or "who should I interview". Enforces the outside-in rule: build only for problems that are urgent, pervasive, and that the market will pay to solve. Produces a Market Discovery Document and a Market Problems Table as a Markdown or Word .docx artifact.

0
installs
▌
Pm Product Roadmap · julianoczkowski
Build a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release plan). Frames outcomes and market problems over time-frames, not features on dates. Produces a Product Roadmap as a Markdown or Word .docx artifact.

0
installs
▌
Pm Product Strategy · julianoczkowski
Build a Pragmatic Institute Strategy Matrix — a forced-choice 4×4 that decides who to win and what to build over a set time frame, and surfaces alignment between the product team and leadership. Use when the PM asks about product strategy, "where should we invest", "what should we build for whom", focus, prioritizing markets, or avoiding a spread-too-thin roadmap. Produces a Strategy Matrix as a Markdown or Word .docx artifact.

0
installs
▌
Pm Win Loss Analysis · julianoczkowski
Run a Pragmatic Institute Win/Loss analysis — understand why recent evaluators did or did not buy and the steps they took in their buying process. Use when a PM says "why did we win/lose", "win-loss", "why do deals slip", "churn reasons", "why did they pick the competitor", or "interview a lost prospect". Enforces the rule that win/loss is run by an objective party not involved in the sale, and evaluates the buying PROCESS, not the salespeople. Produces a Win/Loss Interview Guide and a Win/Loss Findings Report as a Markdown or Word .docx artifact.

0
installs
▌
Pm Opportunity Scoring · julianoczkowski
Score and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare options objectively instead of by opinion. Produces an Opportunity Scorecard as a Markdown or Word .docx artifact.

0
installs
▌
Pm Competitive Landscape · julianoczkowski
Map the Pragmatic Institute Competitive Landscape — identify competitive AND alternative offerings, assess their strengths and weaknesses, and develop a strategy for winning (knowing when to fight and when to run). Use when a PM says "competitive analysis", "competitors", "battlecard", "how do we win against X", "alternatives", or "where do we play". Includes the Solution Matrix (customer impact vs. depth of investment). Produces a Competitive Landscape analysis and a Solution Matrix as a Markdown or Word .docx artifact.

0
installs
▌
Pm Distinctive Competence · julianoczkowski
Articulate your organization's Distinctive Competencies the Pragmatic Institute way — the unique abilities to deliver value that are valued, different, and provable. Use when a PM says "what makes us different", "our moat", "unique strengths", "why us", "competitive advantage", or "distinctive competence". Strategy = intersect market problems with what only you can do. Produces a Distinctive Competencies worksheet as a Markdown or Word .docx artifact.

0
installs
▌
Pm Stakeholder Communication · julianoczkowski
Build a Pragmatic stakeholder communication plan and status updates that expose risk early and speak each audience's language. Use when the PM asks to manage stakeholders, plan comms, write an exec/status update, a project status report, a steering-committee update, or "keep everyone aligned". Covers the Identify→Analyze→Communicate steps, the Influence×Importance matrix, and the four metric categories. Produces a Stakeholder Communication Plan and a Status Update as a Markdown or Word .docx artifact.

0
installs
▌
Run Lint Checks · julianoczkowski
Run comprehensive lint checks for React + Vite project to ensure design system compliance, type safety, and code quality. Use when making code changes, before completing tasks, or when the user requests lint checks.

0
installs
▌
Modus Frontend · julianoczkowski bundle
Build production-grade frontend interfaces using the Modus 2.0 Design System with Tailwind CSS. Use this skill when the user asks to build web components, pages, dashboards, or application screens. Enforces the 9-color semantic system, Modus Web Components, Modus Icons, and design system compliance. Framework-agnostic (works with SolidJS, React, Angular, or any framework).

0
installs
▌
Integrate Modus Icons · julianoczkowski
Help with correct Modus icon usage patterns including naming conventions, sizing, and accessibility

0
installs
▌
Create Modus Form Component · julianoczkowski
Scaffold form components with proper Modus input integration, event handling, validation, and checkbox bug handling

0
installs
▌
Set Up Modus Event Listeners · julianoczkowski
Properly set up and clean up event listeners for Modus web components using useEffect patterns

0
installs
▌
Create Modus Wrapper Component · julianoczkowski
Scaffold a new Modus wrapper component following established patterns with proper TypeScript interfaces, event handling, and cleanup

0
installs
▌
Handle Modus Checkbox Value Bug · julianoczkowski
Apply the critical checkbox value inversion workaround when working with ModusCheckbox components

0
installs
▌
Implement Modus Modal With Refs · julianoczkowski
Create Modus modals using the forwardRef + useImperativeHandle pattern for programmatic control

0
installs
▌
Fix Modus Component Event Issues · julianoczkowski
Debug and fix common event handling problems with Modus web components

0
installs
▌
Style Modus Components With Tailwind · julianoczkowski
Style Modus components using custom border and opacity utilities that work with CSS variables, avoiding Tailwind patterns that don't work with runtime CSS variables

0
installs

39 published skills