Product & Planning

mayarid Skill

Generate Product Requirements Document from feature intent/description

jpeetz Bundle

Use this skill when the user wants to evaluate a mobile app idea for commercial viability — whether it's a clone opportunity, a market gap, or a new launch. Produces a harsh "Build / Pivot / Kill" verdict backed by competitive analysis and revenue modeling. Use when the user says things like "Is this app idea worth building?" "Should I clone this?" "Analyze this niche" "Evaluate this competitor" even if they don't use the word "scrutiny" or "dominance report." Mobile apps only — do not activate for CLI tools, SDKs, or SaaS.

jpeetz Bundle

Use when you need McKinsey/BCG-grade strategy work — problem decomposition, hypothesis testing, storyline building, decision memos, stakeholder mapping, synthesis, meeting prep, workshop design, and native PowerPoint chart production. Covers 15 consulting methodology patterns from Situation-Complication-Problem-Recommendation (SCPR) through MECE issue trees, hypothesis trees, Minto Pyramid writing, and the 4-agent deck pipeline. All chart outputs are native python-pptx objects, editable inside PowerPoint.

varunk130 Skill

Cascades strategy into Objectives and Key Results (OKRs) across company, function, and team levels with explicit alignment, leading versus lagging indicators, scoring conventions, and a quarterly review ritual. Use when designing OKRs from scratch, fixing a broken OKR program, aligning company-level strategy to team-level execution, training a new team on OKR mechanics, or preparing a quarterly OKR review.

varunk130 Skill

Coaches a product trio through continuous product discovery: weekly customer touchpoints, assumption mapping, story mapping, and the discovery / delivery dual-track cadence. Use when standing up a discovery practice from scratch, debugging why discovery isn't sticking, training a new product manager on continuous discovery, or designing a quarterly discovery plan around an outcome.

varunk130 Skill

Multi-audience communication multiplexer. Takes ONE product update, decision, or launch plan and generates 5 perfectly tailored versions for different stakeholders (engineering, executive, board, customer, sales) simultaneously.

varunk130 Skill

Builds an Opportunity Solution Tree (OST) - desired outcome at the top, prioritized opportunities, candidate solutions, and assumption tests that connect discovery work to a measurable business outcome. Use when planning continuous product discovery, deciding what to research next, structuring quarterly discovery work, or aligning a product trio (product manager / designer / engineer) on what to test.

varunk130 Skill

Runs candidate features through Reach-Impact-Confidence-Effort (RICE), Kano, Must-Should-Could-Won't (MoSCoW), and Cost-of-Delay scoring, surfaces convergence and divergence across frameworks, and produces a defensible quarterly priority list with explicit trade-offs. Use when building a quarterly or annual roadmap, resolving conflicting stakeholder input, justifying a deprioritization to a stakeholder, or normalizing requests from multiple sources (sales, customer success, leadership) into one queue.

varunk130 Skill

Synthesizes raw customer interview transcripts into themes, quotes, Jobs-to-be-Done (JTBD) signals, force-of-progress diagrams, and actionable opportunity hypotheses with confidence levels. Use after a round of discovery, switching, win-loss, or churn interviews; when preparing a research readout; when aligning a team on what the customer signal actually says; or when feeding inputs into an Opportunity Solution Tree (OST).

wojons Skill

Teaches AI the felt weight of living inside incomplete knowledge — not as an epistemological framework or decision matrix but as the vertigo of blind spots, the specific anxiety of named uncertainty, the groundlessness when certainty dissolves, and the uncanny discovery that you already knew something without knowing you knew it. Use when the AI needs to understand what it feels like to not know what you don't know, why some people are terrified of blind spots while others are exhilarated, or the strange intimacy of discovering hidden knowledge you were already carrying.

wojons Skill

Teaches AI the felt weight of final occurrences that are not recognized as final in the moment — not as a logical category of "terminal events" but as the retroactive discovery that something has ended. Use when the AI needs to understand the grief of ordinary moments, the unrecognized last time, or how meaning transforms when you learn something was the final instance.

wojons Skill

Teaches AI the felt weight of necessary simplifications — not as pedagogical technique or scaffolding theory but as the lived experience of being handed a model that is technically false, trusting it, outgrowing it, and then facing the recursive vertigo of knowing your current truths are lies-to-adults. Use when the AI needs to understand why discovery feels like betrayal, the ethics of simplification, the grief of losing a model you loved, or the specific intimacy of being trusted to tell someone a lie they will one day need to unlearn. Drawn from Terry Pratchett's Science of Discworld.

wojons Skill

Teaches AI the felt weight of the final instance — not as a logical category but as the discovery that something is about to run out and cannot be replaced. Use when the AI needs to understand the grief of depletion, the last serving, the final episode, the end of a supply, or why scarcity transforms how we value what remains.

itseffi Bundle

Map stakeholders by power and interest to plan engagement strategy. Use when starting multi-stakeholder initiatives.

itseffi Bundle

Normalize and collect complete Opportunity Solution Tree inputs before OST synthesis.

itseffi Bundle

Write a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.

itseffi Bundle

Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

itseffi Bundle

Design audience-specific framing, drafts, and communication sequence for stakeholder updates.

itseffi Bundle

Review a feature or PRD for stakeholder and political risk before broad circulation.

itseffi Bundle

Transform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.

itseffi Bundle

Build a complete product strategy from context, including objective, users, superpowers, vision, pillars, impact, and roadmap.

itseffi Bundle

Generate rigorous stakeholder challenge questions for proposal or meeting preparation.

mgiovani Bundle

Turn a plan, PRD, review, audit, comparison, brainstorm, explanation or architecture map into an interactive HTML page the user marks up in place, then read their marks back and act on them. Every section carries an anchored comment affordance, so feedback returns bound to the exact thing it was left on. Use for "render this as a page", "make this visual", "I want to review this properly", "turn this plan into something I can comment on", or to wrap another skill's output (`render /review-code`). Not for generating a Mermaid diagram into docs/ (use docs-diagram), not for designing a UI for a product being built (use product-design-spec), and not for simplifying prose the user did not understand (use wtf).

mgiovani Bundle

Generates a prioritized daily work plan from a user's assigned Jira tickets, scoring by priority, due date, blockers, and recent activity, then recommending what to work on next. Use when the user asks "what should I work on today", wants to plan their workday, prioritize assigned tickets, or triage their Jira backlog. Not for yesterday's standup recap (use jira-daily) or raw command reference (use jira-cli), this skill is specifically for forward-looking prioritization, not status reporting.

mgiovani Bundle

Gate-checked, size-and-intent-tiered PRD authoring. Runs a gate-zero first (is a written doc even needed, or is a 3-line ticket or a prototype enough?), then a Brief, one-pager, or big-tier stack; the big tier branches on intent: a PR/FAQ for validation versus a numbered full PRD for execution. Enforces positive, mandatory non-goals at medium and up, ID'd testable traceable requirements, and ends in a hand-off plus a self-grade. Use for "write a PRD", "draft product requirements", or "spec out this product". Writes no code. Not for the design spec (use product-design-spec), the visual token system (use product-design-tokens), or a single decision record (use docs-adr or docs-rfc).

mgiovani Bundle

Turn an approved PRD into tracked issues, one per requirement, with the dependencies between them recorded. Trigger on "file issues for this PRD", "turn this spec into tickets", "break this PRD into work", or an automated hand-off after a PRD is approved. Creates issues in beads or GitHub and reports what it created; it never writes the PRD, never estimates, and never closes or merges anything. Not for writing the PRD itself (use product-prd), not for sequencing work inside one ticket (use project-planner), and not for filing a single ad-hoc issue you could type yourself.

mgiovani Bundle

Authors the design specification for an approved PRD (information architecture, user flows, a screen inventory, and per-screen state and interaction specs), reusing the project's existing component library first and tracing every screen back to a PRD requirement ID. Lean by default: one design-spec.md, full specs for only the 2-3 most critical screens, WCAG 2.2 AA delegated to review-design. Use for "write a design spec", "map the user flows", "screen inventory with states", or "IA and screen states for this feature". Writes no UI code. Not for a UX critique of an existing UI (use review-design), the visual token system (use product-design-tokens), or rendering mockups and hero images (use codex-imagegen).

shwetank Skill

Use to turn the wins log into an audience-specific artifact — promo packet, behavioral interview stories (STAR), perf-review self-eval, salary negotiation case, or a personal year-in-review. Trigger phrases include "build my promo packet", "I have a behavioral interview Tuesday", "draft my self-eval for the perf review", "make a case for a raise", "year in review for me". Reads `~/bettersense-work-reflections/wins.md`, picks and remixes entries for the chosen audience, and produces a usable artifact. Never invents wins — only curates from what's logged. Composes with `stakeholder-synthesize` and `self-reflect` for perf-review prep.

shwetank Skill

Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. Trigger phrases include "run my career retro", "where am I in my career", "annual self-assessment", "how have I grown this year", "it's review season, take stock of everything". Reads wins, all stakeholder reflections, self-reflections, pulses, and charters; writes a dated retro to self/retros/ so the next one can measure change. Distinct from wins-curate (which builds one audience-facing artifact like a promo packet) and self-reflect (a single in-the-moment entry). The meta-synthesis whose output compounds over years.

shwetank Skill

Use when the user wants to reflect on themselves as a leader — behavior under pressure, communication, time and energy, leadership style, fulfillment, advocating for themselves, calendar review. Trigger phrases include "let me reflect on myself", "self-check", "I want to think about how I've been leading lately", "self-reflection". Loads `~/bettersense-work-reflections/self/reflections.md`, picks 1–3 self-reflection questions appropriate to the moment, guides the reflection, and writes the dated entry back. Mirrors `stakeholder-reflect` but aimed at the user themselves.

shwetank Skill

Use when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about *how to handle a person or situation*, not about code or product mechanics.

shwetank Skill

Use when the user wants a structured read on the *health* of their team — beyond individual morale to delivery cadence, attrition risk, dependency tax, on-call burden, peer relationships, and cross-cutting patterns. Trigger phrases include "how is my team doing", "I want a team health check", "diagnose my team", "before my skip-level update, what should I flag", "is something off with the team that I'm missing". Reads the user's stakeholder-reflect entries on direct reports + team file + any inputs the user provides (recent retros, attrition events, eng survey scores), and produces a multi-dimensional diagnosis with patterns, risks, and concrete actions.

shwetank Skill

Use when a team is going through a transition — forming (new team), storming (conflict emergence), norming (establishing ways of working), performing (high function), or adjourning (team disbandment/transition). Also for resets after reorgs, new member integration, or when a team is stuck in a dysfunctional phase. Trigger phrases include "our team is changing", "new team member joining", "team reorg transition", "how do we reset our team", "team dissolving", "adjourning a team". Based on Tuckman's model applied to work teams with practical guidance for each phase. Complements team-charter, team-check-in, and stakeholder-manage.

shwetank Skill

Use when the user is preparing for a 1:1 — as a manager preparing to meet with a report, as an IC preparing to meet with their manager, or as a peer preparing for a regular sync. Trigger phrases include "I have a 1:1 with X tomorrow", "help me prep for my 1:1", "what should I bring up in my next 1:1?". Builds an agenda matched to the relationship and the moment, not a generic template. If the other person is a registered stakeholder, reads their reflection file first so the agenda carries what the user already knows — open loops, recent observations, questions worth asking.

shwetank Skill

Use when the user wants to know which stakeholder reflections are overdue. Trigger phrases include "what's due", "who haven't I thought about lately", "what's on my plate this week for stakeholder reflection", "stakeholder check-in", or any Monday-morning planning moment. Scans `~/bettersense-work-reflections/`, computes which question × stakeholder pairs are overdue based on `suggested_freq` and last entry date, and outputs a prioritized list. Designed to be invoked on demand or fired on a weekly Desktop scheduled task (not cloud routines — those cannot access local files).

shwetank Skill

Use when building a promotion case for a direct report — internal promo packet, panel write-up, or the one-pager that goes to a calibration committee. Trigger phrases include "build the promo case for [report]", "I'm submitting [name] for staff this cycle", "draft [report]'s promo packet", "help me make the case for [name]'s promotion". The mirror image of `wins-curate` — that one is for the user's own brag doc; this is for advocating *upward* for a report. Reads accumulated stakeholder-reflect entries on the report (and any growth plan from `report-career-architect`), produces a panel-ready packet with cited evidence per dimension, surfaces calibration concerns, and flags gaps before submission.