Skills, playbooks and project records
Your agent needs both the ability to do something and a reason to do it. Egbe keeps those responsibilities distinct so the same capabilities can support different businesses and ways of working.
Four parts of useful context
Section titled “Four parts of useful context”Skills describe capabilities. They explain how to use a service, its inputs, access requirements, technical checks and recovery behavior. A payments skill can explain how to implement a purchase. An analytics skill can explain how to collect and inspect events.
Playbooks describe methods. They help your agent approach questions, compare choices and judge results. The Product playbook covers value, offers, experience, delivery and evaluation. Market and acquisition covers customer evidence, test selection, preparation and interpretation.
Plans describe a particular commitment. A plan holds this task’s result, scope, owner, budget, timing and accepted choices. For an experiment, it also preserves the question and criteria established before execution.
Results describe what happened. They retain the evidence, its limitations and the interpretation that supports the next decision. Completing an implementation and observing a customer benefit are separate results worth recording clearly.
An example: changing an offer
Section titled “An example: changing an offer”Suppose you are considering charging per completed report. The offer method helps examine why customers would pay, what they receive and the obligations you take on. The payments skill establishes how the agreed model can work. The implementation plan names the purchased right and release scope. The results show whether the payment and delivery journey works, then what customers actually choose.
These records can stay concise. Existing requirements, notes and evidence are useful inputs; each task does not need a fresh document collection.
Adapt the method deliberately
Section titled “Adapt the method deliberately”Project playbooks are editable. You might adopt a preference to review an acquisition proposal after seeing complete sample materials, or require a particular quality check for your product’s output. Ask your agent to preserve the reason and the conditions where that preference applies.
A one-time exception belongs in the task’s plan. A standing method changes when you adopt it for future work. Updated Egbe methods provide comparison material; your agent should explain relevant proposals and preserve local adaptations as you review them.
For this test, use the audience we already chose. Afterward, help me decide whether any lesson should change our ongoing acquisition method. Keep this test’s original criteria and results intact.
Expect the agent to identify the applicable method, reuse existing evidence and separate a proposed adaptation from an accepted change.
Project work is kept together under egbe-docs/ in your product repository. Protect sensitive records and exclude this working material from public builds. See Continuity between sessions for practical handoffs.