Skip to content
Community open-source Web · 0.2.1 release docs · 0.2.1Content reviewed: 2026-10-18View Markdown

4.1 Content team: from materials to a first draft ​

Practice with fictional materials, without connecting to an external business system. Check the model's facts and conclusions. Before using marketplace resources, review the requirements on their detail pages.

Prepare ​

Connect a model. Create research, writing, and review employees in the same business area or in General work, then add them to the same group. Each employee only needs the materials for this exercise. Without authorization for external tools, do not assume it can search or write to an external system.

Sample materials ​

text
The product “Desktop Notes” supports local storage, tags, and Markdown export. Team sharing is still planned. The intended audience is independent consultants. No price is provided.

1. Define the first round of work ​

Share the materials in the group and mention the first employee:

text
Extract confirmed facts and missing information. Keep the supporting evidence from the materials for each item. If information is missing, list questions instead of guessing.
Do not invent prices, user counts, or claims that a feature is available.

If you need formal tracking, create a linked task and check its owner and scope. Then review whether the resulting facts are complete.

2. Hand over and review ​

After checking the first result, pass the confirmed content to the second employee:

text
Write a title and a 300-character first draft. Use only confirmed materials and label inferences separately.

Then pass it to the review employee:

text
Check every claim and its source. Go beyond polishing the writing: identify where the source and conclusion do not agree.

3. Verify the results ​

Expected deliverables include a fact list, a working draft, and review comments. Check the owner, sources, unresolved questions, and task records for each deliverable.

Do not invent prices, user counts, or claims that a feature is available. If you later connect real tools, separately verify their scope, keys or authorizations, and approval requirements. This exercise grants no permission for real external actions.

Reuse the workflow ​

Choose Save as a method or Save as a plan on a result; it is saved after you send it, and a plan stays paused until you enable it. Configure an automation only after the recurring input source and acceptance criteria are clear. Keep the handoffs manual for the first exercise so that unverified steps do not run automatically in sequence.