Skip to content

improvement: generate schema.json from manifest.md frontmatter #452

@Luis85

Description

@Luis85

Context

Part of the plugin audit in #444 (§2, R2). The 12 manifest.md / schema.json pairs under plugins/ are currently maintained manually — creating drift risk. The audit flags this as blocking for the MCP Server (issue #316) because it consumes schema.json in production.

Work

Add a build step that generates plugins/*/schema.json from the YAML frontmatter of each corresponding manifest.md.

High-level approach:

  1. Extend scripts/build-claude-plugin.ts (or a new scripts/generate-plugin-schemas.ts) to:
    • Read YAML frontmatter from each plugins/*/manifest.md
    • Produce a JSON Schema-compatible schema.json in the same folder
  2. Add generate:schemas npm script
  3. Add check:schemas npm script that diffs generated vs. committed — fails CI if stale
  4. Wire into npm run verify

Constraints

Definition of Done

  • generate:schemas produces schema.json for all 12 plugin manifest pairs
  • check:schemas fails if any schema.json is stale vs. its manifest.md
  • npm run verify includes check:schemas
  • No manual schema.json edits required after this lands
  • Verify gate green

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Critical / blocks current releasearea:scriptsScript tooling and verificationenhancementNew feature or requestroadmap:automation-hardeningv0.7 automation contract — registry, verify tiers, agent checks, Zod runtime validationroadmap:mcp-serverMCP server exposing workflow.* methods so any LLM client can drive the 12-stage methodologytrack:specorator-improvementImprovement to the Specorator template itself

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions