Loading...
Loading...
Found 31 Skills
Creates a new Product Requirements Document (PRD) with auto-numbered filenames in the project's PRD directory. Gathers business context, defines the problem, and produces a structured PRD.
Use this skill when > Generate a structured Product Requirements Document (PRD) from existing conversation context and codebase state. Synthesizes knowledge into a PRD without interviewing the user. Use when documenting requirements for a feature or change to publish to the project issue tracker.
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com."
Create feature definition documents with phased delivery, MVP scope, and definition of done. Use when specifying new product features, user-facing capabilities, or system enhancements that require planning and incremental delivery.
Create documentation-first PRDs that guide development through user-facing content
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Authoritative reference for Anthropic products. Use when users ask about product capabilities, access, installation, pricing, limits, or features. Provides source-backed answers to prevent hallucinations about Claude.ai, Claude Code, and Claude API.
Create, update, validate, or analyze a PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD.
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.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Creates PRDs and plans features.