Product & Planning

aneviaro Skill

Maintain a project's backlog by adding, updating, or creating docs/backlog.md. Use when the user asks to record a future improvement, backlog item, TODO, or planned enhancement in project documentation.

aneviaro Skill

Relentlessly interview the user to sharpen a vague idea into an actionable implementation spec, then save that spec to the repository. Use when the user wants to refine an idea, stress-test a concept, build a spec, write a PRD, or says "hone this idea", "grill me", "turn this into a spec", or similar.

larsboes Bundle

Operates Axon and guides work on the Axon repository through dynamic discovery, bounded self-context, capability APIs, architecture placement, focused branches, and proportionate verification. Use when operating Axon services or feeds, diagnosing Axon, planning or coding inside the Axon repository, deciding where Axon code belongs, or handling Axon branches and PRs. Do not use for unrelated repositories, direct Home Assistant or device control, or generic prose and skill authoring with no Axon decision.

larsboes Bundle

Drives Axon's travel capabilities as one workflow — feasible days from calendar, journey search and split tickets from transit, measured delay history from punctuality, event discovery from scouting, and plan state in trips. Use when planning a trip, searching connections or fares, checking how late a train usually runs, or turning a discovered event into an itinerary. Do not use for home network or Home Assistant work, and never work from a remembered route or port — ask the service.

larsboes Bundle

Queries an AVM Fritz!Box (7590/FRITZ!OS) read-only over two transports — TR-064 via fritzconnection for the authoritative host table, and the AVM JSON API (login_sid.lua + data.lua) for what TR-064 cannot see: active channel and width per band, DFS exposure, mesh topology with per-AP client counts, the timestamped WLAN event log, and subsystem load. Credentials come from a Bitwarden item at runtime, never hardcoded. Use when listing network devices, checking what is on the network, Fritz!Box device discovery, WLAN clients, guest-WiFi status, spotting an unknown device, or diagnosing a slow or unstable WLAN (channel width, DFS/radar eviction, repeater backhaul, airtime saturation). Do not use for Home Assistant entity control (use ha-cli), DNS or ad-blocking (use pihole), local subnet scanning and drift (use netmon), or non-Fritz routers.

larsboes Bundle

Monitors a home LAN and its traffic from the local host — active host discovery with MAC and vendor, per-host open-port scans, a saved baseline plus drift diff (new/missing devices), WAN throughput totals, and DNS-egress visibility (which domains each device phones home to) via the resolver's query log. Subnet is auto-derived from the primary interface or set by env/flag; Fritz!Box throughput credentials come from a Bitwarden item at runtime, never hardcoded. Use when scanning who is on the network, spotting a new or unknown device, checking open ports, watching bandwidth or WAN throughput, auditing what a device phones home to, or baselining and diffing the network. Do not use for the router's own authoritative device list (use fritz), or filling and deploying Home Assistant automation templates (use homectl).

larsboes Bundle

Turn unstructured input — a raw brainstorm, a pile of notes, scattered ideas, a half-written PRD — into one precise document where every claim is grounded in the actual repo or vault and every decision is dated with its reasoning. Drives the process through batched multiple-choice questions rather than open-ended prompts, because the user has the judgment and you have the ability to measure. Use this whenever someone says "help me think this through", "make this precise", "turn this into a spec/PRD/plan", "I have a bunch of notes and no structure", "brainstorm with me", "ask me questions", "finalize this doc", or hands you a rambling document and asks what to do with it. Also use it when a document and the system it describes have drifted apart and you need to find out which is lying.

michelve Skill

Creates well-formed tasks following a template that engineers can implement. Triggers on: 'create tasks', 'define work items', 'break this down', creating tasks from PRD, converting requirements into actionable tasks, feature breakdown, sprint planning.

gaintrace Bundle

When the user has a customer conversation coming up and needs to walk in prepared. Also use when the user mentions 'prep me for', 'brief me on', 'I have a call with', 'meeting with', 'call tomorrow', 'what do I need to know', 'account brief', 'call prep', 'one-pager on', 'catch me up', 'who am I talking to', 'who has to say yes on their side', 'I know nothing about them', or 'I'm covering for'. Use this whenever a customer conversation is imminent, even if they don't ask for a brief and only mention the meeting in passing. For the QBR deck itself, see qbr-builder. For what to send afterwards, see post-call-followup. For risk depth, see churn-risk. For who is in the room, see stakeholder-map.

gaintrace Bundle

When the user wants to know who they actually know inside an account, who is missing, and how much money depends on one person staying — relationship mapping, multithreading, champion risk and executive sponsor coverage. Also use when the user mentions 'who do we actually know', 'who else do we have', 'stakeholder map', 'relationship map', 'org chart', 'who are the key contacts', 'who is the decision maker', 'economic buyer', 'our champion left', 'my champion is leaving', 'single-threaded', 'multithreading', 'who else should I know', 'power map', 'coverage gap', 'exec sponsor', 'new stakeholder', 'who actually signs', 'someone is blocking us', 'they love us but nothing moves', or 'my main contact went quiet'. Use this whenever an account's renewal depends on one human being, even if they never say 'stakeholder'. For the attendee read before a specific meeting, see pre-call-brief. For account-wide risk scoring, see churn-risk. For the relationship section of a renewal runbook, see renewal-prep.

gaintrace Bundle

When the user must decide whether to build something bespoke for one customer, generalise it, work around it, or say no — priced on the carrying cost, not the build cost. Also use when the user mentions 'wants something bespoke', 'cost us long term', 'build this custom', 'should we build this', 'build it or push it to product', 'they want a custom', 'one-off for this customer', 'is this worth building', 'how do I say no to this', 'the deal depends on us building it', 'we'll productise it later', 'bespoke work', 'custom connector', 'roadmap collision', 'what will this cost us to maintain', or 'can we just hack it for them'. Use this whenever someone is deciding what gets built for a single account, even if they never say 'custom' — a 'quick script', a 'small tweak' and a pilot hack that reached production are all this decision. For the SOW that governs agreed work, see fde-scoping. For what is already built and what it costs, see fde-account-plan.

howells Bundle

Reprioritize a project's backlog for a goal. Not implementation (`next`).

hyperfx-ai Skill

Research Reddit discussions with high signal using scrape_reddit_leads and scrape_reddit — pain points, intent discovery, and trend tracking. Use when the user wants to mine subreddits for leads, find threads worth replying to, or track what a community says about a topic.

hyperfx-ai Bundle

Plan and manage OpenAI Ads (ChatGPT ads) campaigns end-to-end via the Hyper MCP — API-key auth, account discovery, geo targeting, image upload, chat_card and product-feed creatives, custom audiences, conversion tracking, status flow, and insights, with integer-micros money values. Use when the user wants to launch OpenAI ads, ChatGPT ads, chat card ads, manage OpenAI ad groups or audiences, or pull OpenAI Ads insights.

multiplex-ai Bundle

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".

echovic Bundle

可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程', '自动化开发', '一键开发', 'start a project', 'new feature' Does NOT trigger: - 单文件修改或简单 bug 修复（直接编辑即可） - 纯代码阅读或解释（使用 read 工具） - 已有 pipeline 正在运行时的重复启动 - 极小事（预计 <30 分钟人工可完成、不需要 PRD/架构/门禁记录） Output: 完整项目代码 + PRD/架构/UI/测试/部署文档，写入 .boss/<feature>/ 目录

echovic Skill

产品需求文档(PRD)的标准编写格式和内容要求，确保输出完整、清晰、可执行的产品文档

elzawarudo Bundle

Supports standalone and Seneschal-nested delivery with per-run state, inherited initiative contracts, and brokered decisions. Discovery-gated artifact-first orchestrator for compound-engineering product delivery. Resolves roadmap/readiness generation, runs brainstorm/plan/document-review loops, derives mergeable work packages with focused review units, executes each review unit through resolved work/code-review roles, and hands shipping to krt-release-marshal with CI break-prevention evidence. Use when turning an existing documented software project into a sequenced roadmap and PR/Jira delivery program. Runtime aliases may expose this as krt:compound-master.

elzawarudo Bundle

Turn validated software requirements into a practical project delivery plan. Use when a user has a requirements packet, especially one produced by krt-requirements-weaver, and needs project planning artifacts such as scope framing, major tasks, prioritized backlog, milestones or iteration slices, schedule outline, team responsibilities, technology choices, dependencies, risks, and partial deliveries. Also use when the user asks how to build the system, how to organize the work, how to phase delivery, or how to plan the backlog before implementation. Runtime aliases may expose this as krt:delivery-navigator.

elzawarudo Bundle

Generate exactly one roadmap or readiness report for a documented initiative. Validates context sufficiency, maps source-backed roadmap items, dependencies, waves, and branch/PR strategy, or blocks with actionable readiness guidance. Use when a user needs a roadmap before compound delivery, or when krt-compound-master resolves its required roadmap_generator role. Runtime aliases may expose this as krt:roadmap-cartographer.

elzawarudo Bundle

Orchestrates a comprehensive, evidence-based polish audit of web, mobile, and desktop applications through a versioned atlas, a cartographer, and twelve evaluators, with a required cognitive-load overlay on every finding. Use when asked to polish an application, assess its product maturity, walk end-to-end flows, find rough seams or amateur behavior, produce a prioritized improvement backlog, or verify that a round of changes raised perceived quality.

fredrikaverpil Bundle

Native Neovim config idioms and conventions — use whenever writing, reviewing, or modifying any Neovim configuration that uses Neovim's built-in conventions WITHOUT a plugin manager framework (no lazy.nvim, packer, etc.). Covers directory structure, vim.pack plugin management, lsp/ auto-discovery, plugin/ loading order, keymaps, and standard paths. Trigger on any task involving init.lua, plugin/*.lua, lsp/*.lua, vim.pack.add(), vim.lsp.enable(), or "native neovim config" — even if the user just says "add a plugin" or "configure LSP" in a native-style config.

rynhardt-potgieter Skill

Linear MCP integration patterns — issue taxonomy (Epic/Task labels), Milestone-based sprint grouping, status lifecycle, label definitions, query patterns, creation patterns, retry handling, and team/project discovery. Use this skill when sprint tracking is routed through Linear instead of markdown files.

rynhardt-potgieter Skill

Detect architectural drift and erosion by comparing implemented or planned work against the project's Linear "Architecture & Roadmap" document. Use this skill in /sprint-plan and /sprint-enrich (planning-time drift), in /sprint-start Phase 3 QA and code review (implementation-time drift and erosion), and in /sprint-retro (sprint-level drift summary). Defines drift vs erosion, the reflexion-modeling comparison method, severity rules, the standard report format, and the conditions under which the check is skipped gracefully.

stefanoskarakasis Bundle

Guides Product Managers and Product Marketing Managers to co-create complete Product Requirements Documents with embedded Solution Stories. Reads brain context (positioning, ICP, Revenue Levers) to anchor PRDs in strategy. Outputs: structured Solution Story for GTM communications + full PRD for execution alignment.

stefanoskarakasis Bundle

Guides Product Marketing leaders and individual PMMs through building a complete, export-ready OKR set for their quarter — including Objective, Key Results, Projects, Scorecard metrics, and Exec Summary language. Use when setting quarterly OKRs, reviewing existing OKRs, stress-testing KR quality, or building a measurement plan. Trigger on: "help me set our OKRs", "are my KRs measurable", "build a scorecard", "stress-test this KR", "write OKRs for my team", "present goals to exec team". Produces output paste-ready for the PMM OKR Builder spreadsheet or leadership sharing.

stefanoskarakasis Bundle

Rewrites and sharpens B2B written communication into sendable, high-signal copy while preserving the writer's real voice, or drafts it from scratch when none exists. Use when someone wants to rewrite, tighten, or draft a Slack message, email, memo, PRD, or marketing copy, or asks why their copy isn't landing.

stefanoskarakasis Bundle

Builds political maps (not org charts) showing who can kill your launch, who champions it, and what to say to each stakeholder. Reads brain context (ICP, positioning, GTM motion) and guardrails from prior stakeholder mapping sessions; produces Power × Interest grid with political role assignment, conflict map, and weekly Sprint Cards for execution.

stefanoskarakasis Bundle

Customer interview synthesis engine for PMMs, Product Managers, and UX Researchers. Transforms raw transcripts into structured discovery outputs anchored in JTBD theory, with signal-level pattern detection and confidence scoring. Trigger on: "summarize interview", "process transcript", "interview summary", "what did customers say", "synthesize discovery", "interview debrief", "JTBD analysis", "customer insight", "research synthesis", or any request to process, structure, or extract meaning from a customer or prospect interview.

stefanoskarakasis Bundle

Orchestrates multi-skill PMM programs end-to-end — chains positioning, competitive, GTM strategy, campaign briefs, stakeholder maps, and retros into one coherent program with a master document and brain updates. Trigger on: "run full GTM workflow", "run a full launch", "launch [product] end to end", "positioning refresh", "quarterly PMM cycle", "competitive program", "new market entry program", "full PMM onboarding", or any request for a multi-step PMM initiative that spans more than one skill.

techwolf-ai Bundle

Analyze, re-engineer, or bootstrap projects to align with AI-first design principles. Use when asked to review, audit, improve, 'ai-firstify', or start a new project. Performs deep analysis across 7 dimensions, actively restructures existing projects, or guides new project setup through discovery questions. Based on the 9 design principles and 7 design patterns from the TechWolf AI-First Bootcamp.

techwolf-ai Bundle

Set up a new content studio for a person. Copies the plugin template, adapts it to the person's voice, themes, and content types through interactive discovery. Use when asked to create a content studio for someone new.

timzaak Skill

Interactive guide that teaches how to use the t-tools plugin. Explains the Decision -> PRD/Tech Research -> Design -> Task -> Run -> Demo -> Release workflow, maps the user's goal or question to the right /t-tools:t-* entry command, and shows preconditions and next steps. Use when the user types "/t-tools:t-how" or asks how this plugin works, which command fits a goal, or how stages connect. Teaching only; never executes stages or writes target-project files.

timzaak Bundle

Create or update draft PRD and user stories for a feature.

timzaak Skill

Organize and realign PRDs, user stories, design/task docs, implementation facts, and project structure so the target project keeps a clean current context instead of accumulating stale or misleading information. Use when asked to audit documentation drift, structure drift, traceability gaps, whether PRD/code/test/demo directory organization and module boundaries are reasonable, or to merge/prune/rewrite PRDs into concise current authority sources.

timzaak Bundle

Decide whether a feature should enter the t-tools workflow before tech research or PRD.