Content roster audit: evaluate roles by their deliverables

Inventory coordination, judgment, research, growth, production and monitoring, then review overlaps and missing artifacts.

The source describes a layered roster, file handoffs and gradual expansion. This role card audits the roster without one-click installation or deleting roles.

Verification status

Source reading and media coverage are listed below. This site has not executed the live workflow. Fixtures, fields and prompts here are independent exercises, not the author’s results.

Scenario and input

Synthetic roster: researchers A and B collect the same brief; writer C has no output directory.

1. Inventory deliverables

Record known inputs, artifacts and ownership, marking unavailable evidence rather than inferring capability from titles.

2. Find overlaps and breaks

Compare research scope, topic ownership and review roles, marking duplicate collection and missing or competing owners.

3. Separate execution and acceptance

Identify drafting, factual checking and publication approval, keeping separate records even if one person fills several roles.

4. Propose the smallest change

Prefer a skill or handoff adjustment and document the routines and files affected by any proposed roster change.

5. Retest one input path

Retest one research-to-draft path before adding monitoring; quiet reporting still leaves checking costs.

A synthetic acceptance fixture

roster-review.csv: role, input, artifact, reviewer, overlap, proposal. Recommend consolidation after inspecting rules and routines rather than deleting Bots.

Copyable task brief

Copy template

Use the synthetic fixture to prepare the deliverable for Content roster audit: evaluate roles by their deliverables. Do not connect real services yet.
Input: Synthetic roster: researchers A and B collect the same brief; writer C has no output directory.
Requirements:
1. Record known inputs, artifacts and ownership, marking unavailable evidence rather than inferring capability from titles.
2. Compare research scope, topic ownership and review roles, marking duplicate collection and missing or competing owners.
3. Identify drafting, factual checking and publication approval, keeping separate records even if one person fills several roles.
4. Prefer a skill or handoff adjustment and document the routines and files affected by any proposed roster change.
5. Retest one research-to-draft path before adding monitoring; quiet reporting still leaves checking costs.
Return itemized records, evidence locations, unknowns and next steps, marking unperformed actions explicitly.
Do not install tools, change access, purchase, publish, create Bots or schedule work in this pass.

Acceptance and review

Each proposal cites an artifact or a gap, without automatically installing templates, deleting Bots or changing schedules.

Copy template

Review the artifacts without taking external actions.
Acceptance: Each proposal cites an artifact or a gap, without automatically installing templates, deleting Bots or changing schedules.
Separate pass, fail, untested and evidence; distinguish synthetic fixtures from live results.
Stop on missing sources, permissions or uncertain outcomes and list the required evidence.
Propose one next step with a recovery plan and wait for confirmation.

Sources and applicability

Original article: @Jackywxsz; published 2026-10-10.

Index-to-source mapping: strong content match.

The collector reports viewing 16 images; 0 videos remain unwatched. Images identify sender, recipient, artifact and reviewer, keeping topic, author input, final copy and publication with the owner. Public installation packages were not run.

Prices, interfaces and menus change. Check unresolved conditions against the actual account and current official documentation.

See the rewrite and verification map for all 24 sources