Package the terminal workflow without personal-machine assumptions.
1. Reproducible commands
Use repository scripts and the project’s Gradle wrapper where appropriate. Document required tools and avoid hidden aliases or absolute personal paths.
2. CI differences
Headless environments may lack devices, credentials or interactive prompts. Mark which checks can run in CI and which require a controlled device environment.
3. Useful reporting
Report the requested behavior, commands that establish it, failures and unverified areas. A long command transcript is less useful than a clear evidence-backed result.
Worked scenario
A teammate runs the workflow on a clean machine and sees a clear missing-SDK precondition rather than a confusing application error.
Apply it
Write a portable verification script and a short handoff document with expected outputs.
Check your understanding
The workflow either produces evidence or stops with an actionable explanation. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.