The published schema
From 3.19.0 every key and every hook the skills read is listed once in the plugin's seam registry (schemas/seam-registry.json), with its shape, its default and the skill steps that call it; the JSON Schema (schemas/ds-config.schema.json) and the readable table (skills/setup/references/seam-registry.md) are generated from it. Point your editor at the schema for completion and inline errors with a top-level key, pinned to the release you run:
{
"$schema": "https://raw.githubusercontent.com/devstride/claude-plugin/devstride--v3.45.0/schemas/ds-config.schema.json"
}
An unknown key used to be silently ignored, which quietly switched off whatever it was meant to turn on. Now a wrong shape is an error and an unknown key a warning that suggests the key you probably meant. Keys your own repository's tools read, and the plugin never does, go in repoLocalKeys:
| Key | Shape | Default | Purpose |
|---|---|---|---|
$schema |
URL string | absent | Editor completion and validation against a published schema. The plugin ignores it. |
repoLocalKeys |
array of key prefixes, e.g. ["mergeGuard", "deploy.notes"] |
[] |
From 3.19.0: keys (and everything under them) the check leaves alone because your own tools read them. |
any key starting with _ |
anything, e.g. "_comment": "why this is set" |
absent | A note for the people who read the file. The schema accepts it at any level, in any block, and the plugin never reads it. |
Planning reads very little of this file
Planning never requires it, but uses it when it is there.
planreadsprofileandprofileOverridesfor story grain and spec depth, and may usehierarchyRoles.releaseUnitto resolve an ambiguous release boundary and the release branch/deploy settings to shape production-safe release units.insert-storyandinsert-defecttakehierarchyRolesand the branch settings from it.rationalize-ganttfinds the plan's deferred container bydefects.deferredContainerTitleand its legacy titles, to date that work after the plan.comprehend-planreads none of it. Delivery uses the rest.