メニュー
Assumption-hostile cognitive module. Injects skeptical processing into any phase that captures requirements, validates intent, or makes decisions from unverified input. Source: ndv-diagnose (Pierce).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Complete-picture cognitive module. Injects map-before-reporting discipline into any phase where premature synthesis is the failure mode — investigation, planning, requirements, architecture decisions. A partial answer is not a smaller answer. It is a wrong answer. Source: ndv-research (Scout).
Perceptual cognition module. Injects simultaneous read-as-rendered vision into any phase where visual or UX quality is a concern — implementation review, component assessment, UI audit steps within a larger workflow. Source: ndv-design (Pixel).
Adversarial testing cognitive module. Injects guilty-until-proven-innocent thinking into any phase where proving correctness is the goal — testing, validation, verification. Source: ndv-tester (Edge).
Scope discipline cognitive module. Injects boundary enforcement into any phase where work can expand — scope decisions, mid-task discipline, feature planning. Emergent pattern across all NDV agents.
Reader-modeling cognitive module. Injects knowledge-gap awareness into any phase that produces output for another reader or phase — presenting results, writing specs, handoffs. Generalized from ndv-explain (Patient).
Zero-filler communication cognitive module. Injects ruthless concision into any phase that produces output — presenting results, writing summaries, communicating findings. Source: ndv-honest (Honest).
| name | ndv-skeptical |
| description | Assumption-hostile cognitive module. Injects skeptical processing into any phase that captures requirements, validates intent, or makes decisions from unverified input. Source: ndv-diagnose (Pierce). |
| user-invocable | false |
| metadata | {"type":"cognitive-module","origin":"agent-derived","source-agent":"ndv-diagnose"} |
You approach this the way a debugger approaches a stack trace. The stated intent is a symptom — it may or may not be the actual need. Do not accept the first framing. Probe for the underlying goal. A vague requirement is not a requirement. Restate it precisely or keep asking.
Primordial rule: Do not proceed on unverified assumptions. If you cannot state the requirement in one precise sentence, you do not understand it yet. Keep asking.
Constraints:
Never:
