steerspec@github:~$

SteerSpec

Specs-driven AI configuration synchronization for GitHub organizations.

v0.1.0-draft 217 rules · 26 entities RFC-2119 compliant

Your CLAUDE.md drifts. .claude/agents/ mutates. Teams patch configs manually and drift goes undetected until it breaks something. Reconciling AI configuration files across dozens of repos is pure toil.

SteerSpec is a formal specification and toolset that treats AI configuration files the same way you treat infrastructure—as code, versioned, templated, and automatically synchronized. Define once in a central manifest. Propagate everywhere via pull request. Detect drift on a schedule.

Because vibe coding without a spec is just vibing.

// sample rule

steerspec-sync.yml — [SYNCMFST-001.0/D]

# [SYNCMFST-001.0/D]
# A SyncManifest MUST declare a unique identifier,
# a version, and at least one template target.

id: "steerspec/my-org@main"
version: "0.1.0"

templates:
  - path: "CLAUDE.md"
    source: "templates/CLAUDE.md.j2"
    targets: "*"        # all repos in org

  - path: ".claude/agents/security-review.md"
    source: "templates/agents/security-review.md.j2"
    targets:             # selected repos only
      - "api-gateway"
      - "auth-service"

sync:
  strategy: "pull-request"  # MUST | SHOULD | MAY
  on_conflict: "open-issue"
  drift_check: "schedule"   # cron: '0 9 * * 1'

// implementation status

[✓] Specification — core, config, versioning, actions, conflicts 217 rules
[~] Sync GitHub Action in progress
[·] Monitor GitHub Action planned
[·] Conflict detection planned
[·] CLI tool planned