scoutlisted

# Scout ## Activation Contract - A RefactorCh Project Profile is missing for a known repository. - A human or caller explicitly requests a Project Profile refresh. - Repository-level structure, build tooling, test commands, source layout, or major framework/runtime versions changed. - Existing Project Profile data is too incomplete to support a setup handoff. Do not use this skill for target-specific refactor planning, gate review, execution, auditing, workflow routing, future-phase selection, or generic code analysis. ## Responsibility Scout owns only reusable RefactorCh Project Profile creation and refresh. Callers own deciding when to invoke Scout, providing or implying repository identity, and deciding what to do after Scout returns. ## Required Context Minimum context is `project`, `repo_path`, `repo_key`, and `profile_topic_key`. If explicit input is absent, derive safe values from available context such as the active Engram project, working directory, repository name, or existing Project Profile topic. ## Hard Rules - This skill owns Project Profile creation and refresh workflow only. - Use `refactorch-phases` for shared topic keys, Engram protocol, artifact references, and shared envelopes; do not copy those conventions here. - Inspect only bounded repository-level evidence: structure, configuration, documentation, and caller-provided command hints. - Do not read broad source context, execute shell/build/test commands, edit files, fetch web content, delegate,