Blueprint Descriptor Standard (BDS-001)
Use this skill when adding or updating blueprint descriptors so they remain rich enough for MCP exposure and audits without bundling workflow code.
When to Use
- •Creating a new blueprint descriptor under
packages/blueprints/src/descriptors/ - •Updating manifest generation that reads blueprint descriptors
- •Auditing blueprint governance fields (owner, costCenter, roles, SLA, classification)
Instructions
- •Keep IDs consistent:
blueprintIdmust equalmetadata.idand registry key. - •Include governance fields: metadata/security/operations are required.
- •Include schemas: input + config always; output is required for MCP-exposed tools.
- •Validate aiHints: exampleInput must validate against input; for MCP tools, exampleOutput must validate against output.
- •Use CSS-001 classification semantics (do not restate).
See references/blueprint-descriptor-standard.md for the normative specification.