implementing-python-files

Automate Python file implementations using a 4-step TDD workflow.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill implementing-python-files-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-python-files
Source: https://github.com/outcomeeng/claude/tree/main/plugins/python/skills/implementing-python-files
Command: npx skills add https://github.com/outcomeeng/claude --skill implementing-python-files-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File-focused Python implementation skill enforces a disciplined 4-step TDD workflow to drive targeted changes for one or more files.

Core Features & Use Cases

  • Sequential TDD guidance: write tests, review tests, implement code, review implementation for each file.
  • Multi-file support: handle one or more targets in a controlled, traceable sequence.
  • Workflow orchestration: integrates with in-repo commands to coordinate tests and reviews before coding.

Quick Start

Supply one or more file paths to implement and the skill will guide you through tests, review, and implementation steps.

Frequently Asked Questions about implementing-python-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Python file implementation using a TDD workflow?

Automate Python file implementation by supplying target file paths to trigger a strict 4-step TDD workflow: write tests, review tests, implement code, then review the implementation for each file.

Can I implement multiple Python files in a single traceable sequence?

Yes, you can implement multiple Python files in a single run. The workflow processes one or more target files sequentially, ensuring traceable progress and verifiable results across the entire sequence.

What's the best way to ensure test coverage before writing new Python code?

The best way to ensure test coverage is using a strict TDD workflow that mandates writing and reviewing tests before any implementation code is generated for the target Python files.

How do I coordinate testing and code reviews for targeted Python file changes?

Coordinate testing and reviews by integrating with in-repo commands like /testing-python, /reviewing-python-tests, /coding-python, and /reviewing-python to drive verifiable progress for file-level changes.

Does this TDD workflow support updating existing Python files or only creating new ones?

This TDD workflow supports both creating new Python files and updating existing ones, applying precise file-level changes with coordinated tests and reviews throughout the implementation process.