Workflows contributor guidance

Workflows contains independently installable, instruction-only engineering skills. The host owns execution tools and permissions; Continuity, when configured, owns persistent project knowledge and coordination.

• Keep each skill self-contained and preserve distinct task boundaries.
• Include only guidance that changes a relevant decision or protects a concrete requirement. Reuse current context and evidence. Keep operational guidance independent of model names.
• Writing and layout defaults yield to user and project choices. Keep branch prefixes, commit types and PR types independent.
• Keep repository documentation and commit/PR content in concise English, using Conventional Commits unless explicitly directed otherwise.
• Maintain one canonical explanation. Review-only work stays read-only; browser and visual QA remain opt-in.

For prose changes, review scope, clarity and affected links. For changed skill or manifest metadata, use available host validators and check the affected inventory. For behavioral changes, evaluate relevant realistic requests rather than asserting exact wording. Reuse adequate checks and do not add a test framework for prose.

Verify discovery and selected-skill installation in disposable destinations when package structure or installation behavior changes. Before publication, validate the full skill inventory and aligned manifests. Commits, pushes, publication and changes to user installations require their corresponding authorization; do not ask again when already granted.