python-project-workflow

Python Project Workflow

Apply a preservation-first workflow to Python project setup, tooling, CI, packaging, compatibility, and repository-wide verification.

Framework-specific project conventions are out of scope. For Django, FastAPI, Flask, and similar frameworks, use dedicated framework guidance or preserve the project's established workflow. Do not present this generic baseline as framework-complete guidance.

Workflow

1. Inspect before advising: read repository instructions, version-control state, and project-native configuration first. Do not recommend or make changes until the current state is established from repository facts.
2. Classify the repository and the requested operation.
3. Load only the references relevant to that classification.
4. Preserve coherent local conventions unless the user explicitly requests modernization.
5. Verify with project-native gates and report actual results.

Repository Classification

Apply Existing and Automation before considering Greenfield. Missing packaging metadata or tests does not make a repository greenfield when meaningful source, scripts, documentation, or history already exist.

Signal	Classification	Guidance
Empty directory or explicit new-scaffold request	Greenfield	Load references/pyproject-template.md
Packaging metadata and coherent tooling	Existing project	Orient first, then load task-specific guidance
Python used for repository checkers or governance	Mature automation	Load references/mature-repo-preservation.md
Eval or benchmark runners	Automation with benchmarks	Also load references/eval-benchmark-hardening.md

For isolated support scripts that fall outside this skill's trigger, use repository-native instructions and focused checks. Do not infer correctness from classification alone.

Operation Modes

• Inspect or advise: use read-only discovery. Do not install dependencies, synchronize environments, generate files, or edit configuration.
• Implement: make only changes authorized by the user and preserve unrelated worktree changes.
• Verify: run already-available project-native gates first. Treat setup or dependency installation as a separate step when it is required.
• Bootstrap: create or replace project structure only for an explicit greenfield or modernization request.