python-test-architecturelisted

# Outcome Produce a concrete, reviewable result for the workflow below without overstating what was observed, executed, or verified. ## Compatibility Portable across Claude Code, Codex, and OpenCode. The optional inventory helper requires Python 3.11, parses test files without importing them, and uses no network. Framework-specific execution remains the repository's responsibility. ## Use this skill when - A Python project needs a new or substantially revised test strategy. - A repository-wide strategy also needs a focused CLI test matrix; also use `python-cli-testing`. - A package-layout or import-boundary migration also requires unit, integration, or package-install tests to be redesigned; also use `python-project-layout`. - Tests are slow, flaky, order-dependent, over-mocked, or poorly mapped to risk. - Fixture scope, test data, markers, parameterization, or CI selection needs review. - The team needs to choose unit, contract, integration, and end-to-end boundaries. ## Do not use this skill when - The task is package discovery, `src/` layout, or build artifacts without test-architecture changes; use `python-project-layout`. - The task is only command-line stdout, stderr, exit codes, or shell invocation; use `python-cli-testing`. - The request is to diagnose a single application exception rather than the test architecture. ## Inputs Inspect or obtain: - System behaviors, critical journeys, failure impact, and known incident history. - Current tests, fixtur