Product & Planning

richfrem Bundle

Interactive co-authoring skill for the wide end of the exploration funnel. Captures and refines the core intent, whether the outcome is a software app, a business process improvement, research analysis, or strategic roadmap. Guides users through gathering context, iteratively drafting the brief, and testing for blind spots.

richfrem Bundle

Builds a prototype component by component, self-reviewing each component against the Discovery Plan before moving to the next. Invoked by prototype-builder after the layout direction is confirmed. Trigger phrases: "build the prototype", "let's build it", "start building". Also invoked by prototype-builder-agent after visual-companion confirms layout.

zpankz Bundle

Routes tasks to skills in skill-db and skill-library using semantic discovery. Triggers on specialized skill requirements, domain-specific tasks, or explicit skill requests. Uses skill-discovery, mcp-skillset, and skill-rag-router for semantic matching.

zpankz Bundle

Discover and search 36,500+ skills via progressive Markov-chain traversal of semantic search hypergraphs. Use when (1) Users ask to find/search/discover skills or capabilities, (2) Users describe a task/problem needing specialized skills, (3) Users ask "what skills exist" or "show me skills for X", (4) Users want to explore or browse available skills, (5) Users ask meta-questions about skill discovery itself ("how do I find skills?"), or (6) No specific skill matches the user's need and discovery is appropriate

zpankz Bundle

Semantic skill discovery and routing using GraphRAG, vector embeddings, and multi-tool search. Automatically matches user intent to the most relevant skills from 144+ available options using ck semantic search, LEANN RAG, and knowledge graph relationships. Triggers on /meta queries, complex multi-domain tasks, explicit skill requests, or when task complexity exceeds threshold (files>20, domains>2, complexity>=0.7).

thewatcher01 Skill

Synchronize roadmaps, AGENTS.md, versions, and documentation across chainskills monorepo packages — use when updating version numbers, syncing roadmap status, or keeping documentation consistent

jacob-balslev Skill

Use when generating a wide range of solution concepts before converging on a direction, running structured idea-generation sessions, breaking out of solution fixation, or moving from divergent to convergent selection with explicit criteria. Do NOT use for collaborative engineering domain discovery (event-storming), solo deep technical design, or making final go/no-go investment decisions — those require different methods. Do NOT use for Decide whether to invest in this feature for the next quarter. Do NOT use for Model the bounded contexts for the order-fulfillment domain. Do NOT use for Write the production code for the selected concept.

delorenj Bundle

Produce a periodic project update for one pjangler project and one declared audience (internal or external), from Candystore, git, the ticket board and Hindsight, rendered as plain text, markdown and a self-contained HTML artifact, and emitted as one bloodbank.project.activity.recorded event. Use for "daily update", "client update", "internal update", "what did we ship", "periodic update", "activity report", "portal update", the nightly 03:00 run, a catch-up for a skipped window, or re-writing an update that lint refused. Do NOT use for the Surface operations payload (apps/surface, no free text), for roadmap checkpoints, for deploys, or for Bloodbank schema work (bloodbank-integration).

kevinnft Skill

Passive domain reconnaissance using Python stdlib. Use this skill for subdomain discovery, SSL certificate inspection, WHOIS lookups, DNS records, domain availability checks, and bulk multi-domain analysis. No API keys required. Triggers on requests like "find subdomains", "check ssl cert", "whois lookup", "is this domain available", "bulk check these domains".

jacob-balslev Skill

Use when designing or reviewing HTTP API surfaces: consumer tasks, audience class, protocol/paradigm fit, resources/actions, route taxonomy, request and response schemas, status codes in context, pagination, filtering, sorting, field selection, idempotency, auth and tenant boundaries, error envelopes, rate-limit signals, versioning, deprecation, discovery, and contract artifacts. Do NOT use for pure HTTP protocol semantics (use `http-semantics`), framework-specific route handler mechanics (use `route-handler-design`), non-HTTP system contracts (use `system-interface-contracts`), async event contracts (use `event-contract-design`), database design (use `entity-relationship-modeling`), inbound provider webhook mechanics (use `webhook-integration`), or post-failure diagnosis (use `debugging`). Do NOT use for define the broader contract between a job, service, and dashboard. Do NOT use for design database tables, foreign keys, and views.

jacob-balslev Skill

Use when classifying product features, service attributes, customer needs, or roadmap candidates with the Kano model: must-be/basic quality, performance/one-dimensional quality, attractive/delighter quality, indifferent quality, reverse quality, and questionable responses. Covers paired functional/dysfunctional survey design, segment-specific classification, feature-priority implications, category migration over time, and the boundary between Kano analysis and general backlog scoring. Do NOT use for generic RICE/ICE/MoSCoW ranking without customer-response evidence (use prioritization), open-ended research synthesis (use user-research or research-synthesis), or product-market positioning (use positioning). Do NOT use for Rank this backlog by reach, impact, confidence, and effort. Do NOT use for Synthesize these interview transcripts into research themes. Do NOT use for Design a generic quality-improvement process with DMAIC or PDCA.

jacob-balslev Skill

Use when applying Lean Startup methodology to validate a new venture, product, feature, program, or business model under high uncertainty: build-measure-learn loops, minimum viable products, validated learning, riskiest assumptions, actionable metrics, innovation accounting, learning milestones, and pivot/persevere decisions. Covers experiment design and learning discipline before scaling. Do NOT use for generative customer interviews alone (use user-research), synthesizing existing research (use research-synthesis), feature satisfaction classification (use kano-model), OKR goal-setting, product positioning, or quantified option valuation. Do NOT use for Plan interviews to discover what users need before we have a product concept. Do NOT use for Synthesize these interview transcripts into themes and insights. Do NOT use for Classify these roadmap items as must-be, performance, delighter, indifferent, or reverse features. Do NOT use for Turn this strategy into quarterly Objectives and Key Results.

jacob-balslev Skill

Use when diagnosing whether a business has, can build, or is falsely claiming durable strategic power using Hamilton Helmer's Seven Powers: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power. Covers Power as benefit plus barrier, persistent differential returns, moat-source classification, Power Progression by company phase, false-positive checks, and strategy implications. Do NOT use for industry-structure analysis alone (use porters-five-forces), integrated strategy-cascade formulation (use playing-to-win), generic prioritization, financial valuation, or surface-level SWOT lists. Do NOT use for analyze the attractiveness of this industry using entrants, suppliers, buyers, substitutes, and rivalry. Do NOT use for turn this market-entry plan into a winning aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for make a SWOT table for this company.

kevinnft Bundle

llama.cpp local GGUF inference + HF Hub model discovery.

jacob-balslev Skill

Use when choosing among actions under quantified uncertainty by enumerating outcomes, assigning probabilities, valuing each outcome in one shared unit, computing probability-weighted value, testing sensitivity, and checking downside constraints before recommending. Covers expected value, expected utility, expected monetary value, payoff tables, break-even probability, value of information, and risk-of-ruin constraints. Do NOT use for updating probabilities from evidence (use bayesian-reasoning), broad mixed-criteria backlog ranking (use prioritization), or tracing consequences before outcomes are modeled (use second-order-thinking). Do NOT use for Update these probabilities after new customer evidence. Do NOT use for Prioritize this backlog with RICE using reach, impact, confidence, and effort. Do NOT use for Trace the second- and third-order consequences before we model outcomes.

jacob-balslev Skill

Use when turning a vague business strategy, product strategy, market-entry decision, or initiative plan into an integrated Playing to Win strategy cascade: winning aspiration, where to play, how to win, must-have capabilities, and management systems. Covers Lafley/Martin choice-making, fit across the five choices, trade-off pressure, reverse tests, capability-system alignment, and the difference between strategy and planning. Do NOT use for competitive-industry structure analysis (use a five-forces skill when available), generic backlog scoring (use prioritization), or broad process-gate design (use methodology). Do NOT use for analyze whether this industry has attractive supplier power and threat of substitutes. Do NOT use for score these ten backlog items by impact and effort. Do NOT use for design a quality gate process for this multi-step implementation. Do NOT use for write OKRs for this strategy after it has already been chosen.

jacob-balslev Skill

This skill provides prioritization frameworks for AI engineering: RICE-A (adding AI Ambiguity to RICE) for product features, ICE for research experiments, and MoSCoW for MVP/Release scoping. Use when ranking the backlog, deciding which model research path to follow, or defining the scope of a new feature. Do NOT use for one-off task sequencing (use task skill) or personal time management.

jacob-balslev Skill

Use when balancing an innovation, growth, transformation, or venture portfolio across McKinsey's Three Horizons: Horizon 1 current core businesses, Horizon 2 emerging growth businesses, and Horizon 3 future options. Covers concurrent portfolio balance, resource allocation (the 70-20-10 benchmark and its caveats), evidence maturity, governance and metrics by horizon, metered funding, ring-fenced budgets, transitions from option to emerging business to core, the collapsed-time critique that disruption can now arrive on core timelines, and the risk that short-term core demands or incentives starve future growth. Do NOT use for BCG growth-share portfolio allocation (use bcg-matrix), Ansoff product-market growth path selection (use ansoff-matrix), Blue Ocean value-curve redesign (use blue-ocean-strategy), scenario construction and stress-testing across alternative futures (use scenario-planning), OKR goal-setting (use okrs), or quantified probability-weighted valuation (use expected-value).

kevinnft Skill

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

kevinnft Skill

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

jacob-balslev Skill

Use when building or operating multi-source intelligence pipelines across video, GitHub, Reddit, curated lists, search, and RSS feeds. Covers source adapters, discovery/transcription/summarization/evaluation phases, deduplication, schedules, model-stage choice, and actionable brief generation. Do NOT use for SEO keyword research (use `keywords`) or competitive product analysis (use `user-research`).

jacob-balslev Skill

Use when orchestrating a full human-centered design process across discovery, definition, ideation, prototyping, and testing — when uncertain which stage of the arc a team is in, when deciding whether to loop back, or when routing to the right stage-specific sibling skill. Do NOT use for single-stage execution (go directly to problem-framing, user-research, research-synthesis, journey-mapping, ideation, prototyping, or usability-testing) or for engineering domain discovery (use event-storming). Do NOT use for Run a single crazy-8s round on this specific how-might-we. Do NOT use for Write the React component for the dashboard widget. Do NOT use for Model the bounded contexts for the order-fulfillment domain. Do NOT use for single-stage divergent/convergent concept generation (use ideation).

delorenj Skill

Capture durable mental-model memories during a work session with the `jot` command, so the session-end hook can flush them into question-framed Hindsight memories. Use whenever you learn something worth remembering — a gotcha, a non-obvious decision, negative knowledge ("X did NOT work"), a surprising discovery, or a "future-me will ask this" fact — and you want it to survive past this session. Triggers:"remember this, "jot that down", "capture this", "note for later", "save this insight", mental model, write-ahead memory, hindsight capture.

delorenj Bundle

Create HTML timelines and roadmaps with status pills, dependency arrows, and milestone markers — for quarterly planning, project retrospectives, release histories, incident timelines, sprint visualizations. Use whenever the user wants to visualize a sequence of events over time, a plan, a roadmap, a release schedule, or look back at how a project unfolded. Reach for this whenever the explanation has a clear time axis, even if the user doesn't say "timeline".

delorenj Skill

ProductManager agent persona and operating prompt for feature candidate discovery. Use when the user asks for ProductManager, PM discovery, feature candidates, product opportunities, mock use, visual inspection, external research, ResearchPhase, BrainstormPhase, FeatureDocPhase, or ReportPhase. Loads with product-manager-research-phase, product-manager-brainstorm-phase, product-manager-feature-doc-phase, and product-manager-report-phase. Do NOT use for implementation, code review, sprint execution, or generic project management without discovery.

jacob-balslev Skill

Use when building, reviewing, or applying a Balanced Scorecard for strategy execution and performance management: destination statement, strategy map, perspectives, strategic objectives, strategic readiness, measures/KPIs, targets, initiatives, owners, review cadence, cascading, and learning from performance gaps. Covers financial/stewardship, customer/stakeholder, internal process, and learning/growth or organizational-capacity perspectives, with sustainability/ESG embedded or added as a fifth perspective when strategic, and adaptation for business, nonprofit, public-sector, product, and transformation contexts. Do NOT use for upstream strategy formulation alone (use playing-to-win), quarterly goal-setting alone (use okrs), technical service thresholds (use performance-budgets), portfolio allocation (use bcg-matrix), generic internal/external factor inventory (use swot-tows), probability-weighted option valuation (use expected-value), or activity-level value/cost decomposition (use value-chain-analysis).

jacob-balslev Skill

Use when updating beliefs, forecasts, diagnoses, or decision assumptions under uncertainty using Bayesian reasoning: priors/base rates, likelihood, evidence strength, posterior direction, and residual uncertainty. Covers base-rate discipline, likelihood-vs-posterior separation, independent evidence updates, natural-frequency examples, confidence calibration, and when to stop at qualitative probability instead of fake precision. Do NOT use for expected monetary value calculations, strategy-cascade choices (use playing-to-win), industry-structure analysis (use porters-five-forces), or generic task prioritization (use prioritization). Do NOT use for calculate the expected value of these three options. Do NOT use for turn this growth plan into a strategy cascade. Do NOT use for analyze supplier power and substitutes in this industry. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for build a statistical model from a dataset.

kevinnft Skill

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

kevinnft Skill

Discover and analyze trending GitHub repositories from TrendShift and other sources — evaluate usefulness, extract learnings, and identify valuable skills/tools

jacob-balslev Skill

Use when creating, auditing, or pressure-testing a Blue Ocean Strategy: value innovation, strategy canvas, Four Actions Framework, ERRC grid, six paths, buyer utility, noncustomers, and commercial viability. Covers reconstructing market boundaries, breaking the value-cost trade-off, shifting from competitor benchmarking to alternative/noncustomer insight, and turning the result into a new value curve. Do NOT use for industry-structure diagnosis alone (use porters-five-forces), durable moat classification (use seven-powers), or integrated five-choice strategy cascades (use playing-to-win). Do NOT use for analyze supplier power, buyer power, entrants, substitutes, and rivalry in this industry. Do NOT use for classify which durable moat this company has using Seven Powers. Do NOT use for turn this company strategy into aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap initiatives by impact and effort.

jacob-balslev Skill

Use when translating messy business requirements, stakeholder language, or early product ideas into an implementation-neutral domain model before database schemas, API endpoints, or DDD aggregates are named. Covers entities, attributes, named relationships, cardinality, identity criteria, specialization/generalization, aggregation/composition, reification, abstraction-level control, stakeholder validation, and modeling anti-patterns. Do NOT use for database ER diagrams with keys and normalization, formal ontology axioms with OWL/RDFS, or DDD tactical design; use those dedicated skills instead. Do NOT use for give me the physical table design with PKs, FKs, and normalization forms. Do NOT use for turn this model into SQL migrations and index definitions. Do NOT use for I need OWL class axioms and reasoning constraints for these concepts. Do NOT use for build the DDD aggregate boundaries and anti-corruption layer. Do NOT use for what hypernymy or meronymy labels apply between these two terms.

delorenj Skill

ReportPhase for ProductManager feature discovery. Use to create the final overview report, summarize ResearchPhase and BrainstormPhase outputs, list feature candidates, recommend next actions, package feature docs, and deliver results to a repo docs folder, vault, email, Telegram, or another requested channel. Triggers on ReportPhase, discovery report, feature candidate report, PM summary, deliver results, vault note, email summary, Telegram summary, and final recommendation. Do NOT use as a substitute for research or feature spec creation.

delorenj Skill

ResearchPhase for ProductManager feature candidate discovery. Use for product research, mock use, visual inspection, app walkthroughs, screenshot review, repo/document analysis, competitor research, market research, customer workflow evidence, and discovery evidence logs. Triggers on ResearchPhase, feature discovery research, product audit, inspect the app, use the product, visual QA for opportunities, and external research for feature ideas. Do NOT use for brainstorming or PRD writing without first gathering evidence.

delorenj Skill

BrainstormPhase for ProductManager feature candidate discovery. Use to turn ResearchPhase evidence into possible feature candidates, opportunity clusters, candidate matrices, RICE-style scoring, user-value scoring, effort/risk estimates, prioritization, and top recommendations. Triggers on BrainstormPhase, candidate generation, feature ideas from research, opportunity matrix, rank feature candidates, prioritize product ideas, and synthesize opportunities. Do NOT use before a research artifact or evidence base exists.

delorenj Skill

FeatureDocPhase for ProductManager discovery. Use to write detailed PRD-like feature docs from a selected candidate, including problem framing, evidence, goals, non-goals, UX requirements, data/API notes, acceptance criteria, risks, rollout, metrics, dependencies, and implementation handoff. Triggers on FeatureDocPhase, PRD-like feature doc, product requirements, feature spec, acceptance criteria, implementation-ready candidate, and write the chosen feature. Do NOT use for raw ideation or broad reports.

delorenj Bundle

Scaffold and populate a Requirements Management & Traceability Register — a multi-sheet spreadsheet that tracks project requirements from scoping through execution to acceptance and testing. Use when the user wants a requirements tracker, traceability register or matrix (RTM), acceptance matrix, phase-based requirements workbook, or a requirements dashboard in Google Sheets or Excel — built from a Lists validation tab, per-phase registers (P1/P2/P3) on a shared 21-column schema, an aggregated All Requirements master (VSTACK/QUERY), Traceability and Acceptance Matrix views, and COUNTIFS metric cards. Triggers include requirements traceability matrix, requirements register, acceptance criteria matrix, requirement ID, trace tags, phase gate, requirements dashboard, requirement statement. Do NOT use to author a PRD (use bmad-create-prd), run a Plane/Trello ticket board (use `momo` for 33GOD board orchestration; use `project-lifecycle` for direct Plane ticket CRUD outside 33GOD), or build a Gantt/timeline (use htm