skf-brief-skill

Use guided discovery to collect target repository, language, scope hints, and intent, which orchestrates validation and scoping steps to produce a canonical skill-brief.yaml for downstream automation.

Skill scope definition is the process of turning user intent and repository context into a precise brief. You need it when enforcing a canonical contract for skill scoping and version handling to reduce drift in downstream automation.

Yes, skill brief validation supports both interactive and headless modes, allowing you to enforce schema rules, version precedence, and provenance within CI workflows for reliable automation.

A validated skill-brief.yaml output generates fields including name, version, target_version, source_repo, language, description, forge_tier, scope, and doc_urls for downstream tooling consumption.

Strict version and target handling prevents skill drift by enforcing schema rules and version precedence during validation, ensuring consistent skill boundaries and reducing staleness across downstream automation pipelines.

Automated skill scoping requires clear user intent and repository context to function effectively, relying on strict version handling and schema validation to maintain boundaries rather than dynamically inferring missing scope parameters.