aws-coworker-development

Governance guardrails for extending AWS Coworker are enforced through mandatory frontmatter validation in SKILL.md, design-tenet checks, and production safety gates. This ensures all new skills, agents, or commands pass compliance checks before implementation.

The plan-then-execute workflow for AWS Coworker development requires explicit approval gates between planning and implementation phases. It integrates governance checks and design-tenets validation to prevent unsafe deployments and production risks.

Yes, mandatory frontmatter in SKILL.md is required to add new AWS Coworker commands. The guardrails specify frontmatter usage and gating rules to ensure structured, approved changes and prevent production risks.

The best way to validate design tenets before restructuring AWS Coworker components is using the built-in design-tenets validation combined with governance checks. Review CLAUDE-DEVELOPMENT.md and docs/DESIGN.md before proposing modifications.

Approval gates for AWS Coworker agent modifications should be used whenever you plan to add new skills, agents, or commands, or restructure components. This plan-then-execute process ensures safe, approved changes and prevents production risks.

AWS Coworker requires design-tenets validation for safe development to codify mandatory guardrails before any modification. This governance process prevents unsafe deployments by ensuring all changes adhere to structured design principles.