القائمة
Spec-Driven Development — the PRD/SPECS/TESTS triangle, EARS criteria, governance hierarchy. Load when creating or changing specs, features, or ADRs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
| name | sdd |
| description | Spec-Driven Development — the PRD/SPECS/TESTS triangle, EARS criteria, governance hierarchy. Load when creating or changing specs, features, or ADRs. |
Three layers, three owners, one triangle:
| Layer | File | Answers | Owner |
|---|---|---|---|
| WHAT & WHY | PRD.md | product intent, personas, principles | product |
| HOW | SPECS.md (+ §ADR registry) | architecture, interfaces, decisions | architect |
| VERIFY | TESTS.md | pyramid, coverage targets, conventions | qa (definition), execution tiers (authoring) |
memory-long.md + active ADRs — the constitutionPRD.md — requirementsSPECS.md — architecturememory-medium.json — sprint stateAn agent finding a contradiction between levels stops and escalates — it never picks silently.
WHEN <event> THE SYSTEM SHALL <behavior>WHILE <state> THE SYSTEM SHALL <behavior>IF <condition> THEN THE SYSTEM SHALL <behavior>These criteria become the verification keys of Sub-Agent Reports downstream — write them checkable.
New feature → instantiate core/templates/spec-kit.md (What / Why / EARS criteria / Dependencies) → register in memory-medium.json with FEAT-YYYY-MM-DD-slug id.
Structural decision → architect drafts from core/templates/adr.template.md → deliberation if weight demands (core/protocols/deliberation.md) → human OK → registry in SPECS §ADR + one-line ref in memory-long. Anchors (ADR-NNN) are graph edges — always reference them in commits and specs.