Chapter 1 · Meet BasilAOS — Your New Work Partner

1.10 Choose Resources and Deliverables for Your Task

Chapter 1 ends here. First, a recap of what is now in place:

  • Four resource types: Skill for method, Work for combination, Connector for the channel, App (Library / Base) for material and data
  • Two mechanisms: Memory remembers you, the workspace remembers the work

That leaves a practical question: which parts of the work do these capabilities actually cover?

Three Kinds of Work That Fit

KindCharacteristicExample
Clear inputs and acceptance criteriaMaterial available, format fixed, correctness checkableTranslation, summary, format conversion, data cleaning
Multiple steps with a stable sequenceThe same process runs repeatedlyEmail triage and follow-up, weekly reports, competitor sweeps
Aggregation across materialSources scattered, manual assembly is slowContract comparison, multi-table roll-up, document search

The common thread is two conditions: the goal can be described, and the result can be checked. When both hold, the task fits.

Choose Resources for the Task

TaskResourcesDeliverable
Compare contract clausesStandard terms and the supplier contract in LibraryClause differences and negotiation items
Prepare publishing materialBrand assets, content templates, and a writing SkillChannel-specific copy and files
Organize files in bulkA Library folder and naming rulesA categorization plan and organized files
Summarize business dataBase tables and metric definitionsAnalysis tables, charts, and a summary

Specify Inputs and Deliverables

Name the files, tables, or folders in the task description, then state the output format, fields, and destination. For example:

Read the meeting notes in Library and generate Markdown meeting minutes and an action-item table. Include the action, owner, due date, and status, and save the files in this task's outputs.

For practice adding requirements in the same conversation, see 1.3 Review the Deliverable.

Next: Chapter 2

Chapter 1 covered how to use the resources that already exist. Chapter 2 covers how to turn one result into a system:

  • Workspaces and automation: let a flow run on its own schedule
  • Three lessons on Skill: understand the structure, create one, iterate on it
  • Work design: assemble several Skills into one complete business chain
  • Library and Base in depth: turn files and data into reusable assets

If a task is waiting on your desk right now, the office scenarios in Chapter 3 are there to look up. If you want this to work for you over the long term, Chapter 2 is the main line.