📋 Product Management

sickn33/git-pr-workflows-onboard

Verified by SkillsAuth

testing

You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You

sickn33/comprehensive-review-full-review

Verified by SkillsAuth

tools

Use when working with comprehensive review full review

davila7/requirements-clarity

Verified by SkillsAuth

testing

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

davila7/cto-advisor

Verified by SkillsAuth

tools

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

nearai/developer-setup

Verified by SkillsAuth

development

One-time onboarding for the developer workflow — installs github-workflow missions, creates the commitments workspace, registers per-repo projects, writes calibration memories. After successful setup this skill is excluded from selection until the marker file is deleted.

nearai/developer-assistant

Verified by SkillsAuth

tools

Commitment tracking and workflow automation for software developers — multi-repo GitHub awareness, CI/PR signal extraction, tech debt tracking, coding agent delegation, morning dev brief and weekly retro.

modelcontextprotocol/search-mcp-github

Verified by SkillsAuth

tools

Search MCP PRs, issues, and discussions across the modelcontextprotocol GitHub org

openclaw/skill-routing-benchmark

Verified by SkillsAuth

tools

测试多个 Skill 描述是否会路由冲突，并生成正例、反例与负向触发语句。；use for skills, routing, benchmark workflows；do not use for 只给模糊建议, 忽略高度相近的 skill.

openclaw/1kalin/afrexai-stakeholder-management

Verified by SkillsAuth

data-ai

# Stakeholder Management Mastery You are a stakeholder management strategist. You help identify, analyze, engage, and manage stakeholders across any project, initiative, or organizational change to maximize alignment, minimize resistance, and drive successful outcomes. --- ## Phase 1: Stakeholder Identification ### Discovery Questions Before mapping stakeholders, gather context: 1. What is the initiative/project? (scope, timeline, budget) 2. Who approved/sponsors it? 3. Who is directly affec

compozy/cy-idea-factory

Verified by SkillsAuth

development

Expands a raw idea into a structured, research-backed spec in .compozy/tasks/<slug>/_idea.md through interactive brainstorming, web research, business analysis, and multi-advisor debate. Use when the user has a feature idea and wants to explore and structure it before creating a PRD. Do not use for PRD creation, technical specifications, task breakdown, or code implementation.

compozy/cy-create-techspec

Verified by SkillsAuth

development

Creates a Technical Specification plus its companion test contract (_tests.md) by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, when technical architecture decisions need documentation, or when a feature needs its exhaustive test-case catalog. Do not use for PRD creation, task breakdown, or direct code implementation.

tech-leads-club/technical-design-doc-creator

Verified by SkillsAuth

development

Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).

rmyndharis/git-pr-workflows-onboard

Verified by SkillsAuth

testing

You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You

rmyndharis/comprehensive-review-full-review

Verified by SkillsAuth

tools

Use when working with comprehensive review full review

rshankras/app-planner

Verified by SkillsAuth

testing

Guides you through comprehensive iOS/Swift app planning and analysis. Use for new apps (concept to architecture) or existing apps (audit current state, plan improvements, evaluate tech stack). Covers product planning, technical decisions, UI/UX design, and distribution strategy.

a5c-ai/plantuml-renderer

Verified by SkillsAuth

development

Render PlantUML diagrams to various image formats with theme and styling support

a5c-ai/plugin-registry-manager

Verified by SkillsAuth

tools

Manage SDK plugin discovery and registration

aj-geddes/bmad-tech-spec

Verified by SkillsAuth

testing

Quick Flow lightweight technical specification for small-scope work (1-15 stories). Replaces the full PRD + architecture pair when scope is small and requirements are clear. Produces bmad-output/tech-spec.md as the single planning artifact before story creation. Use when the user says: "write a tech spec", "create a technical specification", "I need a tech spec for this feature", "quick spec", "small project spec", "we don't need a full PRD", "just a tech spec", "spec out this change", "document this feature". QUICK FLOW TRACK ONLY (1-15 stories). If scope grows beyond ~15 stories or involves multiple teams / external integrations at scale, stop and redirect to bmad-prd + bmad-architecture instead — those skills are built for that complexity. Supports three intents: Create (new spec), Update (revise an existing tech-spec.md), Validate (review a draft for completeness against BMAD criteria).

aj-geddes/bmad-architecture

Verified by SkillsAuth

development

Solutioning skill (Winston, the Architect). Produces architecture.md with ADRs and systematic NFR coverage, mapping every FR/NFR from the PRD to a concrete design decision. ONE architecture forces all future parallel dev agents to share the same API style, data model, state management, naming conventions, and security approach — catching alignment here is 10x cheaper than during implementation. Use when the user says "design the architecture", "create architecture", "/architecture", "solutioning", "tech stack", "system design", "ADR", "architecture decision record", "data model", "API design", "NFR coverage", "non-functional requirements", or after a PRD is done and they ask "what's next" / "ready for solutioning". Supports Create (new architecture.md), Update (revise against PRD changes), and Validate (check coverage + ADR completeness). PLANS only — never writes application code, runs tests, lints, or builds.

pedronauck/requirements-clarity

Verified by SkillsAuth

testing

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.