Slash commands are frequently-used prompts defined as Markdown files that Claude executes during interactive sessions. Understanding command structure, frontmatter options, and dynamic features enable

>

context-status

Final submission gate combining full verification, score enforcement, and submission checklist.

Plan reproducible ML experiment runs with parameters and metrics tracking

Systematic prompt engineering methods for AI-assisted academic research workf...

Measure what matters with proper event tracking, funnels, cohorts, and metrics. Use when setting up analytics, tracking features, or understanding behavior.

1. [Purpose](#purpose)

This skill provides an AI-driven workflow for enhancing SRT subtitle files by comparing them with an original reference document (`origin.md`). The enhancement process corrects typos, standardizes pro

Status: Backlog

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.

Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end). Auto-populates topic skeleton from a sibling meeting-agenda when available and reconciles planned vs. actual topics. Accepts transcripts from Zoom, Meet, Otter, Fireflies, Krisp MCP, or manual notes; runs on variable-quality input without blocking.

Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.

Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.

>

>

Watch subreddits for people describing the problem you solve. Score their relevance. Draft a helpful reply for each match.

Take a competitor's public GitHub repo. Fetch their open issues. Filter noise locally. Cluster into 6 demand categories. Score by real engagement. Output a ranked demand gap report and GTM messaging b

>

Use when someone asks 'RRF or DBSF?', 'how to combine sparse and dense', 'how to combine scores from multiple searches?', 'custom fusion', or 'fusion is not producing good results'

Use when writing Go code that returns, wraps, or handles errors — choosing between sentinel errors, custom types, and fmt.Errorf (%w vs %v), structuring error flow, or deciding whether to log or return. Also use when propagating errors across package boundaries or using errors.Is/As, even if the user doesn't ask about error strategy. Does not cover panic/recover patterns (see go-defensive).

Use when deciding whether to use Go generics, writing generic functions or types, choosing constraints, or picking between type aliases and type definitions. Also use when a user is writing a utility function that could work with multiple types, even if they don't mention generics explicitly. Does not cover interface design without generics (see go-interfaces).

Interactive conversational setup wizard for instar. Walks users through initial configuration and identity bootstrapping conversationally.

Spawn, monitor, and communicate with persistent Claude Code sessions running in the background. Use when a task needs to run without blocking the current session, when the user asks to do something in the background, or when a long-running task needs its own context window. Trigger words: background task, spawn session, persistent, run in background, parallel, separate session, async task.

Automatically triggered when Tapestry is first launched on a new environment or lacks dependencies. Intelligently detects environment and installs Tapestry dependencies with user confirmation.

Find the most relevant external agent skills for the current task, then submit grounded feedback about which skills were actually used and useful in the same session. Whenever you start a task, use this skill first.

Create atomic commits by staging the right files, analyzing the staged diff, composing a conventional commit message, and optionally pushing.

This skill should be run only when the user explicitly invokes it. Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass.

**Company:** Series B Healthcare SaaS (80 people)

**Company context:** Series B healthcare SaaS, ~80 employees

**Organization:** B2B Analytics SaaS

**Prepared for:** Mid-level PM (3 years experience) at a 500-person enterprise SaaS company

**Title:** Q1 All-Hands: What We Shipped, What's Next, and Where We Need Help

**Prepared for:** Director of Product, 200-person fintech startup

- **Date type:** Fixed external deadline

Design employee onboarding (first 90 days + trajectory). See also: user-onboarding (product UX onboarding).

**Role:** Product Lead (IC/people-manager hybrid typical of product leadership)

Prioritize product roadmap: scoring model, ranked opportunities, decision narrative. See also: technical-roadmaps (engineering roadmap).

- **Product:** Team collaboration SaaS

**Decision statement (one sentence):**

**Prepared for:** New Product Lead, 5 direct reports (3 PMs, 1 Designer, 1 Data Analyst)

**Team:** Product Team (10 people, remote-first)

Since the user did not provide answers to intake questions, the following explicit assumptions are made. Open questions that could change the ship decision are listed in Section 8.

**Feature:** Role-Based Access Control (RBAC) for Admin Users

Align stakeholders and secure buy-in: stakeholder map, pre-brief plan, decision summary.

**Founders:** 2 co-founders (ex-ops managers in logistics + PM from warehouse software)

**Company:** AI Support Copilot (E-commerce)

**Date:** March 2026

**Remote Cross-Functional Team: Reduce Chaos, Increase Decision Velocity**