CW-201a · Module 3
Custom Workflow Assembly
3 min read
Plugins provide domain knowledge. Skills provide workflow memory. Manual prompts provide the customization layer. A custom workflow combines all three into a pipeline tailored to your specific business. No two businesses need exactly the same workflow, and that is the point — the assembly is the value.
Consider a consulting firm's pre-meeting preparation workflow. The sales plugin researches the prospect company. A custom skill formats the research into the firm's standard meeting brief template. A manual prompt adds context: "This prospect was referred by Client X, so emphasize our work with Client X in the brief." Three components — plugin, skill, manual prompt — each contributing something the others cannot.
The assembly process is iterative. Start with the manual workflow you already do. What steps do you follow? What data do you gather? What templates do you use? What quality checks do you run? Document that workflow in plain language. Then identify which steps map to existing plugins, which steps should become skills, and which steps remain manual prompts.
Not everything needs to be automated. Some steps require human judgment that no plugin or skill can replace. The goal is not full automation — it is a hybrid workflow where the automated steps handle the 80% of repeatable work and the human steps handle the 20% of judgment calls. The workflow should make you faster, not replace you.
Do This
- Map your existing manual workflow before trying to automate it
- Use plugins for domain expertise, skills for repeatable procedures, manual prompts for context
- Start with the highest-ROI workflow — the one you do most often
- Accept that some steps will remain manual — human judgment is part of the workflow
Avoid This
- Try to automate everything at once — start with one workflow and expand
- Build custom solutions when a plugin already covers the domain
- Skip the documentation step — you cannot automate what you have not described
- Assume the first version of the workflow is the final version — it will evolve