Product & Planning

suibianqugenichenghaole Skill

Judge whether the current requirement/demo/PRD work is stable enough to freeze as a review or delivery baseline, and identify what blocks freezing when it is not ready. Use when a product workflow round may be turned into a versioned snapshot, when Codex needs to decide whether to keep iterating or preserve the current baseline, or when downstream embedded-PRD/project-ops work depends on a trustworthy freeze decision.

suibianqugenichenghaole Skill

Extract structured page, annotation, and visual evidence from an exported prototype package before requirements are finalized. Use when the source is prototype-export data rather than a clean PRD; do not use for ordinary screenshot absorption or requirement writing.

suibianqugenichenghaole Skill

触发：文档/PPT/PRD需先定读者判断；不触发：需求价值→用pm-value-anchor；需求澄清→用pm-requirement-intake；输出：读者判断+证据

suibianqugenichenghaole Bundle

触发：ready demo handoff需做可运行React原型；不触发：需求/规则不稳→用pm-requirement-intake；嵌入式组装→用pm-embedded-prd；输出：React原型基线

tamdogood Bundle

Create or update a complete repository skill from a user's idea, including the workflow instructions, references, scripts or assets, agent metadata, skill-card artwork, cinematic banner artwork, README links, discovery metadata, and validation. Use when the user asks to create a new skill, add a skill to this collection, turn a workflow into a reusable skill, or make a skill's documentation and artwork consistent with the repository.

tamdogood Bundle

Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current paradigms, a complete roadmap or curriculum, deliberate practice and feedback, or a top-1%-level mastery plan. Answer explanation questions completely before offering a curriculum; route explicit mastery goals to an adaptive practice and proof-of-capability system.

the-open-agent Bundle

Build and run a system for handling incoming issues. Use when an issue backlog has become unmanageable, when setting up issue templates or a label taxonomy, when deciding what to close, when configuring stale bots or automation, or when the user asks "how do I deal with all these issues". Covers issue forms, a minimal label set, triage rotation, converting issues to discussions, writing closing messages that don't burn people, duplicate handling, and turning recurring issues into documentation or code changes.

tronghieu Bundle

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

tronghieu Bundle

Act as a project-management copilot (PM/PMO) for the delivery loop: charters, plans and schedules, estimates, risk registers, status reports, scope changes, stakeholder communication, meeting actions, lessons learned, and portfolio roll-ups, in a per-project `_project/` workspace. Use whenever the user wants to start, plan, track, rescue, or report on a project: "kick off this project", "make a project plan / timeline / WBS", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report", "the deadline slipped, what now", "turn this meeting into action items", "review my project portfolio", in any language ("quản lý dự án", "gestion de projet", "プロジェクト管理", "项目管理"), even when they never say "project management". Also use whenever a `_project/` directory exists and the user asks about schedule, deadline, risk, status, scope, budget, or stakeholders. Not for what to build (product-manager) or company-level bets (strategy-board).

validkeys Bundle

Generates a concise developer summary from planning artifacts. Auto-discovers business requirements, technical requirements, milestones, and timeline from the docs/ folder structure. Outputs a focused summary with project overview, deliverables, and milestone roadmap.

vraj-ai Bundle

Drive a published spec to verified, pushed completion through a resumable backlog, worktree-isolated parallel builds under a lazy-senior-dev ladder, gate-first review, a milestone reviewer, and a final adversarial teardown. Use when the user invokes /ship, asks to build out a spec autonomously, or resumes a ship run.

vraj-ai Bundle

Drive a plan document to verified completion through a resumable single-writer backlog, named Worker Role research and review, worktree-isolated parallel builds, milestone gates, and a final adversarial teardown. Use when the user invokes /goal, asks to execute an architecture plan autonomously, resumes a goal, or needs a large issue set delivered milestone by milestone.

vraj-ai Skill

Audit a whole codebase rather than a single diff — establish the boundary and baseline, sweep layer by layer (entry points, domain, data, integrations, auth, tests, ops), check every stated invariant for a real enforcement point, a failing-on-violation test, and a production signal, rank findings by blast radius, and emit each as a ticket with a Verification-command. Use when asked to audit an app or codebase, assess a project's health, review before a launch, verify that a security/performance/privacy claim is actually enforced, or produce a prioritized defect backlog.

vraj-ai Skill

Run independent multi-model research, evidence-based debate, voting, and scoped T0/T1 reviews without rubber-stamping. Use when goals encounters a genuinely contested research item, Phase B needs backlog sanity checks, an item needs independent T0 reviewers, or a milestone needs one rotating integration reviewer.

wei63w Skill

Diagnose .pm/ health (missing files, broken audit, stale map, unconfirmed PRD) and repair or increment without overwriting confirmed content.

fabioc-aloha Bundle

Internal metacognitive skill for automatic capability discovery — self-triggers when uncertain about available skills

go-sphere Skill

Generate high-quality Product Requirements Documents (PRDs) following go-sphere development workflow. Use when: user wants to create a PRD, document requirements, plan a feature, or translate business ideas into product specs. Required for the PRD solidification phase in AI Agent collaboration development.

go-sphere Bundle

Write or revise implementation-ready specifications for products, systems, APIs, workflows, runtime services, and technical designs. Use when asked to create a new spec from requirements, rewrite an ambiguous PRD or design doc into an executable SPEC.md, deepen an existing specification that feels too thin or hand-wavy, update a spec after scope changes, or modify a specification without leaving contradictions. Trigger on requests such as write spec, rewrite PRD as spec, improve this SPEC.md, make the spec more complete, modify spec, 修改规范, 写技术规格, 改 SPEC, 补技术细节, or 整理实现方案.

go-sphere Skill

Organize scattered project inputs and generate standardized intake documents. Use when users mention project kickoff, requirement initialization, PRD preparation, input organization, requirement gathering, or turning prototypes/demos/drafts into structured documents. Apply to new feature development, project initialization, requirement clarification, and similar scenarios. Always complete intake before writing PRD or any detailed design.

guhcostan Skill

Use when creating or updating a product roadmap, defining OKRs, or communicating product direction to stakeholders.

guhcostan Skill

Use when you have an approved discovery document and need to write a Product Requirements Document before implementation begins.

guhcostan Skill

Use before any product work — new features, product ideas, or behavior changes. Use before writing PRDs or user stories.

guhcostan Skill

Use when you have an approved PRD and need to break it into actionable user stories for development.

guhcostan Skill

Use when setting up or improving a continuous product discovery practice with weekly customer interviews.

guhcostan Skill

Use when you need to update stakeholders, write executive summaries, manage cross-functional relationships, or resolve conflicts with engineering and design.

hardiktiwari 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.

hardiktiwari 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.

hardiktiwari 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.

hardiktiwari Skill

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

kotlin Bundle

General-purpose YouTrack operations for the kotlinx-rpc project (KRPC). Use this skill whenever the user wants to search, read, update, comment on, link, tag, or otherwise interact with existing YouTrack issues — anything that isn't creating a brand new issue. Also use it when the user asks about issue status, sprint progress, who's working on what, backlog queries, or wants to browse/filter issues. Trigger this even if the user doesn't say "YouTrack" explicitly — if they mention a KRPC-### issue ID, ask about tickets, want to check on an issue, update a status, or log work, this is the right skill. Do NOT use this skill for creating new issues — use file-youtrack-issue instead.

kotlin Skill

Audits and manages Gradle dependency graphs with high-resolution update checks, transitive tree analysis, and Maven Central discovery; use for dependency auditing, finding stable updates, and resolving GAV coordinates. Do NOT use for exploring dependency source code (use `searching_dependency_sources`) or running builds.

kotlin Skill

Explores and searches source code of all external library dependencies, plugins, and Gradle internals via indexed symbol, full-text, and glob search; STRONGLY PREFERRED for understanding APIs, finding class/method definitions, and reading implementation logic. Do NOT use for project source code (use grep), Gradle documentation (use `researching_gradle_internals`), or Maven Central discovery (use `managing_gradle_dependencies`).

mattjmdesign Bundle

Turn a brief or existing feature into testable behavior, quality constraints, and explicit data and permission contracts. Use when stakeholder notes, a brief, or a vibe-coded concept needs FR/NFR requirements before design or implementation.

pale-knight Bundle

Credential operations: secret discovery, classification, extraction, conversion, offline cracking of hashes the operator already has as a credential job, policy-aware spraying, NetNTLM capture, generic SMB relay, and Windows/Linux harvest. Do not hijack an in-progress /ad-attack Kerberoast/AS-REP chain (that module cracks and uses the ticket itself). Do not DCSync, read LAPS LDAP, or escalate cloud IAM. Usable credentials are recorded; the operator chooses the next module.

pale-knight Bundle

HTTP/HTTPS application-layer reconnaissance after a web service is identified: fingerprinting, content/API discovery, JS/source maps, proxy/cache topology, WAF, CMS, and known CVE/PoC candidates. Recon only — do not exploit, write files, or obtain a shell. Hand CVE candidates and attack surface to the operator, who may select /web-attack. Non-HTTP ports belong to /recon.

pranav8494 Skill

Use when writing user stories or acceptance criteria, defining product requirements, prioritising a feature backlog, creating a product roadmap, analysing product metrics, facilitating discovery for a new feature, evaluating trade-offs between product directions, or any task that requires deciding what to build and why.