propose-a-skill

To decide if a work procedure is worth capturing as a reusable skill, evaluate it for repeated execution patterns, non-obvious complexity, and cross-cutting impact across your projects.

The best way to document work procedures for code reuse is to draft a skill proposal that captures the task logic, ensuring it does not duplicate existing skills and is ready for human review.

Skill drafting handles procedures with non-obvious complexity by assessing the task against specific criteria, isolating the intricate logic, and structuring it into a documented proposal for human oversight.

Yes, you can check if a proposed skill duplicates existing ones before drafting, because the evaluation process explicitly ensures the new procedure does not overlap with previously captured skills.

You need human oversight for skill proposals after the procedure is evaluated and drafted, ensuring the final captured skill accurately reflects the work procedure before it is finalized for reuse.

Capturing a skill does not strictly require cross-cutting impact, but procedures demonstrating repeated execution, non-obvious complexity, and cross-cutting nature are prioritized as highly valuable for work documentation.