wr-itil:scaffold-intake

Scaffolding OSS intake surfaces idempotently involves generating .github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, and CONTRIBUTING.md files with state tracking markers to ensure safe re-runs without duplicating content or overwriting manual changes.

OSS intake surfaces are standardized files like SECURITY.md, SUPPORT.md, CONTRIBUTING.md, and issue templates that govern problem reporting and project contributions. You need to scaffold them when adopting a governance framework to ensure consistent community interaction.

Yes, re-running intake file scaffolding safely handles present-but-outdated files. It uses .claude markers for state tracking to suppress repeat prompts and applies idempotent writes, ensuring existing repository governance files are correctly updated without data loss.

Personalizing CONTRIBUTING.md and SECURITY.md templates is done through template substitution. The scaffolding process automatically injects variables like the project name, repository URL, active plugins, and designated security contact directly into the generated files.

Scaffolding intake surfaces requires foreground-synchronous invocation. This execution pattern aligns with the ADR-036 contract, ensuring the governance file generation process completes directly within the active workflow context before returning control.

Automating governance file creation across downstream repositories is best handled by an idempotent scaffolding process. It enforces consistent OSS intake surfaces, applies template substitution for project-specific details, and uses markers to track state for safe, repeatable automation.