Loading...
Loading...
Found 314 Skills
Convert bug reports into prd.json user stories for autonomous fixing. Use after running test-and-break skill. Triggers on: convert bugs to stories, fix these bugs, add bugs to prd, create fix stories.
PRD Document Management, provides creation and update functions for main PRD and module PRD. Supports quick generation using natural language requirement templates. Call when you need to create or update PRD documents.
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
Create Product Requirements Documents (PRDs) that define the end state of a feature through iterative design interview. Use when planning new features, migrations, or refactors. Generates structured PRDs with acceptance criteria, testing strategy, and architectural decisions.
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.
Full-pipeline iOS App Store opportunity research. Discovers underserved niches, analyzes competitor gaps, estimates revenue, produces scored top-3 opportunity reports, and writes MVP PRDs — all through browser and web research. Use when the user wants to find profitable iOS app ideas, research App Store charts, analyze competitor apps (ratings, reviews, revenue, gaps), generate opportunity reports, or write MVP PRDs. Triggers on "find app opportunities", "app store research", "what app should I build", "research this app category", "find a gap in the app store", "ios app ideas".
Use when a Lightning Web Component data need is described in ambiguous natural language — turn "get contact info" or "show account data" into a clear, PRD-ready data-requirements spec. TRIGGER when the user says "define data requirements for this LWC", "turn this PRD data section into validated object/field names", "recommend GraphQL vs UIAPI for this data need", "validate these Salesforce API names", or "spec out the LDS adapter for this component", or references LWC bundle files (`.js`, `.js-meta.xml`) whose data layer is not yet specified. DO NOT TRIGGER when the data layer is already fully specified, when authoring the actual query or adapter code from a known spec, or when implementing an LWC end-to-end (use experience-lwc-generate).
Use when stress-testing a plan, getting grilled on a design, or before writing a PRD.
Unified prompt engineering and requirements planning. Use when exploring ideas, improving prompts, creating PRDs, generating task breakdowns, or iterating on existing plans. Includes Jira integration for creating subtasks from plans.
Creates well-formed tasks following a template that engineers can implement. Triggers on: 'create tasks', 'define work items', 'break this down', creating tasks from PRD, converting requirements into actionable tasks, feature breakdown, sprint planning.
Creates detailed Product Requirements Documents in Markdown format. Use when writing PRDs, defining feature requirements, or creating specification documents for development teams.