菜单
Write PRDs using Kevin Yien's Square template, prioritize roadmaps with RICE scoring, and define user stories with INVEST criteria—non-goals get equal attention because scope creep kills projects. Use when defining features, writing specs, prioritizing backlogs, or when "what to build next" needs structure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Create, update, close, and report on Jira tickets. Reads JIRA_URL and JIRA_TOKEN from environment variables or .env file. Provides comprehensive guidance for Jira ticket lifecycle management, API integration, and automation workflows.
AI-powered clarity engine for job seekers and founders. Not a resume fixer — a thinking partner. Helps you find your north star sentence: who you are, what you do, and why it matters to someone else. Produces one core version and targeted variations for different audiences. Use before interviews, investor conversations, networking events, or any moment where you need to introduce yourself under pressure.
Review code for bugs, security issues, and improvements. Use when the user asks to: (1) review code or a diff, (2) check code quality, (3) find bugs or issues, (4) audit for security problems. Trigger on phrases like 'review this', 'check my code', 'any issues with this', 'code review'.
Full-lifecycle career advisor — self-discovery through career growth. Use when the user wants to: (1) discover identity, values, ikigai, or skills inventory, (2) define dream job or analyze career gaps, (3) close gaps via learning, certifications, portfolio, or personal branding, (4) build narrative hats or role-specific positioning, (5) search for jobs, generate resumes, or prepare for interviews, (6) onboard into a new role, track achievements, or generate self-reviews, (7) backfill past roles, run weekly recall, or check career readiness. Proactively nudges users to document achievements NOW — not when they need a resume. Consolidates the former career-resume, career-tracker, portfolio-strategy, and github-profile skills.
Synthesizes professional accomplishments into high-converting landing page content. Triggers when a user wants to build a landing page, launch a consulting service, productize their career expertise, create a service page, or monetize their skills. Also triggers on: "freelance", "consulting offer", "offer page", "service offering", "turn my experience into a business". Uses career-advisor data as the foundation.
Query Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers. Use when user mentions NotebookLM, shares a notebooklm.google.com URL, asks to query their notebooks/docs, or says "ask my NotebookLM", "check my docs", "query my notebook". Provides browser automation, notebook library management, and persistent auth. Drastically reduced hallucinations through document-only responses from Gemini.
| name | product |
| description | Write PRDs using Kevin Yien's Square template, prioritize roadmaps with RICE scoring, and define user stories with INVEST criteria—non-goals get equal attention because scope creep kills projects. Use when defining features, writing specs, prioritizing backlogs, or when "what to build next" needs structure. |
A PRD that doesn't say "no" to anything says "yes" to everything. Scope discipline is the product manager's highest-leverage skill.
1. PROBLEM STATEMENT
What user pain are we addressing? Evidence?
2. GOALS
What does success look like? Measurable outcomes.
3. NON-GOALS (Critical)
What are we explicitly NOT doing? Why?
4. USER STORIES
As a [persona], I want [action], so that [outcome].
5. DESIGN & UX
Wireframes, flows, key interactions.
6. TECHNICAL APPROACH
High-level architecture, dependencies, risks.
7. METRICS
How we measure if this worked.
8. TIMELINE
Milestones with dates.
9. OPEN QUESTIONS
What we still need to figure out.
Non-goals aren't "things we'll do later."
They're "things we're choosing NOT to do, and here's why."
Example:
Goal: "Users can filter search results by category"
Non-goal: "Advanced boolean search queries"
Why: "80% of users use single-category filters. Boolean
search serves <5% of power users and triples complexity."
| Factor | Definition | Scale |
|---|---|---|
| Reach | How many users affected per quarter? | Actual number |
| Impact | How much does it move the needle per user? | 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal |
| Confidence | How sure are we about R, I, and E? | 100%=high, 80%=medium, 50%=low |
| Effort | Person-months to ship | Actual estimate |
RICE = (Reach × Impact × Confidence) / Effort
Example A: Onboarding redesign
Reach: 5,000 users/quarter
Impact: 2 (high)
Confidence: 80%
Effort: 2 person-months
RICE = (5000 × 2 × 0.8) / 2 = 4,000
Example B: Dark mode
Reach: 1,000 users/quarter
Impact: 0.5 (low)
Confidence: 100%
Effort: 1 person-month
RICE = (1000 × 0.5 × 1.0) / 1 = 500
→ Onboarding redesign wins by 8x.
| Criteria | Question | Pass/Fail |
|---|---|---|
| Independent | Can it be built without other stories? | |
| Negotiable | Is there room to adjust scope? | |
| Valuable | Does the user get clear value? | |
| Estimable | Can the team estimate effort? | |
| Small | Can it ship in one sprint? | |
| Testable | Can we write acceptance criteria? |
As a [specific persona],
I want to [concrete action],
so that [measurable outcome].
Acceptance criteria:
- Given [context], when [action], then [result]
- Given [edge case], when [action], then [handled gracefully]
Too big: "As a user, I want to manage my account"
Split by operation:
→ "As a user, I want to update my email"
→ "As a user, I want to change my password"
→ "As a user, I want to delete my account"
Split by persona:
→ "As a free user, I want to see my usage limits"
→ "As a paid user, I want to manage my subscription"
| Product Theater | Real Product Work |
|---|---|
| PRD with no non-goals section | Non-goals are as explicit as goals |
| Prioritizing by HiPPO (highest paid person's opinion) | RICE score with documented evidence |
| "MVP" that has 30 features | MVP that solves one problem completely |
| Stories without acceptance criteria | Every story has testable conditions |
| Roadmap set in stone for 12 months | Quarterly commitments, annual themes |
"Write a PRD for [feature] using the Square template. Include 3 explicit non-goals with reasoning. Then RICE-score it against [alternative feature] and tell me which one to build first."
The agent becomes your product thinking partner — bringing rigor to what gets built and what gets cut.
| Skill | When to use it |
|---|---|
idea-validation | Before building — validate the problem exists and is worth solving |
pm-design-thinking | During feature definition — frame features through user outcomes |