Loading...
Loading...
Found 42 Skills
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.
Enhance PRDs, feature specs, user stories, or product briefs with explicit OWASP ASVS coverage and FIASSE v1.0.4 SSEM implementation guidance — before code is written. Trigger on "harden the PRD/spec", "choose ASVS level", "map features to ASVS", "find missing security requirements", "add NFRs for security", "make these requirements securable", "security-review my product brief". For code review use securability-engineering-review; for code generation use securability-engineering.
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.
Эксперт feature documentation. Используй для документации функций, release notes, user guides и product documentation.
Convert 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.
Create documentation-first PRDs that guide development through user-facing content
Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria.
Transforma o problema em proposta, jornada principal, módulos essenciais e limites claros para a versão 1.0.
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.
Create a complete SPEC from scratch through an exhaustive requirements interview before any planning or implementation. Use this skill whenever the user asks to create, define, clarify, scope, or write a spec/SPEC/PRD/requirements document from an idea, especially when they want to avoid assumptions, start at "step zero," or prepare input for later planning workflows. This skill must question goals, requirements, constraints, edge cases, business rules, and acceptance criteria before drafting the final spec.
Definición del artefacto de producto: convierte una idea en BORRADOR en un contrato de producto completo — problema, requisitos con IDs estables, actores, flujos, ejemplos de aceptación, fronteras de alcance — como UN artefacto que madura in-place (nunca dos docs que driftan), con right-sizing (el doc crece con el contenido, no por plantilla) y confirmación de alcance ANTES de escribir (Declarado/Inferido/Fuera). Usar en la etapa de definición de wachi-producto, o suelta para escribir/enriquecer el contenido de una ficha funcional. Aterriza en RumIAndo: contenido versionado de la ficha + transición BORRADOR→PARA_VALIDAR. NO decide adopción de tecnología (wachi-validacion-interna) ni valida con usuarios (wachi-validacion-usuario).
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."