Write a skill outlining your expectations of the code, put that skill into the pipeline, so that it can be included within your workflow. Webdev here, but curr

Write a skill outlining your expectations of the code, put that skill into the pipeline, so that it can be included within your workflow. Webdev here, but currently I have: - a skill where I outlined how the architecture of the system should look like, with guards (static analysis, architecture tests, linting) confirming that the code it generates adheres to standards - a skill that tells it how tests should look like (use generators, write both feature / unit tests) - a skill that tells it to generate docs from the code in a form of acceptance criteria (Given / When / Then) - a skill that tells it to generate frontend uat tests + accompanying backend seeders given the AC - a skill that tells it to verify that ticket objectives match what was delivered At this point I still need to guide it to move task from one stage to the other (coding, testing, verification that indeed what was coded adheres to what was required), but I believe that these dynamic workflows can automate this work as well.