القائمة
Review Q2/Q3 changed business paths for production diagnosability and persist structured review input.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/yezhwi/superpowers-engineering-harness --skill diagnosability-reviewيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when starting or resuming a task in a repo with .harness/ state, when unsure which harness phase comes next, or when asked to run the Engineering Harness loop end-to-end. Orchestrates the fixed state machine; MUST NOT implement business code itself.
Turn a User Requirement into a Task Contract: Acceptance Criteria, Requirements, Invariants, Risks, Verification Plan. Produces .harness/requirements.yaml and .harness/invariants.yaml and advances task state CREATED -> SPECIFYING -> PLANNED. This skill MUST NOT implement business code.
Adversarial review of a Task Contract: construct failure scenarios, attempt to violate Requirements and Invariants. Produces .harness/findings/FND-nnn.yaml files with status=PROPOSED only. This skill MUST NOT confirm bugs, review code style, or suggest refactors.
عرض SKILL.md
| name | diagnosability-review |
| description | Review Q2/Q3 changed business paths for production diagnosability and persist structured review input. |
Read .harness/observability.yaml, changed files, declared direct dependencies, and existing logging, correlation, masking, exception-handler, and reason-code conventions.
Do not scan whole repository. Do not add code. Do not prescribe logger framework.
For each review, create input for harness review diagnosability --file <file> with all checks:
business_keys
external_failure_context
state_transitions
caller_rejections
sensitive_data
duplicate_exception_logging
low_value_logging
Use pass, fail, or not_applicable. Every fail needs concrete FND-* DIAG Finding with linked REQ-*, code location, scenario, severity, reason code, and static-compliance required checks.
Never recommend full-object logging, method entry/exit logs, automatic insertion, or generic logging best practice. Claim only reviewed-scope evidence.