Product & Planning

stanestane Bundle

Audit a game feature, roadmap candidate, UX improvement, support system, connective-tissue feature, or quality-of-life change for KPI coverage bias and measurement blind spots. Use when a team is overvaluing only directly attributable metrics, neglecting foundational work that is hard to measure, or struggling to justify features whose value is real but not cleanly tied to one headline KPI.

stanestane Bundle

Identify the single highest-leverage thing to remove from a game design, feature, system, UX flow, pitch, roadmap item, or prototype in order to improve it significantly. Use when a design feels bloated, muddy, overengineered, overly tutorialized, friction-heavy, or diluted by low-value mechanics, and you want a subtractive critique with rationale, tradeoffs, and a cleaner alternative.

stanestane Bundle

Help analyze recurring conflict patterns on software or game projects by identifying likely collaboration archetypes, behavior patterns, project risks, and practical response strategies. Use when someone describes a teammate, lead, founder, stakeholder, client, producer, or collaborator whose recurring behavior is creating friction, slowing decisions, damaging trust, or disrupting execution. Focus on observable behavior and project consequences, not clinical diagnosis, then suggest safer and more effective next moves.

stanestane Bundle

Prioritize game design feature options by comparing expected impact, implementation cost, strategic fit, and roadmap context. Use when choosing between competing feature ideas, deciding what to do now versus later, ranking solution paths after ideation, or identifying which option is best immediately and which is better long-term.

8421bit Bundle

Applies OKR (Objectives and Key Results) framework to define and track strategic goals. Use for quarterly planning, goal alignment, performance management, or team focus.

8421bit Bundle

Applies Opportunity Solution Tree framework to connect product outcomes to discovery and delivery. Use for continuous discovery, feature planning, solution validation, or aligning research to roadmap.

8421bit Bundle

Defines and tracks Key Performance Indicators for product features and initiatives. Use for metrics planning, success measurement, stakeholder reporting, or OKR alignment.

8421bit Bundle

Applies RICE prioritization framework to score and rank features or initiatives. Use for feature prioritization, roadmap planning, resource allocation decisions, or stakeholder alignment on priorities.

8421bit Bundle

Applies MoSCoW prioritization method to categorize requirements by importance. Use for scope negotiations, release planning, or stakeholder alignment on priorities.

8421bit Bundle

Creates product user journey diagrams with Mermaid. Use for UX planning, feature flow design, or stakeholder communication.

8421bit Bundle

Creates product roadmaps with Mermaid Gantt diagrams showing feature timelines. Use for release planning, stakeholder communication, or team alignment on delivery schedule.

8421bit Bundle

Generates user stories from PRD or initiative documents following agile best practices. Use for sprint planning, backlog creation, requirements decomposition, or development handoff.

8421bit Bundle

Creates detailed user personas from feedback, interview data, and behavioral analysis. Use for user segmentation, design alignment, stakeholder communication, or empathy building.

8421bit Bundle

Drafts or converts documents into Product Requirements Documents (PRD). Supports two modes - (1) Create new PRD from initiative documents and research, or (2) Convert existing documents to PRD format using standard or daily iteration templates.

8421bit Bundle

Creates wireframe specifications for UI concepts. Use for design handoff, stakeholder review, or early prototyping.

8421bit Bundle

Conducts and documents user interviews following best practices. Use for user research, requirement discovery, or validation.

8421bit Bundle

Analyzes user satisfaction metrics (NPS, CSAT). Use for customer health monitoring, product quality assessment, or stakeholder reporting.

8421bit Bundle

Creates a new product initiative document using Socratic questioning and guided discovery. Use when starting a new product feature, clarifying vague product ideas, structuring informal concepts into formal proposals, or aligning stakeholders on initiative scope and goals.

8421bit Bundle

Applies DACI decision-making framework to clarify roles and responsibilities in decisions. Use for cross-functional decisions, stakeholder alignment, or decision documentation.

8421bit Bundle

Creates stakeholder update report. Use for executive communication.

valentinnikolaev Bundle

Assess the commercial and financial viability of a software product, startup idea, MVP, repository, PRD, requirements folder, or concept. Use when the user asks whether a project is worth building or wants demand, competitors, MVP scope, development and operating costs, unit economics, scenarios, risks, validation experiments, or a GO, VALIDATE_FIRST, PIVOT, or NO_GO verdict. Default to a quick advisory answer in chat; create analysis files only when the user explicitly requests artifacts.

jhonatan-oliveiradev Skill

Use when a writing task is high-stakes, multi-stakeholder, source-grounded, or ambiguous enough that audience, objective, channel, evidence, and constraints must be resolved before drafting.

jhonatan-oliveiradev Skill

Use when roadmap gaps need to become credible portfolio artifacts with explicit evidence contracts showing which capabilities a project must actually demonstrate.

jhonatan-oliveiradev Skill

Use when a developer needs to normalize job postings or market samples into explainable fit, capability gaps, demand signals, and roadmap-priority recommendations.

l4ci Bundle

Use when the user wants to turn strategy into measurable goals using OKRs (Objectives and Key Results), the goal-setting method from Andy Grove at Intel and popularized by John Doerr in Measure What Matters. Guides a drafting cycle: clarify a qualitative objective, draft 3-5 measurable key results, stress-test the key results with parallel critics, set ambition and cadence, and check alignment. Maintains an OKR document. Triggers include "OKR", "OKRs", "objectives and key results", "set quarterly goals", "Measure What Matters", "draft our objectives".

l4ci Bundle

Use when the user wants to stress-test a plan, proposal, PRD, strategy, or decision before committing to it. Runs a prospective-hindsight pre-mortem by fanning out independent failure-finder subagents across distinct risk lenses, deduplicating and scoring the risks by likelihood and impact, then designing mitigations for the worst ones. Triggers include "pre-mortem", "red-team this plan", "what could go wrong", "stress-test this", "poke holes in this proposal".

qredence Skill

Reads a product requirements document (PRD) and produces the corresponding Figma design -- screens, states, and flow -- reusing existing design system components wherever possible and flagging any requirement that has no corresponding pattern yet. Use when a PRD or spec exists and needs to become an actual design, especially when paired with a connector to the requirements source.

qredence Skill

Writes a concise handoff summary of a file's current state -- what's finished, what's in progress, key decisions made and why, and open questions -- for a teammate picking up the work, a new team member, or a stakeholder update. Use whenever context needs to transfer cleanly to someone else.

qredence Skill

Produces a prototype connection plan from a described user flow, flow diagram, PRD, or set of designed screens. Use when screens exist or a flow is described and the team needs a clear map of frames, triggers, actions, branches, overlays, and missing screens before manual prototype wiring. This is a planning/specification skill, not an interaction-editing skill.

qredence Skill

Plan a Figma Design screen, component, flow, or Figma Make prototype through a short discovery interview, then produce a confirmed design brief without generating UI. Use when the user has a vague request, early product idea, unclear scope, competing constraints, or needs alignment before design generation.

sylphxai Skill

Select and claim the next high-value work item from current product and repository state. Use when the user wants the agent to choose from an existing backlog. Do not use to finish an already accepted objective.

sylphxai Bundle

Drive one already accepted engineering or product objective to its requested terminal. Use when completion matters more than a plan. Do not use to choose what to do next from a backlog.

sylphxai Skill

Bound a request into one objective, one terminal (local, landed, released, or live), in-scope work, adjacent independently shippable outcomes, and hard cut lines. Use when the user mixes several deliverables, scope is expanding, or it is unclear what done means. Do not use to pick the next backlog item or to finish an already accepted multi-step objective.

sylphxai Bundle

Translate an operational decision into an explicit model — objective, constraints, uncertainty, and a recomputed solution — then stress it for proxy failure. Use when the user asks to optimize, allocate, schedule, or choose under constraints. Do not use to pick the next backlog item, run an experiment, or critique a claim.

stanestane Bundle

Audit a game feature, live update, roadmap item, event, or content drop by how different player segments are likely to perceive it. Use when a feature is aimed at one cohort but visible to others, when update messaging may create excitement for players who cannot meaningfully access the feature, or when you need to understand how new, mid, and elder players will read the same feature differently.

carlheath Skill

Meta-skill for upgrading your Ogmios fork against future PAI versions (Daniel Miessler upstream). Structured process: clone PAI repo → diff against your config → classify ISCs (Isolated Strategic Changes) → build PRD → execute in phases → audit-preserve. [WHAT] Process skill that documents how to upgrade your Ogmios fork against upstream PAI releases without losing your customisations. [WHEN] Use when: PAI upgrade, miessler new release, upgrade fork from upstream, "new PAI version released". NOT for: feature requests on your own fork.