teaonly

The principle is this.

My next step is to design the recipe to be hot-loadable. The goal is to achieve self-evolving, optimizing the recipe independently without changing the DAG. This ability to perform local optimization is something Markdown lacks, but Makefiles can.

What I did here was to rewrite SKILL.md in Makefile style, using a DAG structure and omitting the text describing the process. So this should be considered a pseudo-Makefile; writing a SKILL using the Makefile approach is a very natural method.

The core idea of this project is to use Makefiles to style SKILL documentation, leveraging Makefiles' built-in DAG functionality and a defined syntax. The advantages are as follows:

1. It reduces the token consumption of the original MD format;

2. SKILLs are easier to read and more suitable for AI use because the inherent DAG is a Plane Mode;

3. Makefiles are ideal for auditing (git tracing, call statistics), providing a solid fundation for future self-evolving enginering.