docs(skills): require spec-graph skill as dependency for planner/executor/verifier

Add 'Required Skill Dependencies' section at the top of each skill so

agents load the spec-graph schema reference (entity/relation types, edge

matrix, validation rules) before performing any graph operations.

Without spec-graph skill loaded, agents waste tokens guessing at the

schema and hit INVALID_INPUT/INVALID_EDGE errors (e.g., trying nonexistent

relation types like has_risk, mitigated_by, addresses for risks, when only

'mitigates' from decision/test/crosscut to risk is valid).

Author: tyeongkim

skills/spec-executor/SKILL.md

@@ -16,6 +16,21 @@ description: >
 Keeps spec-graph synchronized with implementation progress. This skill manages graph
 updates only — implementation approach is the agent's discretion.
 
+## Required Skill Dependencies
+
+**STOP. Before proceeding with this skill, you MUST load the `spec-graph` skill.**
+
+The `spec-graph` skill provides the schema knowledge required to operate spec-graph correctly:
+- Valid entity types and their ID prefixes (API, STT, TST, QST, ASM, etc.)
+- Valid relation types per layer (`delivers`, `covers`, `belongs_to`, `precedes`, etc.)
+- Edge matrix: which `(from_type, to_type, relation_type)` combinations are allowed
+- Impact analysis semantics: what `spec-graph impact` returns and how to act on it
+
+**Without `spec-graph` skill loaded, you will hit `INVALID_INPUT` and `INVALID_EDGE` errors
+and waste tokens guessing at the schema.** This is non-negotiable.
+
+To load it, invoke the `skill` tool with `name="spec-graph"` before continuing.
+
 ## Prerequisites
 
 - `spec-graph` CLI installed and available in PATH

skills/spec-planner/SKILL.md

@@ -16,6 +16,21 @@ description: >
 Transforms specifications into a validated spec-graph plan. The graph — not markdown — is
 the source of truth. This skill enforces a strict procedure; follow each step in order.
 
+## Required Skill Dependencies
+
+**STOP. Before proceeding with this skill, you MUST load the `spec-graph` skill.**
+
+The `spec-graph` skill provides the schema knowledge required to operate spec-graph correctly:
+- Valid entity types and their ID prefixes (REQ, DEC, ACT, RSK, PLN, PHS, etc.)
+- Valid relation types per layer (`mitigates`, `has_criterion`, `covers`, `belongs_to`, etc.)
+- Edge matrix: which `(from_type, to_type, relation_type)` combinations are allowed
+- Validation rules: what makes a graph valid across arch/exec/mapping layers
+
+**Without `spec-graph` skill loaded, you will hit `INVALID_INPUT` and `INVALID_EDGE` errors
+and waste tokens guessing at the schema.** This is non-negotiable.
+
+To load it, invoke the `skill` tool with `name="spec-graph"` before continuing.
+
 ## Prerequisites
 
 - `spec-graph` CLI installed and available in PATH

skills/spec-verifier/SKILL.md

@@ -16,6 +16,21 @@ description: >
 Verifies implementation fidelity against spec-graph and signs off completed phases.
 This skill is the sole authority for transitioning phases to `resolved`.
 
+## Required Skill Dependencies
+
+**STOP. Before proceeding with this skill, you MUST load the `spec-graph` skill.**
+
+The `spec-graph` skill provides the schema knowledge required to operate spec-graph correctly:
+- Valid entity types and their ID prefixes (REQ, DEC, ACT, RSK, API, STT, TST, etc.)
+- Valid relation types per layer (`delivers`, `covers`, `mitigates`, `verifies`, etc.)
+- Validation rules: arch coverage, mapping completeness, unresolved checks (e.g., RSK needs `mitigates`)
+- Phase lifecycle semantics: draft → active → resolved transitions
+
+**Without `spec-graph` skill loaded, you will misinterpret validation output and sign off
+incomplete phases.** This is non-negotiable.
+
+To load it, invoke the `skill` tool with `name="spec-graph"` before continuing.
+
 ## Prerequisites
 
 - `spec-graph` CLI installed and available in PATH