Loading...
Loading...
Found 40 Skills
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.
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.
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.
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).