{
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "regenerative-software",
      "description": "Design and evolve software so agents can preserve its intent, independently evaluate its behavior, and replace implementations at justified boundaries. Use for regenerative software adoption, agent-maintainable architecture for new projects, repository-wide improvement campaigns, and continued evolution of already adopted repositories. Covers existing codebases, greenfield builds, contracts, state, evaluations, provenance, reconstruction, and retirement. For a routine isolated edit with no regenerative or architectural objective, use the repository's normal workflow.",
      "type": "archive",
      "url": "/skills/regenerative-software.zip",
      "digest": "sha256:5ebed09d63470dfa2537ab245ef0288919eabcce3ea5c0b2868813721e2acf20"
    },
    {
      "name": "regenerative-architecture",
      "description": "Design new projects and new capabilities around durable intent, coherent ownership, independently changeable boundaries, and behavioral contracts. Use for greenfield regenerative architecture, agent-maintainable project foundations, contract design, or repairing an entangled seam in an existing codebase. Produce a working vertical slice when implementation is requested, with repository guidance and executable knowledge for future agents.",
      "type": "archive",
      "url": "/skills/regenerative-architecture.zip",
      "digest": "sha256:23c4805346605f4ed26259a2f2ab9a5bf9e4898d7f616141af3c37a8eed7ffca"
    },
    {
      "name": "regenerative-adoption",
      "description": "Adopt regenerative software practices in existing repositories and embed them in ongoing agent work. Use to discover product behavior, preserve legacy knowledge, prioritize a repository-wide campaign, install concise repository operating instructions, or resume a previous regenerative engagement without losing evidence or overwriting other work.",
      "type": "archive",
      "url": "/skills/regenerative-adoption.zip",
      "digest": "sha256:a3a35338ce50928387ecf3414a4d64f8f771e6c2c00f89b9e375b97e72956ae8"
    },
    {
      "name": "regenerative-evaluations",
      "description": "Build meaningful behavioral evaluations that survive implementation changes. Use for regenerative acceptance gates, independent oracles, contract and consumer tests, async lifecycle checks, evaluation failure diagnosis, or runtime model and agent quality assessment. Separate product correctness from test machinery validity and probabilistic quality from hard constraints.",
      "type": "archive",
      "url": "/skills/regenerative-evaluations.zip",
      "digest": "sha256:3a53ae23e8868ed7974c65abeae46c764481b01e03dedc9197fb1cebc996a073"
    },
    {
      "name": "regenerative-state",
      "description": "Preserve durable state and external effects through software evolution. Use for regenerative migration design, historical reader/writer compatibility, backup and recovery rehearsal, asynchronous ownership, retries, cancellation, late results, or stateful implementation replacement. Establish what survives code changes and verify it through real consumers.",
      "type": "archive",
      "url": "/skills/regenerative-state.zip",
      "digest": "sha256:1a4f7e2bd8c3825c4cfeb532ed126d90503af7ed7732fe7f0ff701ac38a63677"
    },
    {
      "name": "regenerative-provenance",
      "description": "Make regenerative software changes traceable and replayable with proportionate input identities, execution receipts, canonical documentation, and operational evidence. Use for multi-stage verification, reliable handoffs, generated-document ownership, evidence correction, or distinguishing local checks from release and runtime claims.",
      "type": "archive",
      "url": "/skills/regenerative-provenance.zip",
      "digest": "sha256:64a67688f67699eccf78522373311ff2ff379a361416283edebfd51678aa9440"
    },
    {
      "name": "regenerative-reconstruction",
      "description": "Exercise implementation replaceability through isolated substitution or fresh-context reconstruction. Use for regenerative survival packs, deletion rehearsals, independent replacements, or claims that another agent can rebuild a unit from retained intent, contracts, state rules, and evaluations. Distinguish source-assisted replacement from pack-only reconstruction.",
      "type": "archive",
      "url": "/skills/regenerative-reconstruction.zip",
      "digest": "sha256:8f371a76895a6ee3717d37dbaeb1cfec8aafc32c6fb9243c07ab0e35e7b8912d"
    },
    {
      "name": "regenerative-evolution",
      "description": "Keep regenerative repositories improving across agent sessions. Use for ongoing change pipelines, incident harvesting, selective revalidation, repository-wide continuation, compatibility retirement, deletion, and compaction. Preserve valid fixes and durable knowledge while removing obsolete complexity and testing whether future changes actually become easier.",
      "type": "archive",
      "url": "/skills/regenerative-evolution.zip",
      "digest": "sha256:2139615eb5174f1544bfb2f2d0369552372ab0647d3154520e61d2d5ee28a4ba"
    }
  ]
}