القائمة
Use when a feature request is loose or ambiguous and needs a reviewable spec before planning — turns "add X somehow" into user stories, acceptance criteria, out-of-scope, and open questions via spec_writer
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants a security review of code or a diff — OWASP/CWE findings with severity, taint/data-flow analysis, and concrete fixes via security_review
Use when the user wants tests generated for code or a diff — enumerates edge cases and failure modes first, then emits runnable test code via testgen
Use when a task would benefit from a structured thinking technique but you're not sure which — recommends the right prompt technique for the intent (debug, spec, refactor, decision, design) and applies it
Use for decisions or judgments worth multiple independent perspectives — multi-model council with parallel analysis, search grounding, and synthesis (30-60s); for a quick single-call verdict use the jury tool directly
Use when the user shares or finishes a plan and wants it stress-tested before execution — adversarial multi-model pre-mortem with ranked risks, mitigations, and concrete plan edits
Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict
| name | spec |
| description | Use when a feature request is loose or ambiguous and needs a reviewable spec before planning — turns "add X somehow" into user stories, acceptance criteria, out-of-scope, and open questions via spec_writer |
| user-invocable | true |
files.spec_writer with request, context, files, and format if the user prefers user_story or gherkin (default both).planner_maker (or /blueprint) to plan the HOW.Requires OPENAI_API_KEY. If the tool returns its missing-key error, relay it and suggest /setup.