skill-depuis-artefact

Derive a reusable skill from an incident report by extracting repeatable task patterns, critical corrections, and trigger conditions. The output is a reusable skill candidate anchored to the source details.

Extract repeatable patterns from runbooks by isolating reusable mechanics from context-specific data while preserving critical corrections. This derives an evidence-based skill candidate tied to the source artifact.

You cannot derive a skill from abstract brainstorming without a real artifact. Derivation requires a concrete source like conversations, incidents, or documents to anchor results and avoid abstract ideation.

Extracted resources include repeatable task steps, critical corrections, trigger conditions, and minimal reusable references or scripts. These elements form the scoped skill candidate derived from the conversation.

Avoid artifact-to-skill derivation when documentation lacks concrete incidents or repeatable workflow patterns. The process requires a real artifact to extract mechanics from; abstract ideation without contextual data yields no scoped skill.