All authors

Claude Skills by jasonmeans
github.com/jasonmeans30 skills2 installs67 views
- Analyze Ai ProficiencySet up and run the developer AI workflow proficiency analysis on local CSV or Excel exports. Use when asked to process AI usage and developer survey files, estimate workflow levels and probabilities, or rerun the AI proficiency specification.Votes: 0GitHub stars: 2
- Analyze User InterviewAnalyze a Zoom user interview — merges a VTT transcript with PM interview notes (markdown) to produce a complete research summary saved as a local markdown file. Use after a user research session when you have the transcript and notes; for ordinary meetings, use convert-meeting-notes.Votes: 0GitHub stars: 2
- Create Architecture DiagramHelp users document system architecture with Mermaid diagrams; produces overview, tier deep-dives, data flows, and a component summary table. Use when explaining or documenting how a system is built.Votes: 0GitHub stars: 2
- Create Prd Claude CodeWrite a PRD optimized for AI coding agents (Claude Code, Codex). Includes standard product context plus implementation-specific sections -- file structure, code patterns, API contracts with request/response examples, test cases, migration steps, and sequenced build order. The output is designed so an AI coding tool can build directly from it. Use when an AI coding agent will implement the spec.Votes: 0GitHub stars: 2
- Create Prd EngineeringWrite a detailed PRD for engineering teams covering functional requirements, technical constraints, data models, API contracts, edge cases, acceptance criteria per story, release stages, and cross-functional tracking. Use when the engineering team needs a comprehensive build spec.Votes: 0GitHub stars: 2
- Create Prd One PagerWrite a single-page PRD for leadership and partner audiences. Covers problem, proposal, impact, timeline, ask, and risks using business language. Use when you need to drive alignment and approval, not detail implementation.Votes: 0GitHub stars: 2
- Create PrdWrite a complete Product Requirements Document (PRD) for a feature, product area, or initiative. Trigger this skill whenever someone asks to write a PRD, requirements doc, spec, or product brief — or says things like "I need to document this feature," "help me write up what we're building before sprint planning," or "my VP wants a spec for this project." This is the default PRD format covering problem statement, goals, user stories, success metrics, technical considerations, milestones, and r...Votes: 0GitHub stars: 2
- Create Release NotesGenerate weekly release notes by reconciling merged GitLab MRs in a codebase area with a user-provided feature list. Use when drafting release notes for shipped work.Votes: 0GitHub stars: 2
- Create User InterviewInvoke when planning a user interview; produces a best-practice template (Open, Usability, or Mixture) with Mom Test-aligned questions.Votes: 0GitHub stars: 2
- Decision BriefHelp users prepare and deliver decision briefings using the SOCRR framework. Use when someone needs a decision from a manager, executive, sponsor, or stakeholder group.Votes: 0GitHub stars: 2
- Devex SurveyCreate or analyze Developer Experience surveys. Creation mode outputs a 9-question HaTS-aligned survey; Analysis mode outputs sentiment metrics with theme clustering. Use when running a developer experience survey or analyzing its results.Votes: 0GitHub stars: 2
- Engineering FoundationsBuild and reinforce core engineering execution habits with repeatable practices for architecture decisions, testing strategy, and code review discipline. Use when planning capability growth, improving delivery quality, or creating weekly technical drills.Votes: 0GitHub stars: 2
- Jobs To Be DoneHelp users define user needs with personas, a use case table (Outcome / How Today / Future / North Star), and open questions. Use when clarifying who a product serves and what outcomes they need.Votes: 0GitHub stars: 2
- Lenny Analytical Thinking InterviewsPractice Analytical Thinking PM interviews. Use when someone wants to practice an AT interview, get coached on their AT interview template, or learn the AT interview framework. Can act as the candidate (user plays interviewer) or as a coach (user submits their template for scoring).Votes: 0GitHub stars: 2
- Lenny Product Sense InterviewsPractice Product Sense PM interviews. Use when someone wants to practice a Product Sense interview, get coached on their PS interview template, or learn the PS interview framework. Can act as the candidate (user plays interviewer) or as a coach (user submits their template for scoring).Votes: 0GitHub stars: 2
- Question StormingHelp users run question-storming sessions to explore problem spaces. Use when someone needs to understand a new domain, kick off discovery for a feature or initiative, structure a dashboard around the right questions, or get a team aligned on what they don't know.Votes: 0GitHub stars: 2
- Sourcegraph SearchSearch codebases across repositories using Sourcegraph MCP integration — code search, commit history, diffs, symbol navigation, and DeepSearch. Use when a question spans many repositories and a Sourcegraph MCP server is configured.Votes: 0GitHub stars: 2
- Storytelling For ImpactHelp users craft persuasive narratives; produces a Story Map with headline, opening, narrative arc, and delivery practice guide. Use when preparing a presentation, pitch, or talk that must persuade.Votes: 0GitHub stars: 2
- Write As JasonWrite in Jason Means' authentic voice and style. Use when Jason needs help drafting blog posts, LinkedIn posts, memos, talks, or any written content that should sound like him. Analyzes topic and produces content matching his signature blend of personal storytelling, practical frameworks, and vulnerability.Votes: 0GitHub stars: 2
- Write Teachable Personal MomentWrite and rewrite long-form posts in Jason Means's personal Medium voice using story-first structure, practical frameworks, and reflective coaching tone. Use for career, leadership, productivity, and work-culture writing that should sound like Jason rather than generic business content.Votes: 0GitHub stars: 2
- Analyze User FeedbackTurn raw feedback (surveys, tickets, reviews, Slack, notes) into ranked themes with counts, sentiment, quotes, and recommended actions; a script does the counting. Use when you have a pile of feedback to make sense of. For one interview transcript, use analyze-user-interview.Votes: 0GitHub stars: 2
- Audit Agent EnvironmentAudit a Claude Code and Codex setup (CLAUDE.md, AGENTS.md, skills, plugins, config) for token usage, workflow friction, and tool vs. script vs. skill fit, then recommend and apply fixes. Use when sessions feel slow or costly, before adding skills, or as periodic cleanup.Votes: 0GitHub stars: 2
- Automate Review ProcessDesign a risk-tiered review process for code, design, or approvals. Measures review latency, splits the work between checks, AI reviewers, and humans, and produces the policy plus starter config. Use when reviews are slow or inconsistent, or when adding an AI review gate.Votes: 0GitHub stars: 2
- Convert Meeting NotesConvert a meeting transcript (Zoom, Teams, or Meet .vtt, or pasted text) into an Obsidian-ready note with decisions, owned action items, and open questions. Use after a recorded meeting or to turn Zoom notes into notes. For research interviews, use analyze-user-interview.Votes: 0GitHub stars: 2
- Create Figma MockupTurn a PRD or idea into a low-fidelity mockup (screen inventory, wireframe spec with states and interactions, and a single-file HTML wireframe you can import into Figma). Use to visualize a feature before design starts. It does not edit Figma files directly.Votes: 0GitHub stars: 2
- Gtm PlanCreate a go-to-market plan for a launch, covering tier, audience, positioning and messaging, channels, enablement for sales and support, a timeline by release stage, metrics, and owners. Use when coordinating a launch across teams. For the go/no-go review, use launch-checklist.Votes: 0GitHub stars: 2
- Launch ChecklistStage-gate launch readiness review for Alpha, Closed Beta, Open Beta, and GA. Builds a checklist by function with owners, evidence, and sign-offs, ending in go / no-go. Use before promoting a release or when asked "are we ready to launch?" For launch strategy and messaging, use gtm-plan.Votes: 0GitHub stars: 2
- Map StakeholdersMap stakeholders for a project or decision (who decides, influences, or can block, and what each cares about) with a power/interest grid, RACI, and engagement plan. Use when starting an initiative, before a contentious decision, or when alignment keeps breaking down.Votes: 0GitHub stars: 2
- Prioritize FeaturesRank a backlog with RICE, ICE, weighted scoring, or Kano (a script does the math) and write a defensible priority memo with sourced estimates, a sensitivity check, and trade-offs. Use when deciding what to build next or justifying a roadmap order.Votes: 0GitHub stars: 2
- Validate HypothesisTurn a product assumption into a testable hypothesis and validation plan covering the riskiest assumption, cheapest test, success and kill criteria set in advance, A/B sample size, and a results readout. Use before investing in a feature or when a team disagrees about what users want.Votes: 0GitHub stars: 2