implement-task

Implement development tasks by writing failing tests before minimal code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/EtroxTaran/conductor --skill implement-task-etroxtaran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-task
Source: https://github.com/EtroxTaran/conductor/tree/main/collection/skills/implement-task
Command: npx skills add https://github.com/EtroxTaran/conductor --skill implement-task-etroxtaran

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of implementing new features or bug fixes by enforcing a Test-Driven Development (TDD) approach, ensuring code quality and maintainability.

Core Features & Use Cases

  • TDD Workflow: Guides the user through writing failing tests before implementing the actual code.
  • Iterative Development: Encourages writing minimal code to pass tests, preventing over-engineering.
  • Use Case: When tasked with adding a new user authentication module, this skill will ensure robust test coverage from the outset, leading to a more reliable and secure feature.

Quick Start

Use the implement-task skill to add a new user profile update functionality, starting with writing the relevant tests.

Frequently Asked Questions about implement-task

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

FAQPage Schema
How do I implement code features using a test-driven development workflow?

Yes, test-driven development supports both Python and JavaScript/TypeScript projects. You can implement features across these languages by defining acceptance criteria and file scopes, then writing failing tests followed by the minimal code required to pass them.

What is the best way to prevent over-engineering when adding new code features?

To prevent over-engineering, use an iterative test-driven development workflow that encourages writing only the minimal code required to pass predefined failing tests. This ensures your software implementation stays focused, maintainable, and strictly aligned with acceptance criteria.

Do I need defined acceptance criteria before starting test-driven development?

Yes, defined acceptance criteria are necessary for test-driven development because they dictate exactly what the initial failing tests must validate. Having clear file scopes and criteria ensures the subsequent minimal code implementation directly meets the required functionality.

How does writing failing tests first improve software maintainability?

Writing failing tests first improves software maintainability by enforcing strict test coverage from the outset of development. This test-driven approach ensures every piece of implemented code has a validating test, leading to more reliable and robust feature additions.

Can I use this test-driven development approach for fixing existing bugs?

Yes, you can apply the test-driven development workflow to bug fixes by first writing a failing test that reproduces the specific bug, then implementing the minimal code correction to make that test pass, ensuring the fix is verified and maintainable.