Context and request
The Repository Standard requires every module repository to stand on its own, carrying its own governance, community, agent-onboarding, and automation files rather than relying on the organization .github fallback. Json currently carries 6 of the 13 required files.
Missing: CONTRIBUTING.md, SECURITY.md, SUPPORT.md, CODE_OF_CONDUCT.md, AGENTS.md, CLAUDE.md, and .github/pull_request_template.md. README.md links to a CONTRIBUTING.md that does not exist. Several files that are present have drifted from what Template-PSModule now ships, and the repository's own metadata is incomplete.
Scope
In scope: the missing baseline files, drift in the managed configuration files, and the repository's GitHub metadata.
Out of scope: README.md, which has its own outcome, and adopting the Custo distribution runtime.
Aggregate acceptance criteria
- All 13 required baseline files listed in the Repository Standard exist in the repository.
- An agent with no prior context can enter through
AGENTS.md and reach the canonical guidance in PSModule/docs without being told where to look.
- Opening a pull request scaffolds the MSX PR Format.
- The managed configuration files match what
Template-PSModule ships, or the difference is deliberate and recorded.
- The repository's description, topics, and custom properties satisfy Required repository metadata.
Technical decisions
Content for the community files comes from PSModule/Template-PSModule, which is the source of the default shape. These are pointers and policy statements, not repository-specific prose, so they should be adopted rather than rewritten.
AGENTS.md and CLAUDE.md go at the repository root. The PSModule Repository Standard specifies root placement with CLAUDE.md importing AGENTS.md via @AGENTS.md; the MSX Repository Standard specifies .claude/CLAUDE.md. The PSModule standard governs module repositories and matches what Template-PSModule ships, so root placement wins here. The discrepancy between the two standards is worth raising against the docs repositories separately.
The metadata work produces no repository artifact and follows the operational delivery path.
Implementation plan
Delivery is tracked through the native sub-issues on this PBI.
Context and request
The Repository Standard requires every module repository to stand on its own, carrying its own governance, community, agent-onboarding, and automation files rather than relying on the organization
.githubfallback.Jsoncurrently carries 6 of the 13 required files.Missing:
CONTRIBUTING.md,SECURITY.md,SUPPORT.md,CODE_OF_CONDUCT.md,AGENTS.md,CLAUDE.md, and.github/pull_request_template.md.README.mdlinks to aCONTRIBUTING.mdthat does not exist. Several files that are present have drifted from whatTemplate-PSModulenow ships, and the repository's own metadata is incomplete.Scope
In scope: the missing baseline files, drift in the managed configuration files, and the repository's GitHub metadata.
Out of scope:
README.md, which has its own outcome, and adopting theCustodistribution runtime.Aggregate acceptance criteria
AGENTS.mdand reach the canonical guidance inPSModule/docswithout being told where to look.Template-PSModuleships, or the difference is deliberate and recorded.Technical decisions
Content for the community files comes from
PSModule/Template-PSModule, which is the source of the default shape. These are pointers and policy statements, not repository-specific prose, so they should be adopted rather than rewritten.AGENTS.mdandCLAUDE.mdgo at the repository root. The PSModule Repository Standard specifies root placement withCLAUDE.mdimportingAGENTS.mdvia@AGENTS.md; the MSX Repository Standard specifies.claude/CLAUDE.md. The PSModule standard governs module repositories and matches whatTemplate-PSModuleships, so root placement wins here. The discrepancy between the two standards is worth raising against the docs repositories separately.The metadata work produces no repository artifact and follows the operational delivery path.
Implementation plan
Delivery is tracked through the native sub-issues on this PBI.