SFDS / checklist

Validation-Checklist.md

Review a standard suite for structure and adoption guidance.

DownloadView source file Read related standard

Useful when

I want to formalize a repeatable practice.

Choose your situation

What you should change

Select applicable checks and record evidence for your own standard.

Use only the parts that help. These are starting points, not rigid requirements.

View resource

# [Standard Name] Validation Checklist

## Suite Validation

- [ ] `README.md` exists and explains the standard's City Hall role.
- [ ] Primary specification exists and is named by the README.
- [ ] `[StandardName].manifest.toml` exists and describes the standard suite.
- [ ] Required suite docs exist.
- [ ] Scope is clear.
- [ ] Non-goals are clear.
- [ ] Adopter schemas or manifest templates are separate from the standard-suite manifest.
- [ ] Templates exist or are explicitly deferred.
- [ ] Examples exist or are explicitly deferred.
- [ ] Validation procedure is documented.
- [ ] Known gaps are recorded.

## Adopter or Domain Validation

- [ ] Adopter-required files are named.
- [ ] Adopter validation steps are documented or explicitly deferred.
- [ ] Required templates and schemas are present when the standard governs project or artifact records.

Related resources

SFDS / template / Quick win

Standard-Specification.md

Turn a repeatable practice into an explicit standard specification.

View & adapt Download

SFDS / template / Quick win

StandardName.manifest.toml

Describe a standard suite, version, maturity and supporting files.

View & adapt Download