Loading...
Loading...
Found 322 Skills
PRD Expert Advisor Mode. Three well-known PM/CEO act as advisors, proactively review PRD, identify weak points and provide improvement solutions that can be directly written into the document. Users decide whether to adopt via accept/reject. Trigger methods: /li-prd-review, "Enhance PRD", "Expert Advisor", "Help me review this PRD", "Let experts review the PRD", "What are the loopholes in the PRD", "Help me optimize the PRD", "What other issues are there with the PRD". Even if users don't mention "PRD", this skill should be triggered as long as they want expert roles to review a product document and provide improvement solutions. DO NOT trigger for: PRD generation tasks (use li-prd), content script generation, topic analysis and other content creation tasks.
Genera un PRD (Product Requirements Document) liviano a partir de una idea de producto, listo para revisar y pulir. Use when the user asks to generate, draft, or create a PRD, product requirements document, or define product requirements for a new project or feature.
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
Generates professional PRD (Product Requirements Document) files optimized for AI coding tools. Takes a rough product idea, asks clarifying questions, and outputs a structured PDF ready to feed into AI coding assistants.
Analyze existing PRD to identify and recommend the single highest-priority task to work on next
Use this when you need to execute R2 in the sdlc-dev product requirement Spec process, transcribe requirements/solution.md into a deliverable, acceptable, and testable requirements/prd.md, while avoiding guessing file paths, continuing generation when solution.md is missing, or using "Pending Questions/Open Questions" to replace the verification checklist.
Create Product Requirements Documents. Use when defining new features, projects, or initiatives. Covers user stories, acceptance criteria, and scope definition.
Close a PRD that is already implemented or no longer needed
Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation
Generate structured PRD documents for n8n automation workflows. Use when planning n8n workflows, creating automation requirements, starting a new n8n project, or preparing workflow specifications before building.
[Hyper] Create or update a ManyFast-style AI planning package from a rough product idea: PRD, visual planning diagram, feature spec, user flow, low-fidelity wireframe, HTML preview viewer, source log, and optional flow tracking under `.hypercore/prd/[slug]/`. Use when the user wants product planning output before implementation, especially PRD plus diagram/specs/flows/wireframes.
Runs an autonomous delivery loop from an existing PRD to implementation, issue triage, per-slice verification, and final repo validation. Use when the user has already created or approved a PRD and asks to automate to-issues, tickets, triage, ready-for-agent implementation, validation, or production-ready completion.