What problem does it solve? Changes to the SEIS Master Prompt operating contract touch many surfaces—governance docs, JSON manifests, generated reports, CI workflows, and CODEOWNERS—and it is easy to update one surface while leaving the others inconsistent. This Skill keeps every SEIS Master Prompt change tied to the canonical repository artifacts and the dedicated governance quality gates. ## Core Features & Use Cases - Canonical Surface Mapping: Points to the contract, ADR, checklist, GitHub controls doc, JSON manifests, generated report, and CI workflow so edits land in the right files. - Ordered Workflow: Classifies changes by domain, applies the change checklist, updates source manifests before generated outputs, and refreshes the governance report from its generator script. - Validation Gates: Defines the expected npm checks (check:seis-master-prompt-report, check:seis-master-prompt, check:open-source-governance, quality) and when to escalate from focused checks to the full quality chain. - Use Case: When adding a new GitHub control to the SEIS repo, use this Skill to update the controls manifest, regenerate the governance report, align CODEOWNERS and workflow files, and run the dedicated check before claiming readiness. ## Quick Start Use the SEIS Master Prompt governance workflow to plan and validate my change to the repository's governance documentation and generated report.
