CW-301a · Module 1
Meta Plugin Deep Dive
4 min read
Good news, everyone! You already know the meta plugin exists from the CW-101 course. You know it takes a plain-English workflow description and generates a plugin with skills, commands, and connectors. What you do not know — because we did not cover it — is how to push the meta plugin past its defaults into genuinely powerful custom tooling.
The default meta plugin behavior is conservative. You describe a workflow, it generates a plugin with one skill, one or two commands, and a connector suggestion. That is the starting point, not the destination. Advanced usage involves multi-workflow plugins — a single plugin that contains 4-6 related skills, each covering a different phase of a business process. Instead of a "client onboarding" skill, you create a "client lifecycle" plugin with skills for onboarding, project kickoff, milestone review, deliverable QA, project close, and post-project follow-up.
The iteration strategy is what separates a functional plugin from a production plugin. Version 1 captures your initial workflow description. It works, roughly. Then you use it for a week and discover every gap. The onboarding skill missed the step where you check for conflicts of interest. The project kickoff skill assumed a single decision-maker but your enterprise clients have buying committees. The deliverable QA skill does not know about your firm's specific formatting standards.
Each gap is a refinement. Feed the corrections back to the meta plugin: "Update the onboarding skill to include a conflicts-of-interest check after the intake questionnaire. Update the kickoff skill to ask how many stakeholders are involved in the decision. Update the QA skill to enforce 12pt body text, branded headers, and the standard disclaimer footer." The meta plugin regenerates. Version 2 is better. Version 3 is production-grade. This cycle is the fundamentals in action — compounding improvement through disciplined iteration.
- 1. Describe Multiple Related Workflows Instead of describing one workflow, describe the full business process with all its phases. "Client lifecycle management includes: intake, onboarding, project kickoff, weekly check-ins, deliverable review, project close, and retention follow-up." The meta plugin will organize these into a coherent multi-skill plugin.
- 2. Specify Decision Points For each workflow, identify where human judgment is required. "After the intake questionnaire, a human reviews for conflicts of interest before proceeding." The meta plugin encodes these as pause points in the generated skills.
- 3. Run for One Week Use the plugin in real work for at least a week. Keep a running list of gaps, incorrect assumptions, and missing steps. Do not fix them one at a time — batch corrections for a single meta plugin update.
- 4. Regenerate and Repeat Feed all corrections to the meta plugin in one session. Let it regenerate the full plugin with improvements. Test the new version. Repeat for Version 3. After three cycles, the plugin should be stable enough for team deployment.