devx/docs/specs/DEVX-167.md

DEVX-167: Add dependency-graph, deployment-coordination, and skill-creation skills

Problem

Agents working across the oblachno ecosystem lack shared, persistent context for three recurring pain points:

1. Cross-repo dependency ordering — agents frequently merge downstream PRs before the upstream publish job completes, or forget to bump infra. There is no single reference for which repo produces what and in what order changes must propagate.
2. devx release coordination — devx is the base package pinned by grm, sso-bridge, and infra. Agents repeatedly merge devx PRs and immediately merge downstream bumps without waiting for the PyPI publish job, or bump only one consumer when a change affects all three.
3. Skill quality drift — skills are created ad hoc with inconsistent structure, vague advice, and no automated validation reference. New skills miss required sections, reference nonexistent make targets, and drift across repos.

Approach

Add three SKILL.md files under .devin/skills/:

REQ-1: dependency-graph — shared skill mapping the oblachno ecosystem (repos, what each produces, consumers, release triggers, correct cross-repo change order, state verification checklist)

REQ-2: deployment-coordination — devx-specific skill covering the devx release flow, downstream consumers, manual bump procedure, and common mistakes when coordinating a devx change

REQ-3: skill-creation — shared skill defining skill structure, quality standards, scope rules, automated validation reference, and a creation checklist

Files Affected

• .devin/skills/dependency-graph/SKILL.md (new)
• .devin/skills/deployment-coordination/SKILL.md (new)
• .devin/skills/skill-creation/SKILL.md (new)
• docs/specs/DEVX-167.md (new)

Test Plan

• Verify all three SKILL.md files follow the required structure (H1 title, When to Invoke, Prerequisites sections)
• Verify referenced make targets and file paths exist
• Run make pytest-cov — skill validation tests must pass

Deploy Plan

• Merge to master; skills are consumed by agents immediately on next invocation — no build or deploy step required

Rollback Plan

• Revert the merge commit; remove the three skill directories

Acceptance Criteria

• REQ-1: dependency-graph skill exists with ecosystem map, repo table, dependency chain, cross-repo change order, and state verification checklist
• REQ-2: deployment-coordination skill exists with devx release flow, downstream consumer table, coordination steps, and common mistakes
• REQ-3: skill-creation skill exists with structure template, quality standards, scope rules, validation reference, and creation checklist