jr-new-command

A contract-first workflow codifies command requirements before generation, enforcing frontmatter validation and in-repo placement under agents/skills. This approach standardizes command creation for feature expansion and governance reviews, reducing ambiguity and rework.

Frontmatter validation ensures contract clarity during command generation by enforcing standardized metadata before new skills are placed in the repository. This prevents structural inconsistencies and reduces the rework typically caused by ambiguous command definitions.

The best way to standardize onboarding new commands is implementing a contract-based creation workflow with governance rules. This approach codifies requirements upfront and generates documentation alongside skill placement under agents/skills to maintain ecosystem consistency.

Yes, you can use the contract-driven command-generation process for governance reviews. It standardizes skill creation by enforcing frontmatter validation and in-repo placement under agents/skills, ensuring all new commands meet established governance and documentation standards.

Yes, a documentation-first approach updates discovery surfaces automatically during the command creation workflow. By enforcing the contract and validating frontmatter, the process generates necessary documentation alongside placing the new command in the repository.

The standardization process is limited to in-repo skill ecosystems, specifically enforcing placement under agents/skills. It relies on a contract-first workflow with frontmatter validation, meaning commands outside this directory structure or without proper contracts may not be governed correctly.