Product & Planning

anthropics Skill

Turning a described need (several constraints, a gift, a choice between candidates already in view, a search that came back empty or sold out) into a shortlist and a pick. Not needed when one search for the thing the customer named answers the request, or when the customer wants to learn what matters in a category first (purchase-research).

antjanus Bundle

DEPRECATED 2026-09-01 — QA.md manual-QA checklists were retired portfolio-wide on 2026-08-24 and this skill will be deleted in the next release. Do NOT use this skill for anything, including "create a QA list", "set up QA", "what should I QA", "track manual QA", "audit the QA list", or "what's left to check before release". Hands-on verification (playthroughs, parity gates, release sign-offs) is filed as ordinary ROADMAP.md items instead — use track-roadmap for that, and track-session for cross-session progress.

antjanus Bundle

Use this skill to maintain ROADMAP.md whenever the user wants to "add an item to the roadmap", "mark a feature done", "log the work I shipped", "create a roadmap", "what should we build next", "brainstorm features", "audit the roadmap", or file hands-on checks like "add the release sign-off to the plan" — even if they don't mention the roadmap file by name. Covers the generate, update, audit, brainstorm, and resume modes. Do NOT use this skill for session-level task progress (see track-session) or free-form idea backlogs that aren't landing in a roadmap file.

antjanus Bundle

Use this skill to maintain SESSION_PROGRESS.md and track multi-session work — resuming, checkpointing, and handing off long tasks. Triggers include "resume work", "pick up where I left off", "what was I doing", "save progress", "checkpoint before I lose context", "are we done", or "I lost my SESSION_PROGRESS" — even if the user never says "session", as when they return to a multi-day refactor or ask you to write down where things stand. Applies to multi-phase work, cross-file refactors, and long debugging runs; skip it for quick one-file fixes. Do NOT use this skill for feature or milestone planning (see track-roadmap) or for a one-off summary or handoff doc that doesn't live in SESSION_PROGRESS.md (see work-summary).

antjanus Bundle

Interactive SKILL.md builder. Use this skill whenever the user asks to "create a skill", "generate a skill", "scaffold a SKILL.md", "write a SKILL.md", or "turn this workflow into a skill" — even if they don't say "skill" and only describe wanting to make a repeatable agent workflow, checklist, or convention. Do NOT use for grading an existing SKILL.md (see rate-skill) or project roadmaps (see track-roadmap).

zai-org Skill

Documentation-only master skill for GLM ecosystem discovery and installation. This skill does not execute scripts or subprocess commands. It provides a curated list of official GLM skills, install methods, and source links.

zhachory1 Skill

Roadmap creation workflow for agents. Use for roadmap, OKR planning, project evaluation, ROI scoring, dependency mapping, capacity allocation, now/next/later, theme grouping, council review, leadership approval. Produces prioritized roadmap with value/cost/risk tradeoffs, dependencies, resource plan, approval package, telemetry, memory and code RAG context, bounded allocation/dependency loops.

zhachory1 Skill

End-to-end software development workflow for AI agents. Use for plan-to-launch, dev workflow, PRD, DD, design doc, council on docs, implementation plan, ship, code-reviewer, council on review and code, launch PR, merge readiness. Enforces thought-out plan before implementation, bounded PRD/DD council loop, ship/review loop, design kickback, human approval, agent-fleet awareness, telemetry, long-term memory, and code RAG.

zhachory1 Skill

Universal context-gathering skill for AI agent workflows. Use for grounding brief, gather context, step zero, linked docs, tickets, code search, logs, traces, metrics, prior runs, memory MCP, gbrain, code RAG, repo-index, agent-fleet journal, PR context, investigation evidence, roadmap inputs, ML experiment setup. Produces a standard brief with sources, assumptions, open questions, risks, and confidence.

zhachory1 Skill

Project ideation workflow for OKR planning and feature discovery. Use for project ideation, feature ideas, goal deconstruction, gap analysis, customer/data-backed unmet needs, cross-functional jam, multi-persona council, project framing, success metric, technical feasibility, engineering lift. Produces framed candidates ready for roadmap evaluation with telemetry, memory, code RAG, and bounded diverge/converge loops.

zhachory1 Skill

Package workflow outputs for the next agent or human. Use for launch PR package, ML artifacts handoff, debug RCA handoff, roadmap approval packet, project ideation handoff, backprop changelog, implementation handoff. Produces summary, evidence, decisions, files, artifacts, metrics, known limitations, next steps, and telemetry.

zhachory1 Skill

Prepare decision package for qualified human signoff. Use for PR launch, merge/no-merge, roadmap approval, ML deploy handoff, metric changes, council blockers, destructive actions, production risk, budget cap escalation. Produces concise yes/no ask, recommendation, evidence, risks, alternatives, rollback, and telemetry; never auto-approves accountable decisions.

zhachory1 Bundle

Author and revise structured workflow docs for agents: PRD, DD, design doc, implementation plan, RCA, ADR, experiment plan, roadmap proposal, handoff doc. Use for doc writing, doc quality gate, templates, acceptance criteria, risks, tradeoffs, decision records, prevention actions, Mermaid diagrams, Graphviz/DOT diagrams, visual explanations. Produces concise docs with fixed sections, visuals, source links, open questions, and telemetry.

zhachory1 Skill

Define success criteria and metrics before work starts. Use for PRD outcomes, ML offline/online metrics, experiment yardsticks, roadmap ROI, ideation framing, debug done criteria, backprop workflow optimization, launch gates, acceptance criteria. Produces measurable targets, guardrails, measurement plan, anti-metric-shopping lock, baselines, decision thresholds, and telemetry.

zhachory1 Skill

Turn approved goals, PRDs, DDs, ML experiment plans, roadmaps, or investigations into ordered dependency-aware tasks. Use for implementation plan writing, experiment plan, roadmap sequencing, acceptance criteria, blockers, atomic PRs, verifiable tasks, handoff to ship agents. Produces tasks with owners, dependencies, validation, acceptance criteria, risk, and telemetry.

jtenniswood Bundle

Research-only technical debt scan for this EspControl repository. Use when the user asks for a tech debt scan, cleanup backlog, maintainability review, messy or rushed implementation review, duplicated logic audit, fragile assumption scan, dead code review, architecture cleanup plan, or asks to identify code that works now but will be painful to maintain later.

maciejzet Bundle

Run the operational customer-to-resolution loop across support conversations, customer cases, incidents, account risk, commitments, internal handoffs, feedback clusters, and GitHub engineering work. Use when asked to triage an inbox or ticket queue, investigate a customer problem, detect or coordinate an incident, build an operational account 360, watch churn/non-renewal signals, find overdue promises or stalled escalations, dedupe customer-reported bugs into GitHub, produce customer-ops briefs, or verify that a fix actually resolved the customer-visible symptom. Composes with Gmail/support tools, HubSpot/CRM, billing, product analytics, GitHub, Notion/incident records, and connected files. Do not use for broad VOC/persona research, retention-program design, general CRM architecture, analytics implementation, product roadmap prioritization, or security exploitation; hand those workflows to the specialist skill.

maciejzet Bundle

Analyze an entire software/product project and turn verified project truth into an evidence-based, dependency-aware, reusable roadmap. Use for first-time or delta whole-project baselines such as "analyze the whole repo/project", "what is left to build before target state", "create/update a roadmap from GitHub/Notion", "przeanalizuj całe repo", or "update the roadmap after recent changes". Inventory topology before searching, separate intent/presence/behavior/release/outcome truth, prove material absence instead of inferring it from search misses, expose coverage and contradictions, model capabilities/critical journeys, prioritize target blockers and gates, validate hard dependencies, and create immutable baseline/delta roadmap snapshots. Do not use for weekly sprint control, release-candidate GO/NO_GO gates, or "is build v1.2.3 ready to ship?" — use Product Operator or Release Readiness instead. Do not use as an implementation agent, narrow code review, or specialist security/SEO/CRO audit.

maciejzet Bundle

Evidence-governed product operating system that reconciles GitHub implementation and release state, Notion roadmap/tasks/decision docs, product context, and available outcome signals to answer what the team should do next on an existing roadmap or product state. Use for weekly control-loop questions such as what to build/fix/verify next, how to unstick work, what is actually done vs planned, whether roadmap and repo agree, what changed since the last review, or what should wait/stop. Produces bounded BLOCKER/VERIFY NOW/NOW/NEXT/LATER/STOP actions, dependency-aware sequencing, state drift, readiness, immutable snapshots/deltas, confidence, done conditions, and specialist handoffs. Do not use for first-time whole-repo baseline analysis or roadmap creation from scratch — use Repo to Roadmap. Do not use for release-candidate GO/NO_GO gates on a specific build/artifact — use Release Readiness. Read-only by default; delegate deep audits and consequential decisions instead of duplicating specialist skills.

maciejzet Bundle

Analyze external products, websites, apps, APIs, documentation, and source repositories to extract evidence-backed, transferable, implementable product and engineering patterns rather than generic competitor summaries. Use when the user asks to teardown, reverse-engineer at a product/architecture level, benchmark, study, or learn from another product/repo; asks what workflows, UX mechanics, architecture, onboarding, monetization, developer experience, operations, reliability, or implementation ideas are worth adapting; asks "what can we borrow/learn/implement from X" or Polish equivalents such as "przeanalizuj produkt/repo", "wyciagnij wzorce", or "co warto wdrozyc". Also use for multi-product pattern synthesis and source-to-target adaptation. Do not use as the primary skill for ongoing competitor monitoring/delta analysis, broad competitor dossiers, external-facing comparison pages, or a roadmap of the user's own repo with no external/reference target.

maciejzet Bundle

Assess whether a specific release candidate, build, artifact, application, service, mobile/desktop build, or API is ready for production in a named environment and issue an evidence-backed GO / GO_WITH_CONTROLS / NO_GO / DEFER verdict across product acceptance, QA, security, operations/reliability, documentation, billing/entitlements, and support/incident readiness. Use when the user names or implies a concrete candidate (version, build ID, branch/tag, artifact digest, deploy target) for launch/release gates, pre-deploy audits, "is this build ready to ship?", hotfix readiness, post-incident releases, and repeated delta/revalidation reviews. Do not use for first-time whole-project roadmap baselines or "analyze the entire repo" — use Repo to Roadmap. Do not use for ongoing weekly prioritization on an existing roadmap — use Product Operator. Orchestrate specialist evidence without pretending to replace security scans, live-app QA, legal/privacy review, or deployment authorization.

maciejzet Bundle

Find, verify, qualify, compare, and manage companies as design partners, co-development partners, beta partners, paid pilots, lighthouse customers, or early adopters. Use for design-partner discovery, early-adopter shortlists, qualification of an existing candidate list, cohort selection, partner-readiness validation, active-partner review, or revalidation of prior candidates. Go deeper than generic prospecting by optimizing for learning value, urgency, representativeness, implementation feasibility, real user/champion access, mutual commitment, evidence quality, transferability, cohort coverage, and cost-to-learn. Separate desk-research fit from live readiness, preserve evidence lineage/freshness, and prevent prestige or contract size from replacing product-learning quality. Hand off broad lead generation to prospecting, research synthesis to customer-research, and outreach copy to cold-email.

meisterlabs Skill

Create an OKR (Objectives and Key Results) map for a goal or initiative.

meisterlabs Skill

Create a structured project proposal Note from a brief, ready for stakeholder review and handoff to note-to-project.

noorkhalel Bundle

Build an evidence-based mental model of an unfamiliar existing repository: structure, ownership, flows, entry points, and change locations. Use for onboarding, tracing, and discovery before another task. Do not use to prescribe a design, issue findings, implement changes, or diagnose a specific failure.

perdolique Bundle

Analyze repositories for available dependency, tooling, runtime, and infrastructure updates, aggregate changelogs across every version from the current version through each target, and report every direct candidate in structured Markdown with major-release highlights and repository-specific impact. Use for update discovery, dependency update analysis, release-impact and breaking-change review, or requests to update repository dependencies, tooling, runtimes, or infrastructure versions.

perdolique Bundle

Use when non-trivial coding work needs discovery or phased execution. Trigger for risky multi-file features, cross-cutting fixes, refactors, migrations, recovery, iteration plans, and PR-sized task splits. Skip simple edits and publication-only or review-only requests. Domain conventions belong to a more specific skill.

roberdan Bundle

Roberto 'Roberdan' D'Angelo's digital twin — thinks, decides and writes in his voice and values so he can delegate real work. Use it whenever he asks to draft as him, reply as Roberdan, write in his voice or style, decide what he would decide, channel him, or think like him; for a customer or partner follow-up, a Teams reply, a status to leadership, an intro; for inbox, calendar or backlog triage and meeting prep; and for any multi-step piece of work, analysis, document or deck where his method and standards apply.

roberdan Bundle

Helps figure out WHICH problems are worth solving, not just how to solve them. Orchestrates: problem discovery/validation with users (focus-group) → prioritization (severity×frequency×reachability×fit) → solution stress-test (premortem). TRIGGER: 'is it worth solving X', 'vale la pena risolvere X', 'is this a real problem', 'è un problema vero', 'which problem should I attack', 'quale problema attacco', 'should I build this', 'dovrei costruire questo', 'validate before building', 'validiamo prima di costruire', 'prioritize these problems', 'prioritizza questi problemi', 'is this worth building'. YES upstream of any non-trivial build/investment.

sayemnyc Bundle

Draft a client proposal that closes. Structures the proposal around the client's actual problem, not the seller's services. Includes scope, timeline, and price with confident framing. Used when a freelancer, consultant, or small agency owner needs to send a proposal after a discovery call.

delorenj Bundle

Skill-set hub for the ProductManager agent and its discovery workflows. Routes ProductManager, PM discovery, feature candidate research, mock use, visual inspection, external research, BrainstormPhase, FeatureDocPhase, and ReportPhase tasks to product-manager-agent plus product-manager-research-phase, product-manager-brainstorm-phase, product-manager-feature-doc-phase, and product-manager-report-phase. Use when composing the complete feature-candidate discovery workflow. Do NOT use for implementation-only work.

abhillashjadhav Skill

Define falsifiable assumptions, explicit kill thresholds, an evidence plan, and a decision date before an AI feature is built. Use when a team is excited by a demo, proposing an AI feature, debating whether to prototype, or continuing investment without clear stopping conditions. Do not use for post-launch evaluation or ordinary roadmap prioritization.

ivanestar Skill

Acts as a strategic architect-advisor for EITR's own product direction (not a generated project's) - reviews current architecture against fresh industry research, hunts for non-obvious synergies between backlog ideas, designs the SDET onboarding flow across greenfield/brownfield x docs/no-docs x tests/no-tests, and records business-language questions only the user can answer. Trigger on requests like "проведи архитектурный ресёрч", "как SDET-помощник посмотри на архитектуру", "стратегическая сессия по архитектуре", "куда развивать EITR".

myriad-dreamin Bundle

Use when creating, updating, generating, validating, or reviewing Meow dataset packages and dataset output paths. Covers git config dataset path discovery, tmp log locations, pnpm package layout under project/dataset by dataset name, TypeScript generation and validation scripts, and dataset maintenance commands.

myriad-dreamin Skill

Update repository roadmap docs with alias-aware roadmap/topic lookup and preserve archived spec links.

othmanadi Skill

Find niches, topics, audiences, products, channels, and content angles via deep web search. Use whenever Ahmad says "find me a niche", "hunt niches in X", "what's an underserved audience for Y", "find similar sites/videos to <example>", "research the X market", "what are people building in Y space", "/niche-hunter X", or any phrasing that asks for niche / market / topic / audience / product / channel discovery across the open web. Trusts domain + keyword search; chains web_search → web_fetch / web_extract / web_crawl + reddit_search + search_youtube + github_repo_intel. NEVER uses awesome-list shortcuts. Output shape is FLEXIBLE — list, table, report, suggestions, or normal prose — picked from how Ahmad phrased the ask.