Loading...
Loading...
Found 322 Skills
Guides product management for human data platforms—annotation and labeling products, workforce workflows, task design, quality systems (gold sets, adjudication, inter-annotator agreement), customer ML-team project delivery, contributor experience, and privacy-safe handling of human-generated training data. Use when prioritizing roadmap for labeling/RLHF/eval data platforms, writing PRDs for annotation or QA features, defining success metrics for throughput and quality, scoping enterprise customer workflows, or balancing cost-quality-speed tradeoffs—not for hands-on model training (data-scientist), warehouse/analytics pipelines (data-warehouse-engineer), generic BRD workshops without product lens (business-analyst), AI solution architecture for copilots (applied-ai-architect-commercial-enterprise), or control implementation for audits (compliance-engineer). UX flows: product-designer. Eval harnesses: prompt-engineer-agent-prompts-evals. Pricing/packaging for platform: product-management-monetization.
Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.
Documentation-driven project development workflow. Intelligently determines task types, executes existing plans or generates new plans using feature-dev. **Use Cases:** - Complete project documentation exists, need to execute development tasks - User specifies to execute a certain plan (e.g., "Execute plan 001") - User requests to develop new features (automatically uses feature-dev to generate plans) **Prerequisites:** - The project should already have a docs/ documentation structure (PRD, SAD, etc.) - For new projects, it is recommended to first use the project-docs-setup skill to create complete documentation - If plan formulation is needed, it is recommended to use the project-planning skill **Relationship with Other Skills:** - project-docs-setup: Creates project documentation structure - project-planning: Formulates development plans (requirement clarification + design discussion + plan writing) - project-workflow: Executes development plans + updates documentation - Recommended workflow: project-docs-setup → project-planning → project-workflow **Trigger Methods:** - "Execute plan 001" / "Continue 001-user-authentication" - "Start development" / "Execute plan" / "Continue last task"
Hypera infrastructure URLs and endpoints reference. Use when user asks about URLs, domains, ingress endpoints, cluster API servers, application URLs, Helm repositories, Git repositories, or needs to check connectivity to services. Provides quick lookup of all external URLs across all environments (hub, dev, prd) and clusters (cafehyna, loyalty, painelclientes, sonora).
Use when working with the `arise` CLI to check readiness, generate review-first plans from strict PRDs or GitHub issues, inspect `.arise/` artifacts, execute reviewed plans, or recover interrupted and integration-blocked runs.
Create comprehensive technical specs for SDK gaps, feature modules, or system centralization efforts. Use when writing specs, PRDs, gap analysis documents, or planning centralization of scattered functionality into a single module. Triggers on "create spec", "write spec", "gap spec", "centralize", "fill the gap".
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.
Read Feishu Cloud Docs (supports multiple links), parse content such as text, tables, images in documents, and convert Product Requirement Documents (PRD) into structured development requirement documents according to the development language and storage structure selected by users
Automatically coordinates multi-skill workflows and triggers follow-up actions. Use when completing PRD creation, implementation, or any milestone that should trigger additional skills. This skill reads the auto-trigger configuration and executes the workflow chain.
Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...
Orchestrates multi-advisor council debates on high-impact architecture, technology, or product decisions. Dispatches 3-5 domain archetype subagents (pragmatic-engineer, architect-advisor, security-advocate, product-mind, devils-advocate, the-thinker) through opening statements, tensions, position evolution, and synthesis phases. Preserves dissent and delivers actionable recommendations with captured risks. Use when evaluating trade-offs, stress-testing a PRD or tech spec, resolving dilemmas with multiple viable options, or when a decision needs diverse expert perspectives. Don't use for simple yes/no questions, factual lookups, creative brainstorming without tradeoffs, or tasks where a single expert perspective suffices.
Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies. Use after /grill-with-docs has settled the domain language and before /to-prd writes per-feature specs. Bridges the product→engineering gap between domain understanding and feature specification — the missing step that mattpocock's chain doesn't cover natively.