learn

To document debugging workarounds, you can capture the non-obvious knowledge into a reusable skill file. This codifies the problem, context, solution, and verification steps so the specific workflow is preserved and avoids duplication of effort.

The best way to capture multi-step workflows for workflow automation is to extract the process into a structured skill file. This evaluates the learning, checks for existing skills, and creates a new reusable file with specific sections like Example and References.

When creating a new skill for knowledge capture, the file should include specific sections: Problem, Context, Solution, Verification, Example, and References. This structure ensures the non-obvious knowledge is codified logically for future reuse.

Yes, the knowledge capture process checks for existing skills before creating a new one. This prevents duplication of effort and ensures that only new, non-obvious insights and unique workarounds are codified as separate reusable files.

You should use a structured skill file for reusability when standard documentation is insufficient for complex multi-step workflows. It is designed to extract non-obvious knowledge, perform quality checks, and codify discoveries that are not readily available in typical documentation.