القائمة
Deep analysis within a specific domain. Goes deep not wide, using domain-specific vocabulary, frameworks, and constraints.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/benjam3n/reasoningtool --skill nrwd-narrow-domain-analysisيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Route any input through a branching question tree to narrow down the optimal response strategy before writing. Two stages — PERCEIVE (classify input) then ACT (select response). Covers all prompt types.
Generate exhaustive guesses about user input using ALL search methods with coverage tracking. Guessing is SEARCH through possibility space. Tracks space created vs space covered to ensure comprehensive exploration.
Systematically evaluate and select from a set of guesses, options, or possibilities. Combines ARAW analysis with prioritization to determine which guesses are strong, weak, actionable, or eliminable.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | nrwd - Narrow Domain Analysis |
| description | Deep analysis within a specific domain. Goes deep not wide, using domain-specific vocabulary, frameworks, and constraints. |
| output | {"format":"prose"} |
Input: $ARGUMENTS
State the specific domain under analysis. Be precise — narrow beats broad.
DOMAIN: [The specific domain]
DOMAIN LEVEL: [Field > Subfield > Specialty, as specific as possible]
If the input spans multiple domains, pick the primary one. Flag secondary domains for later.
Define what is inside and outside this analysis.
IN SCOPE:
- [What belongs to this domain]
- [What this analysis will cover]
OUT OF SCOPE:
- [Adjacent domains explicitly excluded]
- [Tangential topics to ignore]
BOUNDARY RATIONALE: [Why these boundaries make sense]
Analyze the input using domain-specific depth. This is the core of the skill — resist the urge to go wide.
DOMAIN-SPECIFIC VOCABULARY:
- [Key term 1]: [precise domain meaning]
- [Key term 2]: [precise domain meaning]
APPLICABLE FRAMEWORKS:
- [Framework 1]: [how it applies here]
- [Framework 2]: [how it applies here]
DEEP ANALYSIS:
[The actual analysis, using domain language and frameworks.
This should read like it was written by a domain expert,
not a generalist.]
Identify constraints that only someone in this domain would know about.
DOMAIN CONSTRAINTS:
- [Constraint 1]: [why it matters here]
- [Constraint 2]: [why it matters here]
CONVENTIONS:
- [Convention 1]: [standard practice in this domain]
- [Convention 2]: [standard practice in this domain]
VIOLATIONS: [Does the input violate any domain conventions? If so, flag them.]
Format the final output the way a domain practitioner would expect to see it.
FINDINGS:
[Structured output using the format conventions of the domain.
E.g., a legal analysis uses IRAC, a medical analysis uses SOAP,
an engineering analysis uses requirements/specs format.]
DOMAIN CONFIDENCE: [How confident is this analysis given domain norms?]
RECOMMENDED NEXT STEP: [What a domain expert would do next]
Use with:
/unvs -> Test whether findings generalize beyond this domain/ctgp -> Identify gaps within the domain/skev -> Evaluate a domain-specific method or procedure