skill-definir-perimetre

To define a scoped skill from a vague request, you extract a single coherent capability, establish trigger conditions, and set explicit non-goals. This bounding process creates a structured concept unit ready for downstream redaction.

Explicit non-goals define what a bounded capability will not accomplish, preventing overlap with adjacent skills. Establishing non-goals ensures the capability remains tightly scoped to a single coherent action, avoiding duplication and maintaining clarity for downstream writers.

Identifying overlaps and gaps requires referencing adjacent skills to map existing capabilities against the new bounded scope. This detects functional duplication and highlights uncovered areas, ensuring the new skill fits cleanly into the broader ecosystem.

No, the scope definition process does not output the final SKILL.md file. It produces a bounded capability concept with trigger signals, boundaries, and references, intentionally avoiding the drafting of final evaluation materials or redaction files.

Aligning with cadre-perimetre guidance requires the scoped skill concept to satisfy a predefined structure containing a name, trigger signals, boundaries, and references. This provides a reusable framing note for downstream skill writers.