scaffold-design-spec

Skipping existing stubs during specification scaffolding is an idempotent behavior that prevents data loss by preserving manually edited files. The process scans the catalog, identifies missing stubs, and only generates new design specification files while leaving existing ones untouched.

Idempotent behavior in specification scaffolding means existing files are skipped to prevent overwriting previous work. This ensures that running the stub generation process multiple times during sprint planning will only create missing design specifications without altering or duplicating current ones.

Yes, specification scaffolding supports multi-instance specification types for product, documentation, and technology categories. It cross-references catalog metadata to determine granularity and generates the appropriate stub structure for each enabled entry.

Yes, specification scaffolding supports multi-instance specification types across product, documentation, and technology categories. It cross-references catalog metadata to determine granularity and generates the appropriate stub structure for each enabled entry.

Scaffolding design specification stubs requires catalog metadata and sprint metadata to identify newly enabled entries. The system uses this information to generate correctly named files with complete YAML frontmatter and a report of created paths for governance.