implementing-python-files

To implement Python code with a test-driven workflow, you analyze context, write tests, review tests, implement the code, and review results. This process guarantees changes meet expectations through tests before coding begins.

File-focused Python coding implements changes on a per-file basis for adding features or fixing defects. You need this approach when applying targeted modifications to specific files within a Python project while ensuring adherence to existing interfaces.

To add features or fix defects in specific Python files, invoke the skill with one or more file paths like src/mymodule/handler.py. This triggers a deterministic process that analyzes context, writes tests, implements code, and reviews results.

Yes, this test-driven Python workflow orchestrates an integrated skill chain. It utilizes /testing-python, /reviewing-python-tests, /coding-python, and /reviewing-python skills to deliver deterministic progress on complex per-file changes.

Yes, you can implement multiple Python files in a single operation by invoking the skill with multiple file paths. The workflow applies the same test-driven process to each specified file to ensure overall code quality and correctness.

The limitation of file-focused Python implementation is that it operates on a per-file basis, meaning it is designed for targeted tasks like adding features or fixing defects rather than broad, project-wide architectural refactoring without specified file paths.