Business Policy Refactoring

Start only through an explicit /tk-refactor-policy, $tk-refactor-policy, or host skill selection. Never invoke automatically from tk-review, tk-prep, tk-audit, a generic refactoring request, or the mere presence of complex conditionals.

This skill is read-only. Inspect the requested repository scope and propose refactoring candidates, but do not edit source, tests, configuration, Git state, issues, PRs, ledgers, or durable artifacts. Do not dispatch another skill. If the user later wants an accepted candidate implemented, tk-prep may own that separate execution request.

Target

Look for logic whose primary purpose is to decide a business policy, eligibility, permission, availability, approval, visibility, pricing rule, state transition guard, or similar outcome from multiple facts. Boolean-returning code is a strong signal, not a requirement.