skills

Perform a structured, opinionated code review on a diff, file, PR, or code snippet. Triggers when the user types /review, or when they say things like "review this code", "review my PR", "check this diff", "give me a code review", "what's wrong with this code", "critique this implementation", or any variant asking for review or critique of code. ALWAYS use this skill when the user wants structured feedback on code quality, correctness, security, or maintainability. The output is a detailed review report with severity-tagged findings.

Activate this skill ONLY by using the `/hybrid-plan` slash command. Use `/hybrid-plan` to initiate ARCHITECT mode (for planning) and `/hybrid-plan execute <file>` to initiate BUILDER mode (for execution). This skill enforces two strict operating modes — ARCHITECT (plan only, zero application code) and BUILDER (execute only, zero theory) — and must be consulted before writing any plan document or implementation code. Never mix the two modes in a single response.

Generate a comprehensive, professional Product Requirements Document (PRD) before the user starts building an app or software product. Triggers when the user types /prd-spawnner, or when they say things like "buatin PRD", "buat PRD dulu", "I want to create a PRD", "help me plan my app", "generate PRD", "product requirements document", "I'm about to build an app", "planning a new product", or any variant asking to plan/document a software project before development. ALWAYS use this skill when the user wants structured documentation before coding. The output is a deeply detailed .md file (minimum 800 lines) covering every aspect of the product from architecture to deployment.

Generate a comprehensive, engineering-grade test strategy document from a PRD, feature spec, or plain-English description. Triggers when the user types /test-strategy, or when they say things like "create test plan", "how should I test this", "write test strategy", "test coverage plan", "I need a testing strategy", "plan my tests", "what should I test", or any variant asking to plan testing for a feature, module, or entire product. ALWAYS use this skill when the user wants structured test planning before or during development. The output is a deeply detailed .md file covering unit, integration, E2E, performance, and security testing with concrete test cases, tooling recommendations, and coverage targets.

Generate a comprehensive, professional Product Requirements Document (PRD) before the user starts building an app or software product. Triggers when the user types /vibe-prd, or when they say things like "buatin PRD", "buat PRD dulu", "I want to create a PRD", "help me plan my app", "generate PRD", "product requirements document", "I'm about to build an app", "planning a new product", or any variant asking to plan/document a software project before development. ALWAYS use this skill when the user wants structured documentation before coding. The output is a deeply detailed .md file (minimum 800 lines) covering every aspect of the product from architecture to deployment.