privacy-readiness

After you know what is collected (data-flow-mapping), ask whether the product handles it with restraint: collects no more than it uses, does not leak it, and does not keep it forever by accident.

Activate when

• Personal data is stored or processed, especially accounts, profiles, uploads, or messages.
• Reviewing before launch, after a data-model change, or before answering data-rights requests.
• Not to define legal retention periods (owner/legal decision).

Working alone

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: data-flow-mapping.

Inspect