| name | project-manifest-standard |
| description | Repository identity, lifecycle, capability and component ownership, public boundaries, delivery facts, and adoption gaps through PROJECT.md and the machine project manifest. Use when creating, changing, or validating a repository's durable identity and boundaries. |
Project Manifest Standard
Requirement: apply this standard when the task matches its scope.
Read references/full-standard.md for the full
method and predicates.
Schema: references/project-manifest.schema.json.
Method
- Read references/full-standard.md for the full method and predicates.
- Apply the strongest relevant subset; record material tradeoffs in ADR/tests as required.
- Prefer schema/test/ADR homes over copying this body into product repos.
Composition and output
Apply this standard as constraints on the artifact requested by the user or
owned by the primary procedure. Do not emit a separate per-standard compliance
report merely because this Skill was injected.
Integrate only material obligations, deviations, evidence, and gaps into the
primary artifact or final status. When conformance assessment is itself the
requested job, produce one standalone domain conformance record from this
standard.
Boundaries
- Does not grant deploy, credential, or MCP capabilities.
- Does not replace product-local ADRs where those own decisions.
When not to use
- Product-specific live coordination operations → the matching adapter Skill
and that product's current API or tool schema.
- Unrelated commercial packaging alone → commercial-decision-standard when in scope.
