Product & Planning

rexrainbow Bundle

Use this skill when working with RexBoard setup, the RexBoard BoardPlugin, scene plugin registration, mapping: 'rexBoard', this.rexBoard, this.rexBoard.add.* factories, board-plugin.js, board-components.js, or RexBoard factory discovery. Triggers on: RexBoard setup, rexBoard plugin, BoardPlugin, this.rexBoard, mapping rexBoard, RexBoard factory, this.rexBoard.add, board-components.

romiluz13 Skill

Post-call debrief. Captures notes, maps to qualification framework, flags gaps, drafts follow-up email. Use when: just got off a call, have call notes to process, need to capture discovery output, want to update qualification status, need a follow-up email, or want to update CRM notes. Triggers: debrief, call notes, just got off, post call, call recap, capture notes, what happened, update MEDDPICC, follow up email after call, notes from meeting, call summary, discovery notes, I just spoke with.

romiluz13 Bundle

Builds a complete meeting brief before any discovery, intro, or follow-up call. Never walk in blind. Use when: preparing for a discovery call, intro meeting, follow-up, or AE-led meeting. Includes: exec summary, agenda, qualification gap analysis, key questions, objections, proof points. Triggers: prep, meeting prep, discovery prep, prepare for, call prep, before meeting, discovery call, intro meeting, meeting brief, what should I know, going into a call, prep me.

romiluz13 Skill

Builds a three-act proposal narrative with win themes and executive summary from discovery notes. Use when: deal is qualified (MEDDPICC 20+) and seller needs to write a formal proposal or business case. Triggers: proposal, write proposal, build proposal, proposal narrative, executive summary, business case, win themes, three-act proposal, proposal strategy, proposal draft, write the business case.

rootwarp Skill

Full development planning pipeline. Orchestrates a team of agents (researcher, prd-writer, software-architect, project-planner, issue-estimator) to take a project idea from concept to sprint-ready issues.

royvergara Skill

Use when turning a PRD or requirements document into a first pass information architecture. Triggers on a pasted or linked PRD plus a request for an IA, sitemap, screen list, or structure. Always returns what was excluded and why, not just the IA.

royvergara Skill

Use at first contact with work already in flight — a team adopting the gates when the PRD is written, the roadmap committed, and features already shipped. Triggers on existing material (a PRD, a roadmap, tickets, prior research, shipped features and their analytics) plus a request to bring the work into the system, set up ledgers, or see where things actually stand. Back-fills one ledger per live work item with what genuinely exists and names what is missing, recorded never blocked; refuses to read a document's assertions or a tracker's status as evidence.

royvergara Skill

Use when turning raw research (interview notes, support tickets, sales call logs, analytics, survey responses) into a small set of validated customer pains, before any IA, journey map, or brief. Triggers on a pile of research plus a request to find the real problem or "what's the pain here." Will not promote a pain to validated on stakeholder opinion, a feature request, or a single untriangulated source.

shalintripathi Bundle

Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire, executing sales sequences, or coaching qualification. Also triggers on: outbound, cold outreach, deal strategy, pipeline, battle card, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss.

skills-il Bundle

Walks a person through the Israeli divorce process end to end: the rabbinical-court vs. family-court jurisdiction choice and the joinder doctrine (kricha), the mandatory intake track (bakasha leyishuv sikhsukh and the MAHUT meetings under the 2014 family-disputes law) and the urgent-relief / protective-order carve-out, property balancing (izun mashabim, default 50/50 under the 1973 law, with section 8 deviation), spousal maintenance (mezonot isha) vs. child support (mezonot yeladim) and the Bagatz 919/15 shared-custody reform, custody / parental responsibility, the ketubah, common-law partners (yeduim betzibur), and the get plus get-refusal sanctions. Use when someone in Israel is starting or facing girushin and needs a roadmap, a property-balancing worksheet, or draft divorce-agreement clauses. Do NOT use for pension-split math (use israeli-pension-advisor), and always recommend a family lawyer for the actual filing.

linuxfoundation Bundle

LFX cross-repo topology and ownership router. Use when the task spans more than one LFX repo, asks "which repo owns X", "where does Y live", "what repos does this touch", "what consumes Z", or needs a peer-repo file path from inside a single repo. Loads per-repo configs when invoked from the LFX workspace root with a full task prompt; gives targeted cross-repo guidance when invoked from inside a single repo. Also answers LFX glossary and topology questions, and performs read-only discovery when the user asks whether a contract, API, event, field, workflow, or repo capability exists. Do not fire for single-repo implementation tasks where the active repo's own CLAUDE.md already governs (those belong to the repo's local skills). Do not fire for V2 platform composition, service classes, or cross-service handoffs (use `/lfx-skills:lfx-platform-architecture`), ITX wrapper plumbing (`/lfx-skills:lfx-itx-integration`), or Intercom app/Fin workflows (`/lfx-skills:lfx-intercom`).

marconae Skill

Query specs via the speq CLI — semantic search, feature listing, structure validation. Use before reading any spec file; every speq orchestrator and sub-agent invokes this first for spec discovery, search, or validation.

marcus Bundle

Project switching implementation in sidecar: project discovery, state management, UI flow, modal rendering, filtering, theme preview, and plugin reinitialization. Use when working on the project switcher feature, project management, worktree switching, or the project configuration system.

maro114510 Bundle

コード差分・設計ドキュメントから、リリース前に変更を実際に揺さぶって欠陥を洗い出すための QAランブック(shakedown計画書)を3層構造で生成するスキル。 第1層でクリティカルパス分析(ゴールデンパス・リスク分岐・自動テスト済みと手動必須の切り分け)、 第2層で優先度タグ付きシナリオ全量とユーザー合意ゲート、 第3層で実行者・反証可能な期待結果・証跡欄を持つ実行可能チェックリストを生成する。 PRD や Figma を前提とせず、内部リファクタ・バックエンド専用変更・非同期ジョブ・管理画面にも使える。 「QAシナリオを作って」「QA計画を立てて」「シェイクダウンして」「手動QAの計画を作って」 「リリース前の確認項目を洗い出して」「QAランブックを作って」「クリティカルパスを整理して」 「この変更のQA観点を洗い出して」といった依頼で積極的に使うこと。 単体〜結合レベルのテストケース列挙は tdd-test-cases、PRD(Notion)起点のフラットな チェックリスト生成は対象リポジトリの /self-qa が担当なので、それらの依頼には使わない。

mohitkhandelwal242 Skill

General backlog prioritization — pulls the backlog from Jira, scores each item with RICE or ICE, ranks them, and recommends what to build next. Scores are tied to the business's own metrics from business.json (north star, key metrics, revenue model), assumptions are stated explicitly, and unknowns are confirmed with you rather than invented. Optionally writes scores back to Jira and publishes a summary to Confluence (draft-before-publish). Use when asked to 'prioritize backlog', 'rank the backlog', 'what should I build next', 'rice scoring', 'ice scoring', or '/prioritize'. (Distinct from /audit-offers, which is an offer/discount ROI audit.)

mohitkhandelwal242 Skill

Discovery guide for the AI-PM Operator — answers 'what can you do for me?'. Lists every installed skill grouped by PM job-to-be-done and recommends a tailored starter set based on the user's business.json (business type, platforms, revenue model). Use when the user says '/help', 'help', 'what can you do', 'which skill', 'what skills do I have', 'list skills', 'getting started', 'where do I start', or seems unsure what to run.

mohitkhandelwal242 Skill

Product Requirement Document (PRD) generator. Transforms brief feature ideas into complete, structured specs with user stories, acceptance criteria, metrics, and edge cases. Use when asked to generate a PRD, write a spec, or '/prd-generator'.

tchr-dev Skill

Top-level orchestrator for the autonomous novel pipeline. Drives Phase 1 (foundation), Phase 2 (drafting), Phase 3a (automated revision), and Phase 3b (Opus review loop) by delegating to the seed/gen-world/gen-characters/gen-outline/gen-canon/voice-discovery/draft-chapter/evaluate-*/adversarial-edit/apply-cuts/reader-panel/gen-brief/gen-revision/opus-review skills. State persists in <novel-dir>/state.json. Use when the user asks to run the full pipeline, resume an in-progress run, or run a specific phase end-to-end.

tchr-dev Skill

Discover the voice for a specific novel during the foundation phase. Writes 3-5 trial passages in different registers, evaluates which best serves the world and tone, then fills in voice.md Part 2 with the chosen register, exemplars, and anti-exemplars.

tines Skill

Draft evidence-based status updates from recent work across the user’s connectors. Use for daily or weekly updates, project summaries, stakeholder notes, and progress reports.

tines Skill

Turn an automation idea into a clear workflow brief and practical design. Use when the user is starting a workflow, wants questions that clarify it, or wants workflow ideas based on their connectors.

tsingyuai Bundle

Run an SEO page observation-action-review loop with persistent Memory by coordinating demand research, page creation, adversarial review, image generation, IndexNow submission, and performance review. Use when taking an SEO page from opportunity discovery through publication, measurement, iteration, or continuing a previous SEO loop from Memory.

czarnak Skill

Entry point for TIA Portal engineering automation tasks. Routes to the requested or appropriate MCP, Python, C#, MAC Module Builder, diagnostic, or Add-In implementation. Pure review of already supplied/exported PLC code uses the standalone plc-code-analysis skill.

dkeken Skill

Build visual territories (mood boards) for team alignment before production. Groups references into 2-4 named territories, each with palette, texture, typography feel, and 4-6 generated sample tiles, so a team can agree on a direction. Use when the user says "moodboard", "visual territories", "align the team on a look", "reference board", or needs stakeholder sign-off on aesthetic before generating final assets. Part of the Creative Production set.

dkyazzentwatwa Skill

Roadmap strategy, feature prioritization, PRDs, stakeholder alignment, and release planning

dkyazzentwatwa Skill

Project scoping, milestone tracking, risk management, and stakeholder coordination

tsingyuai Bundle

Collect Baidu Tieba thread and user evidence with MediaCrawler using keyword or bar discovery, exact thread detail, replies, and creator pages. Use for community pain-point, vocabulary, objection, topic, or user research with thread-context preservation.

ttttstc Bundle

使用第一性原则把 PRD、需求描述或现有项目上下文转化为首层架构方案（Architecture First Cut）。当用户要求架构方案、系统设计、技术选型与权衡、系统边界、数据边界、架构演进、架构评审，或要求“像资深架构师一样思考”时使用。适用于绿地系统和现有系统改造；负责目标澄清、决策级项目调研、架构驱动力、关键边界、高价值决策、代价、风险与验证路径。不用于直接编码、详细接口/表结构/类设计、完整实施计划或仅需局部实现的确定性任务。

upex-galaxy Bundle

Orchestrates in-sprint manual QA per issue across Stages 1 (Planning), 2 (Execution) and 3 (Reporting). Use for user-story testing, bug retesting, and sprint-wide QA loops. Creates the PBI folder, drives session-start, runs the triage + veto + risk-score decision tree on bugs, produces the ATP + ATR + TC artifacts in the TMS, executes smoke and trifuerza (UI/API/DB) exploration, and files the final QA comment + bug reports. Triggers on: test this ticket, QA this user story, retest this bug, verify bug fix, run exploratory testing, smoke test a feature, process the sprint, plan the sprint QA backlog, next ticket in sprint, resume sprint testing, continue-from a ticket. Do NOT use for Stage 4 TMS documentation + ROI (test-documentation), Stage 5 automation coding (test-automation), Stage 6 regression suite execution (regression-testing), or onboarding a new repo (project-discovery).

upex-galaxy Bundle

Adapt this boilerplate's KATA test architecture, auth, schemas, variables, fixtures, CI, MCPs, and reporting to a project already reverse-engineered by project-discovery. Use for adapt framework, wire fixtures, connect boilerplate to target stack, or wire auth. Strict gate: analysis and plan first, explicit approval, then writes.

upex-galaxy Bundle

Foundation skill that hosts shared references cited by other workflow skills (briefing template, dispatch patterns, orchestration doctrine, skill composition strategy). Loaded on demand by `shift-left-testing`, `sprint-testing`, `test-documentation`, `test-automation`, `regression-testing`, `project-discovery`, `adapt-framework`, `framework-development`. Do NOT use for: syncing AI-critical docs (use `/sync-ai-memory`), adapting KATA tests (use `/adapt-framework`), or onboarding the target project (use `/project-discovery`).

upex-galaxy Bundle

Generate or refresh the canonical business context maps and master test plan. Use for business-data-map, business-feature-map, business-api-map, master-test-plan, refresh project context, refresh all context, entity map, feature inventory, API business map, or risk-ranked test roadmap. Routes exactly one mode at a time unless refresh-all is explicit. UPDATE mode always shows a diff and waits for approval before overwriting.

upex-galaxy Bundle

Plan, write, and review automated tests following KATA (Komponent Action Test Architecture) on Playwright + TypeScript, or explain existing automated tests in a sealed read-only mode. Use when writing E2E or API/integration tests, creating Page or Api components, designing ATCs, parameterizing test data, registering fixtures, reviewing test code for KATA compliance, or requesting break-down-tests / a plain-English test breakdown. The explain mode reads source and reports assertions without entering Plan-Code-Review or editing tests. Do NOT use for running suites (regression-testing), documenting TCs in Jira/Xray (test-documentation), onboarding a repo (project-discovery), or orchestrating sprint-wide testing (sprint-testing).

upex-galaxy Bundle

Onboard a project through four discovery phases: Constitution, Architecture, Infrastructure, and Specification. Produces PRD, SRS, domain glossary, infrastructure context, and backlog access, then hands business maps and the master test plan to `project-context`. Use for set up this project, onboard this repo, connect to project, discover architecture, or create PRD/SRS. Do NOT use for incremental context refresh (`project-context`), writing tests, TMS documentation, running suites, adapting KATA (`adapt-framework`), or technical OpenAPI sync (`bun run api:sync`).

upex-galaxy Bundle

Walks new users through this repo's QA flow — Playwright + KATA + Allure + Xray stack, Jira QA workflow (Backlog → Shift-Left QA → Estimation → Ready For Dev → Ready For QA → In Test → QA Approved → Ready For Release → Deployed to Production), /shift-left-testing for pre-sprint AC refinement on backlog Stories, /sprint-testing for in-sprint manual QA, /test-documentation for TMS test cases, /test-automation for KATA-compliant E2E/API tests, /regression-testing for CI suite execution, /framework-development for boilerplate evolution, MCPs available (six canonical: Context7, Tavily, Playwright, DBHub, OpenAPI, Postman — Atlassian is opt-in via docs/mcp/), critical env vars, and the ordered 4-phase NEW-PROJECT setup path (foundation → Jira catalogs → /project-discovery + /adapt-framework → git Strategy Setup). ALSO the front desk for anyone who is lost or wants to understand how the repo or any workflow skill works — conceptually AND visually: it explains in plain human language (suspending caveman/compressed re

upex-galaxy Bundle

Orchestrates pre-sprint Shift-Left QA on a batch of backlog Stories. Use when the user wants to refine acceptance criteria, surface ambiguities + gaps, draft an ATP outline, and hand off to PO/Dev BEFORE the Story enters a sprint — so defects are prevented in the requirements, not detected after implementation. Triggers on: shift-left testing, shift-left these stories, groom the backlog, pre-sprint QA, refine these N stories, pre-sprint refinement batch, prepare backlog for sprint planning, run AC refinement on UPEX-100/101/102, run shift-left QA, do early-game testing, pre-sprint test planning. ALSO trigger when the user pastes a comma-separated list of Story IDs sitting in Backlog / Shift-Left QA / Estimation / Ready For Dev and asks any variant of "refine", "groom", "clean these ACs", "shift-left these". Do NOT use for: in-sprint manual QA per ticket (use /sprint-testing — entry status is Ready For QA, this skill's entry status is Backlog/Shift-Left QA), Stage 4 TMS documentation + ROI (test-documentation)