Review a teammate role before publishing it

A published role should explain what it does, what it needs and what it cannot guarantee. Review its instructions as downloadable public content.

Work through these checks

1. Scope

name a repeatable deliverable. Record the evidence or the unresolved question before moving on.

2. Inputs

list required files and tools. Record the evidence or the unresolved question before moving on.

3. Examples

use safe, clearly illustrative material. Record the evidence or the unresolved question before moving on.

4. Rights

confirm permission for included text and resources. Record the evidence or the unresolved question before moving on.

5. Preview

inspect every public field and target server. Record the evidence or the unresolved question before moving on.

Put the checklist to work

Replace a private client brief with a small fictional example before testing the exported package.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

Automatic exclusion of account credentials does not remove secrets you pasted into the working guide.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.