Build Your First Capability Template

Level 2 · Course 15

By now your agent has rules, memory, trigger words, context control, and a boot chain. That is useful — but it is still fragile if every new capability is invented from scratch. One task gets a checklist. Another gets a prompt. A third gets buried in a project note. Six sessions later your agent knows the capability exists somewhere, but cannot reliably find it or run it.

This course gives you the container. A capability template is one self-contained file that tells the agent what the capability is, when it triggers, what tools it uses, what sequence it follows, what it must never do, how it logs results, and how to test that it survived a fresh session. It is not a plugin. It is not code. It is a repeatable operating manual written for the next instance.

Real examples from the JKE ecosystem show the pattern: an Update Shield protocol that snapshots config before upgrades, rolls back on failure, and survives across platform versions. A Sun Run playbook that defines bounded sprints with mandatory QA gates and a hard production lock. A Focus Group methodology that controls context variables, picks profiles, and extracts patterns. All three began as the same structure you are about to build: trigger, purpose, sequence, hard stops, survival test. After this course, your repeatable work stops becoming scattered notes. It becomes doors your agent can find again.

What a Template Looks Like

Here is a simple one. A hypothetical operator — a small business owner with five active clients — sends a status update every Friday. She described the task to her agent three times before realizing it should be a template.

When your agent writes this file, you get a markdown file in your workspace — named, clean, in a known folder. Next session, fresh or loaded, the agent finds it by name. It doesn't improvise. It runs the template.

You decide: what's the first capability you'd template? Pick the task you describe to your agent most often. That's the one.