implement-feature

Translate written specs into production-ready code with test-driven workflows.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/saboteur-labs/ai-workflows --skill implement-feature-saboteur-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/saboteur-labs/ai-workflows/tree/main/skills/coding/implement-feature
Command: npx skills add https://github.com/saboteur-labs/ai-workflows --skill implement-feature-saboteur-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate a written spec, task description, or acceptance criteria into production-ready code that aligns with project conventions and delivery timelines.

Core Features & Use Cases

  • Plan, implement, and deliver a well-scoped feature from a provided spec or description.
  • Follow an incremental, test-driven workflow with explicit acceptance criteria.
  • Adapt to ambiguous requirements by documenting assumptions and seeking clarifications when needed.

Quick Start

Plan the feature from the spec and begin implementing with tests.

Frequently Asked Questions about implement-feature

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

FAQPage Schema
How do I implement a feature from a spec?

To implement a feature from a spec, translate the written specification and acceptance criteria into production-ready code using an incremental, test-driven workflow. This ensures the delivered feature aligns with project conventions and satisfies the documented requirements.

What is the best way to turn acceptance criteria into production-ready code?

The best way to turn acceptance criteria into production-ready code is following an incremental, test-driven workflow. This approach systematically satisfies each criterion through planned implementation and QA validation, adapting to ambiguous requirements by documenting assumptions.

How do I handle ambiguous requirements when implementing a feature?

When handling ambiguous requirements during feature implementation, document your assumptions and actively seek clarifications. This ensures the generated production-ready code remains aligned with project conventions and the underlying task description despite initial vagueness.

Does test-driven feature implementation require integration and QA validation?

Yes, test-driven feature implementation includes integration and QA validation. Translating a written spec into production-ready code requires applying testing aligned to project conventions throughout the incremental implementation process to ensure delivery timelines are met.

Can I plan and build a well-scoped feature incrementally from a task description?

Yes, you can plan and build a well-scoped feature incrementally from a task description. This process translates the provided description into production-ready code, explicitly following test-driven workflows and acceptance criteria to ensure proper delivery.