Repo layout
The repo has runtime payload, source docs, generated docs, fixtures, tests, and release tooling.
They are not interchangeable.
Important paths
| Path | Role |
|---|---|
skills/implementaudit/ | Repo runtime source; contents are flattened into the archive root. |
skills/implementaudit/templates/ | Run artifact templates: roadmap, state, protocol, thinking, sidecars, tools, context, and phase goal. |
skills/implementaudit/references/ | Progressive-disclosure references used by the skill during runs. |
skills/implementaudit/scripts/ | Repo location for helper scripts; the built skill archive ships them as root scripts/. |
CONTRIBUTING.md | Current contributor and maintainer contract: owner selection, generation, validation, review, and public-mutation boundaries. |
.github/workflows/pages.yml | GitHub Pages build, validate, and deploy workflow; public-current claims require successful workflow evidence and any required owner gate. |
.github/workflows/validate.yml | Validation workflow mirroring local package checks. |
docs/diagrams/ | Mermaid diagram sources used by README generation. |
docs/portal/ | Generator-owned source tree for this generated docs portal. |
dist/ | Generated output; gitignored. |
fixtures/ and tests/ | Repo-only validation surfaces. |
docs/audits/ | Historical audit ledgers and release evidence. |
Package boundary
In the repository, the runtime source lives under skills/implementaudit/.
In the built IMPLEMENTAUDIT.skill archive, SKILL.md, references/, scripts/, and templates/ sit at archive root for host import.
Do not claim the archive contains a nested skills/ directory.
Repo-only docs, fixtures, tests, local run roots, sidecar stores, and generated docs are not runtime payload.
Source surfaces
AGENTS.md is the concise maintainer bootloader, CONTRIBUTING.md owns the current contribution workflow, and README.md is the new-user public entry.skills/implementaudit/ owns the packaged runtime; CHANGELOG.md owns release chronology; release reports own exact publication evidence.
Contributor route
Read the current contributor guide before changing runtime, package, public-doc, validation, or release owners.
It records source-versus-generated ownership, platform requirements, focused-to-complete validation, registry and helper reachability rules, and the independent authority gates for commits, pull requests, issues, tags, releases, and publication.
Docs portal generation
The portal is generator-owned.
Edit docs/portal/, then regenerate generated output instead of hand-editing dist/.
scripts/build-docs-portal.pybuilds the portal from source pages, shared assets, andsite.json.scripts/check-docs-portal.pyvalidates routes, anchors, metadata, and generated shell behavior.scripts/verify-docs-portal.shruns build plus validation as the narrow docs gate.- GitHub Pages or any published docs update remains a separate owner-authorized action.