Product & Planning

muvon Skill

Explains how octomind assembles a session at runtime: tap resolution of category:variant tags, manifest placeholders, capability activation and the deterministic embedding auto-activator, domain gating, LRU eviction of the tool surface, skill discovery and the three activation methods, local .agents/tools scripts, and sandbox mode. Activate when a user asks why a tool or skill did or did not appear, how a tag resolves, how capability auto-activation decides, why a capability was evicted or refused, or where skills and taps live on disk.

muvon Bundle

Operational skill for landing genuine editorial guest posts that earn high-quality contextual links without triggering the Oct-2025 spam update on guest-post farms. Encodes the 7-stage workflow (author tier-mapping, discovery operators, 11-point site qualification, content-gap topic ideation, 80–150-word pitch architecture, post writing standards by tier, internal-link strategy, anchor distribution, follow-up). Bakes in Google's hard kill-rules (paid networks, repetitive exact-match anchors, duplicate content, AI-content farms), the data-backed anchor distribution (40-50% branded, <10% exact-match, 68% penalty reduction with diversification), and link-placement rules (1-2 contextual body + 1 bio = 387% more referral traffic than bio-only). Use BEFORE writing any pitch. Stays in the SEO lane: produces strategy, target list, topics, pitch brief — does not write the email or post itself.

viktorbezdek Bundle

Psychological elicitation and deep-interview design using narrative identity (McAdams), self-defining memories (Singer), Motivational Interviewing (Miller & Rollnick OARS), values elicitation (Schwartz), schema detection (Young), and life review (Haight/Birren). Use when designing user interviews that need to reveal motivations rather than stated preferences, writing conversation flows for personal discovery, auditing interview scripts for interrogation anti-patterns, building conversational AI that understands users over time, drafting life story or personal history products, or critiquing a conversation transcript for missed depth. NOT for clinical diagnosis, therapy, or treatment planning. NOT for structured data capture or survey design (use standard survey tools). NOT for persona creation from scratch (use persona-definition). NOT for stakeholder mapping (use persona-mapping).

viktorbezdek Bundle

Git workflow management — use when the user mentions git, conventional commits, commit quality, branch management, worktree operations, GitFlow, changelog generation, semantic versioning, release notes, backlog management, or issue tracking integration. NOT for CI/CD pipelines or pipeline YAML (use cicd-pipelines), NOT for non-git workflow orchestration (use skillstack-workflows or multi-agent-patterns), NOT for code review content or PR quality assessment (use code-review).

viktorbezdek Bundle

Validates a plugin idea by surveying the marketplace, reading authoritative Anthropic sources, and deciding build-vs-fork-vs-skip before writing any code. Use when you want to research existing Claude Code plugins, check whether there is already a plugin for X, decide whether to build a new plugin or fork an existing one, run a marketplace survey before starting work, find authoritative documentation on a Claude Code feature, or gather primary sources for a plugin design. Covers the marketplace survey methodology, the canonical list of authoritative Anthropic URLs (code.claude.com, docs.claude.com, platform.claude.com, github.com/anthropics/claude-code, github.com/anthropics/skills, the Complete Guide PDF), community pattern discovery, and the build-vs-fork-vs-skip decision gate. NOT for deciding whether an idea is worth pursuing (use plugin-ideation) or for designing component layout (use plugin-architecture).

viktorbezdek Bundle

Apply RICE, MoSCoW, ICE, and effort-impact frameworks to rank options and decide what to work on next. Use when the user asks to prioritize a backlog, rank features, decide what to build first, apply RICE or MoSCoW scoring, cut scope, or compare items by effort vs impact. NOT for defining success metrics or OKRs (use outcome-orientation). NOT for making a strategic bet under uncertainty (use strategic-decision workflow).

viktorbezdek Bundle

Map stakeholders across organizations using Power-Interest matrices, RACI charts, influence analysis, and salience models to understand who has authority, who is affected, and how to engage each group. Use when the user asks to map stakeholders, create a RACI matrix, analyze organizational influence, identify decision-makers, prioritize who to involve, or plan stakeholder communication. NOT for individual user personas or empathy maps for product design (use persona-definition). NOT for designing the product's target audience (use persona-definition).

viktorbezdek Bundle

Align stakeholders in writing using RFCs, design docs, proposals, pre-reads, and decision docs with explicit role assignments (DACI, RAPID). Use when the user asks to write an RFC, design doc, proposal, pre-read, or decision doc, wants to align async stakeholders on a decision, needs to assign deciders vs consulted vs informed, wants to structure a cross-team proposal, or is preparing a pre-read for a decision meeting. NOT for structuring a generic memo (use structured-writing). NOT for stakeholder power maps (use persona-mapping). NOT for storytelling pitches or investor decks (use storytelling-for-stakeholders).

viktorbezdek Bundle

Analyze trade-offs between competing product options using cost-benefit, opportunity cost, reversibility (one-way vs two-way doors), and second-order effects. Use when the user faces a product choice with non-trivial trade-offs, asks "what are we giving up", weighs short-term vs long-term impact, or needs to frame a decision before committing. NOT for scored prioritization of a backlog (use prioritization). NOT for quantified risk assessment (use risk-management). NOT for strategic go/no-go (use strategic-decision).

viktorbezdek Bundle

Decide what and when to write down, and produce Architecture Decision Records (ADRs), one-pagers, runbooks, and decision logs. Use when the user asks whether something should be documented, wants to write an ADR, needs a runbook or operational playbook, wants to keep a decision log, or is trying to decide between a one-pager and an RFC. NOT for auto-generating docs from code (use documentation-generator). NOT for end-user tutorials or how-tos (use example-design). NOT for docs-site information architecture (use navigation-design). NOT for cross-team alignment via RFCs (use stakeholder-alignment).

viktorbezdek Bundle

Apply outcome-over-output product thinking — separating what gets built from what actually changes for the user, running the "so what" test to climb from output to outcome to impact, choosing leading vs lagging metrics, and identifying a North Star metric. Use when the user asks whether something is an outcome or an output in a product context, wants to run the "so what" test on a deliverable, wants a North Star metric, needs to choose leading indicators for a product bet, or is debating whether shipping a feature equals success. NOT for generic OKR authoring (use outcome-orientation). NOT for feedback-loop analysis (use systems-thinking). NOT for metric scoring or ranking (use prioritization).

viktorbezdek Bundle

Identify what users actually need using functional/emotional/social jobs, needs-vs-wants laddering, latent-need surfacing, and job statements. Use when the user asks what users truly need, wants to write a job statement (When/I-want-to/So-I-can), wants to move past stated wants to underlying needs, needs to separate functional jobs from emotional or social ones, or wants to spot latent needs the user cannot articulate. NOT for persona demographics (use persona-definition). NOT for stakeholder power maps (use persona-mapping). NOT for interview scripting (use elicitation).

viktorbezdek Bundle

PM funnel workflow for turning user research into prioritized engineering stories — product story, user research to backlog, user needs to stories, PM workflow. Chains elicitation (deep interviews that surface real needs), user-journey-design (touchpoints, pain points, emotions), persona-definition (who we're building for), outcome-orientation (measurable success criteria), and prioritization (RICE/MoSCoW/ICE scoring). Use when translating user research into engineering work, when the backlog is unranked feature requests, when launching a new product from interviews to sprint-ready stories, or when the team builds features nobody asked for. NOT for technical architecture — use strategic-decision. NOT for backlog grooming without new research — use prioritization directly.

yogsoth-ai Skill

Multi-source cross-validation of gap authenticity — cross-database search, temporal sensitivity testing, false-gap filtering, stakeholder confirmation.

yogsoth-ai Skill

Map all affected parties using CSH 12-question framework, identify jobs-to-be-done, classify by salience. Reveals whose perspective is systematically excluded.

yogsoth-ai Bundle

Search for positive deviants and extract transferable principles using Appreciative Inquiry.

yogsoth-ai Skill

Multi-dimensional gap scoring and ranking — define criteria, score, weight, rank, sensitivity-check. Combines multi-criteria-scoring, stakeholder-confirmation, and feasibility assessment.

yogsoth-ai Bundle

Simulate stakeholder perspectives to validate gap priorities. Assesses gap value from researcher, practitioner, funder, and end-user viewpoints.

yogsoth-ai Skill

Apply CATWOE from multiple stakeholder viewpoints and reframing matrix to reveal aspects invisible from the dominant perspective.

yogsoth-ai Skill

Identify research gaps via PICOS frameworks, concept matrices, evidence gap maps, keyword extraction, citation analysis, and topic modeling. Systematic discovery of what is missing in the literature.

yogsoth-ai Skill

Score and rank validated gaps on importance, feasibility, novelty, and urgency. Multi-criteria decision analysis with stakeholder confirmation.

yogsoth-ai Bundle

Simulate multiple stakeholder perspectives evaluating a research gap, method, or proposal. Identifies blind spots from single-perspective analysis.

criptogus Skill

Analyze stock correlations — co-movement discovery, return correlation, sector clustering, and rolling/regime-conditional realized correlation, with practical context. Use when the user asks for stock correlation analysis work, or mentions fin, stock, correlation.

criptogus Skill

Critiques discovery calls against pain, impact, decision criteria, and next-step quality; returns drills. Use when the user asks for gtm discovery call coach work, or mentions gtm, discovery, call.

aradotso Skill

AI Agent learning roadmap and curated resources for building production-ready agents with modern patterns like Claude Code, OpenClaw, skills, MCP, and evaluation

aradotso Skill

Structured learning roadmap for AI Agent development from LLM basics to multi-agent systems (bilingual Chinese/English)

aradotso Skill

AI-powered SAST pipeline for autonomous vulnerability discovery using LLMs with multi-stage analysis, threat modeling, and SARIF output

aradotso Skill

A minimal teaching framework for understanding AI Agent architecture with core loop, fake LLM interface, and skill discovery system

rweisssieker-xp Skill

Use when partners, sales teams, solution sellers, consulting leaders, pre-sales architects, or account teams need AX to D365FO discovery workshop kits, assessment offers, proposals, SOWs, pricing assumptions, or client executive pitch packs.

rweisssieker-xp Skill

Use when exporting AX to D365FO migration backlog, risks, Azure DevOps work item CSV, or analyzer tasks into GitHub issue Markdown files for teams that do not use Azure DevOps.

rweisssieker-xp Skill

Use when a project manager, program manager, PMO, scrum master, delivery lead, workstream lead, or steering coordinator needs AX to D365FO migration planning, status, RAID, RACI, governance, milestones, scope control, backlog, or stakeholder communication.

rweisssieker-xp Skill

Use when preparing or running AX to D365FO steering committee, executive review, board update, gate review, decision meeting, escalation session, or stakeholder alignment across CEO, CIO, CISO, PMO, and delivery leads.

rweisssieker-xp Skill

Use when technical runbooks for AX discovery, X++ export, modelstore, D365FO metadata, DMF, security, integration, reports, testing, or cutover.

rweisssieker-xp Skill

Use when stakeholder communication, emails, steering updates, executive briefs, status notes, escalation messages, or meeting summaries.

selamy-labs Skill

Use when turning stakeholder, reviewer, customer, beta, analytics, or interview feedback into product decisions, tracked work, evals, experiments, or an explicit decision to gather more evidence.

selamy-labs Bundle

Use when translating authoritative project knowledge into stakeholder-facing Google Docs, Sheets, dashboards, journey evidence, or human task lists. Preserves source authority, audience-specific detail, native collaboration structures, protected manual decisions, assignment consent, freshness, and sync auditability.