{
  "name": "spec-driven-devlopment/spec-as-source",
  "version": "2.1.0",
  "description": "Spec-driven development on OpenSpec, with mechanical spec-as-source enforcement: a custom 'spec-as-source' OpenSpec schema adds file-ownership (targets) and test-verification ([@test]) metadata to every capability spec, three scripts (link check, ownership check, manifest build) keep code and specs from drifting apart, plus requirement-gathering, spec-writer, work-review, and a session-handoff skill with a proactive context-warning hook.",
  "summary": "OpenSpec workflow (propose/explore/apply/archive/sync) plus mechanical spec-as-source enforcement, requirement gathering, spec writing, work review, and session handoff",
  "author": { "name": "Giuseppe Di Canosa" },
  "readme": "README.md",
  "skills": [
    "skills/spec-as-source-setup",
    "skills/requirement-gathering",
    "skills/openspec-explore",
    "skills/openspec-propose",
    "skills/spec-writer",
    "skills/openspec-apply-change",
    "skills/spec-verify",
    "skills/work-review",
    "skills/spec-rebuild",
    "skills/openspec-sync-specs",
    "skills/openspec-archive-change",
    "skills/spec-ci-sync",
    "skills/handoff"
  ],
  "rules": [
    "rules/spec-as-source.md",
    "rules/generated-file-header.md",
    "rules/handoff-suggestion.md"
  ],
  "docs": ["docs/policy.md"]
}