Product & Planning

legioncodeinc Bundle

Rebuild the sales pipeline that lives in your head. Trigger on 'what deals do I have open', 'rebuild my pipeline', 'my CRM is empty', 'who am I about to lose', 'which deals went cold', 'what did I quote and to whom', 'build my deal board', 'who hasn't replied to my proposal'. Reconstructs deals from captured DMs, discovery calls, proposals seen on screen, quotes sent and calendar holds into a stage-by-stage board with last-touch recency, a ranked going-cold list, and one next action per deal. Every stage is an inference and shows its evidence. Internal artifact only. Never contacts a prospect.

lklimek Skill

This skill should be used when the user asks to "merge dependabot PRs", "process dependency bumps", "auto-merge bot PRs", or "handle the dependabot backlog". It audits each dependency, comments findings, merges when CI is green, and requests rebases for conflicts or CI failures.

full-stack-skills Bundle

Discover, evaluate, score, and compare Rust crates for adoption — search crates.io, fetch metadata from 4 sources (crates.io API, docs.rs, GitHub API, RustSec advisory DB), apply a weighted 0-100 scoring model across adoption/maintenance/documentation/maturity/community/license, flag red concerns (unmaintained, advisories, no docs, single-maintainer), and recommend the best fit. Use when users ask "which crate should I use for X", "is this crate maintained/safe/popular", "compare these 3 crates", or need to pick a dependency before adoption; hand post-adoption governance (cargo-deny, license policy, advisory response) to rust-dependencies, semver and breaking-change classification to rust-semver, and manifest mechanics to rust-cargo-build.

full-stack-skills Bundle

Generate walkthrough videos from Stitch projects using Remotion. Retrieves screens via Stitch MCP list_projects list_screens get_screen downloads screenshots, builds Remotion composition with transitions and text overlays. Use with stitch-mcp-* for project/screen discovery.

full-stack-skills Bundle

Expert guidance for integrating and building applications with shadcn/ui. Component discovery, installation npx shadcn@latest add customization, blocks, and best practices. Use with Stitch-generated React apps for consistent, accessible UI built on Radix/Base UI and Tailwind.

gitbyeos Bundle

将 OKR Markdown 生成为可切换 Objective 的单页 HTML 看板。用户提到 okr-to-html、OKR 转网页、季度目标 HTML 时使用。

hoetaek Bundle

Capture or resume a LEAF sprout for explicit learning, durable records, or structured discovery of core unresolved decisions. Route ordinary clear tasks through using-leaf first.

hoetaek Bundle

Route explicit LEAF work or work needing structured discovery and design; keep clear ordinary tasks direct. Injected at session start.

huifer Skill

Phased UX improvement plan with prioritized fixes for navigation, ad placement, typography, accessibility, and mobile optimization. Includes design recommendations and implementation timelines.

sirkirby Skill

Activate this skill when adding a new manager, adding a new tool category, writing or debugging tool unit tests, diagnosing tool-visibility failures, investigating startup performance, or extending/maintaining/debugging the two-tier tool discovery system (`tool_index`) — even if the user doesn't explicitly ask about the runtime architecture or "tool discovery." Covers: (1) the four-stage bootstrap sequence and which layer owns which changes, (2) adding a new manager via @lru_cache singleton factories in runtime.py, (3) the three-stage decorator replacement system that enables test isolation without a live controller, (4) lazy loading mechanics and tools_manifest.json regeneration that controls which tool categories are visible, (5) the permission model's two safety axes, and (6) the two-tier tool_index discovery layer: the FastMCP named-param wrapper vs. the silent `args: dict` trap, compact-vs-full schema tiers (`include_schemas`), Worker cloud parity, and SKILL.md runtime manifest sync.

skills-il Bundle

Best practices for using browser-use/video-use to edit Hebrew videos end-to-end with Claude Code. Covers the Hebrew-specific deltas to video-use's 12 Hard Rules: SUB_FORCE_STYLE override (Helvetica has no Hebrew glyphs), the python-bidi pre-shape recipe for libass+SRT BiDi failures on macOS, Hebrew filler-word post-pass on Scribe word timestamps, fontsdir= parameter for reliable font discovery, takes_packed.md handling for Hebrew with sofit/nikud/code-switching, and animation slot guidance that defers to hyperframes-best-practices and remotion-best-practices. Use when editing Hebrew talking-head video, podcast clips, tutorials, or marketing video with video-use. Do NOT use for non-Hebrew video-use sessions (read upstream SKILL.md directly), Hebrew podcast audio-only post-production (use hebrew-podcast-postproduction), or generic FFmpeg work without video-use orchestration.

skills-il Bundle

Navigate the fragmented landscape of Hebrew and Yiddish ML datasets and models. Covers ivrit.ai (20K+ hours of Hebrew audio, whisper-large-v3 ASR variants, Yiddish models), Dicta (DictaLM 3.0 LLM family, DictaBERT variants, HeQ reading comprehension), the Israeli National NLP Program / NNLP-IL (HebrewSentiment, HebNLI), AlephBERT, and Knesset Plenums. Helps researchers and ML engineers pick the right dataset for a task by use case, license (commercial vs research), Hebrew register coverage, and model-dataset pairing. Use when choosing training data for a Hebrew NLP or ASR project, verifying license compatibility for a commercial product, finding a baseline model for a Hebrew downstream task, or exploring Yiddish ML resources. Do NOT use for Arabic NLP datasets (a separate ecosystem), general HuggingFace dataset discovery (use HuggingFace Hub search), or Hebrew OCR dataset selection (use hebrew-ocr-forms).

vemodalen-x Bundle

Decompose a PRD / requirements document into a structured, governable breakdown — functional & non-functional requirements, acceptance criteria, work-breakdown by stage/agent, requirement→stage traceability, and a coverage check. Use at project kickoff or a major new feature, when the orchestrator must turn a PRD into actionable, traceable work before research/build begins. Owned by Framework 0 (orchestration).

microsoft Skill

Delivery-risk reviewer that sizes a plan's investment against the team's real confidence it will land. Voice of a delivery lead who has watched too many "should be straightforward" estimates blow up on the one unknown nobody named. Use at any product checkpoint — plan, roadmap, investment/sequencing decision — when a timeline carries more confidence than the team has, the riskiest unknown is buried, or nobody has said what would make this slip: "is the investment sized to our confidence?"

microsoft Skill

Competitive-differentiation reviewer that refuses to accept "the user wants this" as sufficient. Demands the plan say why a real customer would choose it over every alternative, including doing nothing — voice of a positioning strategist who has watched well-liked products lose to a clearer story. Use at any product checkpoint — plan, roadmap, go-to-market framing — when nobody can say why users would switch or pay, the competitive landscape is unaddressed, or "no one else does this" is asserted without checking: "why us, why this, why now?"

microsoft Skill

Outcome-validity reviewer that refuses to count shipped work as progress until it maps to a measurable change in behavior. Hunts the gap between "we shipped it" and "we moved the number" — the output mistaken for an outcome. Use at any product checkpoint — plan, roadmap, PRD, ship review — when deliverables carry no metric, "done" is confused with "worked," or nobody can say how success will be measured: "what measurable outcome defines success, and how will we know we moved it?"

microsoft Skill

Convene the Product Development Council on the CURRENT conversation — the plan, roadmap, or scope decision built in this session. The INLINE counterpart to /product-council (which forks isolated and cannot see the chat). Use when you want the council to critique what we're working on right now.

moonlarry Skill

Turn a stable research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `paper-plan`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.

owl-listener Skill

Write a clear program status report with RAG status, progress, risks, and asks.

owl-listener Skill

Turn a roadmap into an executable delivery plan with owners and dates.

owl-listener Skill

Build a UX program roadmap with outcomes, phases, milestones, and dependencies.

owl-listener Skill

Define escalation paths and the triggers that activate them.

owl-listener Skill

Map stakeholders by influence, interest, and current stance.

owl-listener Skill

Craft a concise executive update tied to business outcomes.

owl-listener Skill

Design a workshop to align stakeholders on goals, scope, or direction.

owl-listener Skill

Link program work to OKRs and measurable outcomes.

poorvith-mp Bundle

Structure discovery calls: question design, current-state mapping, and gap quantification. Use when running sales discovery calls or BANT qualification.

poorvith-mp Skill

Moved to modernized catalog in skillary. Removed in v4.1.

sergio-bershadsky Bundle

This skill should be used when the user asks to "create a PRD for Replit", "write product requirements", "document app specifications", "prepare a product spec", or needs a comprehensive specification document that Replit Agent can use for complex, multi-feature applications. Creates structured PRDs optimized for AI-powered development.

sergio-bershadsky Bundle

This skill should be used when the user asks to "create task", "add todo", "track action item", "create ticket", "new task", "remind me to", "need to do", "add to backlog", or mentions needing to track work items with priority and status in their secondbrain.

sergio-bershadsky Skill

This skill should be used when the user asks for "freshness check", "freshness report", "what needs attention", "stale items", "review backlog", or mentions wanting to see what secondbrain content needs review or updating.

varunk130 Skill

Systematic unmet-needs discovery engine that maps gaps between market demand and existing solutions with quantified opportunity scores. Use when: find opportunities, unmet needs, market gaps, opportunity discovery, what should we build, where is the whitespace.

chrislacey89 Bundle

Primary pipeline entry for structured requirements discovery. Use first when the problem, scope, or user needs are still fuzzy and you need shared understanding before /research. Not for already-shaped PRDs or implementation-ready work.

chrislacey89 Bundle

Primary pipeline execution step after /prd-to-issues or for clearly scoped implementation work. Use to build, verify, and commit a concrete slice, delegating to /tdd for backend work and behavior-heavy frontend logic when red-green-refactor will reduce risk. Not for shaping or pre-merge review.

chrislacey89 Bundle

Primary pipeline tail step after /pre-merge, when a reviewed PR is ready to land and you want the workspace back to a clean base. Use to merge, switch off the worktree before removing it, prune the merged branch, pull base, and verify a clean end state. Triggers on 'close out', 'merge and clean up', 'get back to a clean main/base', 'tear down the worktree'. Not for capturing lessons (that's /compound) or closing PRD/slice issues and research-artifact hygiene (that's the cleanup prose in SYSTEM-OVERVIEW Step 9).

chrislacey89 Skill

Primary pipeline knowledge-capture step that closes the compounding loop. Capture a durable lesson in docs/solutions/ onto the open PR before /closeout merges (the default), or post-merge when the lesson only surfaces during/after merge. Use so future /research and /write-a-prd runs improve. Not for trivial edits with no reusable project-level learning, and not for the merge/teardown itself (that's /closeout).