Product & Planning

natebjones-projects Bundle

Continuous learning system that extracts reusable knowledge from work sessions. Triggers: (1) /aiception command, (2) 'save this as a skill' or 'extract a skill from this', (3) 'what did we learn?', (4) after non-obvious debugging or trial-and-error discovery. Creates new skills when valuable reusable knowledge is identified. Integrates with Open Brain to prevent duplicates.

masih-0x3 Bundle

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

soia-team Bundle

把产品想法或需求材料整理成可验收的功能规格，并按需拆成纵向交付切片。触发：起草功能规格、把需求写成 PRD、拆分可验收功能

haaaiawd Bundle

genesis Step 2: turn fuzzy or high-level needs into strict product requirement documents (PRDs); includes craft scaffolding, PRD spec contract, optional sub-agent shard orchestration, and Step completion signals. Use when requirements are vague, scope is too large, or expression stays conceptual.

haaaiawd Skill

Code Reviewer — Implementation-side evidence layer

haaaiawd Skill

Specifies the human-facing E2E / manual verification *Testing Guide* and *E2E Verification* report skeleton (PRD traceability, human walk-through order, verdict columns may only be PASS/PARTIAL_PASS/FAIL); **does not include real-browser orchestration**—order of operations and backfill obligations are fixed by the host **`/forge` §3.7** (per `/forge` wording).

j5ik2o Bundle

Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.

katalon-labs Bundle

Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types, Platform/TestOps IDs, verify uploaded runs, handle failed auto-upload, or summarize execution results after automation completes. Written for the automation tester whose framework has already run and whose report is sitting on disk. If the Playwright run has not happened yet, start at playwright-execute.

katalon-labs Bundle

Set up, verify, and troubleshoot Katalon True Platform/TestOps MCP connectivity for any AI coding agent. Use when you need to install or configure the Katalon MCP server, connect to a Katalon platform account, verify available Katalon MCP tools, diagnose missing authentication or repository access, confirm project/repository discovery, or explain what platform operations are and are not exposed through the MCP. One-time cross-cutting setup, run once by whoever wires the agent to the platform, before any lifecycle skill can work.

katalon-labs Bundle

Report Katalon True Platform/TestOps quality metrics to people outside QA. Use when you need to answer a stakeholder question with testing data, choose the few metrics that actually answer it, trend coverage, execution health, defect risk and stability across several releases, sprints, or iterations rather than inside one, and write the summary a manager presents upward at a steering committee, an exec review, or a quality business review. Produces a headline answer with the named specifics behind it, never a metric dump. The MCP returns current state with no history tool, so trends are built from execution dates plus snapshots this skill stores per period. For the ship or no-ship call on a single release, use release-analyze; for a pre-pipeline suite verdict, use test-review. Written for the test manager who has to present quality upward and the test lead who assembles the numbers.

katalon-labs Bundle

Write, run, and debrief exploratory testing charters against Katalon True Platform/TestOps when there is no script to follow. Use when you need to turn a vague area into a charter (mission, areas, oracles, timebox), run a timeboxed unscripted session, log what you find as session notes, judge which findings are real defects, and promote what was learned into atomic manual cases plus the folder or suite that holds them. This is unscripted discovery and the debrief after it; when a written requirement is already in hand and the job is designing cases from it, use create-test-cases instead. Written for the manual tester who has an hour, a feature, and no cases to run against it.

henkisdabro Bundle

Generate comprehensive Product Requirement Plans (PRPs) for feature implementation with thorough codebase analysis and external research. Use when the user requests a PRP, PRD, or detailed implementation plan for a new feature. Conducts systematic research, identifies patterns, and creates executable validation gates for one-pass implementation success. Do NOT use for client discovery, requirements gathering, or scope definition - those need a separate clarification pass before the PRP step.

wanghaisheng Skill

Discovers and compiles lists of relevant influencers across platforms based on niche, audience demographics, content style, and brand fit. The foundation of any successful influencer marketing program.

sach1ng Skill

Help PMs write feature one-pagers — lighter than a PRD, used for quick alignment. Use when you need to align stakeholders without a full spec.

sach1ng Bundle

Use this skill when user asks to create, write, or draft a PRD (Product Requirements Document). Generates structured PRDs with governance framework, problem statements, business goals, use cases, and functional requirements.

rweisssieker-xp Bundle

Use when the current repository needs discovery and autonomous prioritization of evidence-labelled AI-native USP opportunities.

uzysjung Bundle

Defines and enforces a project's long-term direction (North Star Statement, metric-as-proxy NSM, strategic Pillars with a module↔pillar map, Will/Won't, 4-gate + priority-order decision heuristics), then turns that direction into a ranked, persisted roadmap so the plan survives /compact and new sessions. Use when starting a new project, when scope creep is suspected, when a non-obvious feature request needs prioritization, or when the user asks where the project should go next. Sits one layer above SPEC/PRD — answers 'why and where to', not 'what and how'. Fires on the user's real phrasings: "앞으로 어떤 방향으로 개선·발전시킬지 고민해봐", "NORTH.md / NORTH_STAR 보고 나아갈 방향 + 기능 제안", "북극성 정렬 로드맵", and the English "what direction should we take next", "propose a roadmap from the north star". Do NOT use it to find what is broken right now — detecting bugs, gaps, or quality regressions belongs to the audit/gap skills; this skill consumes their findings and DIRECTS forward planning.

uzysjung Skill

Detects when SPEC.md or PRD.md exceeds 300 lines and proposes feature-based splitting with a master route document. Use when SPEC.md grows too large to be effectively used as a single document.

uzysjung Bundle

Runs work through GitHub Issues so the user and the agent can see the same backlog: normalize an incoming request into an issue before building, group tasks under a parent (epic) issue, order them with milestones and priority labels, read every comment before starting, and promote decisions out of comments into the issue body so they survive. Enforces the body template (배경/문제/근거/레퍼런스/제안/전제/방향성/AC/후속) so issues become reusable agent context, and keeps read-only, draft, remote-write, implement, verify, and status stages distinct. Use whenever a request will outlive the chat turn, whenever work needs an order the user can review, or when the user names issues ("이슈로 등록해줘", "에픽으로 묶어줘", "이슈 정리해줘", "#42 작업해줘", "우선순위 다시 잡자", "backlog this", "break this into sub-issues", "implement issue #N"). Read-only stages make no remote change; never create, edit, label, comment on, close, or re-parent a remote issue, and never touch a project board, without the user asking for that change.

hjdspace Skill

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

idaibin Bundle

Use when a Git or non-Git workspace needs a machine-queryable repository asset scan, impact/relationship query, coverage or drift check, or an optional derived navigation view; not for task-local discovery, source changes, repository-guidance authoring, or change review.

juanca202 Bundle

Investigar y sintetizar hallazgos en un informe estructurado (RS-XXX). Skill genérico con seis flujos según la entrada: investigación libre de un tema; decisiones pendientes de un US-XXX/TK-XXX/WI-XXX antes de planificar; análisis de un issue o bug (reproducción, causa raíz y diagnóstico de pruebas, con entregable WI de tipo bug-fix); auditoría de un caso de prueba TC-XXX; análisis de legado (descubrir features FT-XXX y sus pruebas desde código existente); y discovery de migración entre proyectos. Activar cuando el usuario pida "investiga", "research", "¿es viable?", "¿cómo funciona X?", "¿qué impacto tiene?", "compara opciones", "¿qué falta por decidir?", "hay un bug", "falla en producción", "analiza el bug #1234", "revisa este caso de prueba", "analiza este código legacy", "ingeniería inversa de requisitos", "migración entre proyectos", o mencione "RS-XXX". Si hay un artefacto o un identificador del gestor de proyectos en contexto, usarlo sin preguntar.

sach1ng Skill

Capture decision traces — the reasoning behind key PM decisions. Use after PRD approvals, scope changes, launch/kill calls, prioritization shifts, or any significant product decision.

sach1ng Skill

Help PMs write concise status updates for leadership and stakeholders. Use for weekly updates, milestone reports, or progress summaries.

sach1ng Skill

Help PMs map any work item (feature, experiment, initiative) to strategic goals and OKRs. Use before PRDs, backlog prioritization, or planning.

zjunlp Skill

Comprehensive analysis of public companies using SEC EDGAR 10-K financial data stored in a SQLite database. Use this skill whenever the task involves analyzing a company by CIK (Central Index Key), querying SEC financial data, exploring a financial database with tables like companies, filings, financial_facts, or producing a structured financial analysis report. Covers schema navigation, metric discovery, industry-specific exploration, multi-year trend analysis, income statement structure, capital returns analysis, long-term obligations, and producing an insightful financial summary that connects metrics across dimensions.

armelhbobdad Bundle

Design a skill scope through guided discovery. Use when the user requests to "create a skill brief" or "brief a skill."

armelhbobdad Bundle

Pre-code stack feasibility verification against architecture and PRD documents. Use when the user requests to "verify a tech stack" or "verify stack."

outfitter-dev Skill

Run a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.

pyfagorass Skill

Guides Qdrant search strategy selection. Use when someone asks 'should I use hybrid search?', 'how to rerank?', 'results are not relevant', 'I don't get needed results from my dataset but they're there', 'retrieval quality is not good enough', 'results too similar', 'need diversity', 'MMR', 'relevance feedback', 'recommendation API', 'discovery API', or 'missing keyword matches'

dills122 Skill

Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

dills122 Skill

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.

gdm257 Bundle

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

gdm257 Bundle

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.

hive-intel Bundle

Default entry point for any live crypto question when Hive MCP is connected — prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps. Use it whenever the answer depends on live or on-chain data instead of answering from memory, even if the user never mentions Hive. Routes intent to a canonical Hive task toolset, then schema lookup and bounded endpoint invocation. If a domain-specific hive-* skill clearly matches, prefer it; if routing cannot surface the exact tool or schema, hand off to hive-tool-discovery.

hive-intel Bundle

Use this skill when the exact Hive MCP tool, task toolset, provider, endpoint name, schema, operation type, or argument shape is unknown and hive-query routing was not enough — including "what can Hive do", "which provider covers X", "is Hive healthy", or any failed tool-name guess. Discover first with compact Hive resources and search_tools, then inspect the schema before routing reads to invoke_api_endpoint or explicitly approved Hive writes to invoke_stateful_endpoint.