implementing

Implement approved feature specifications into repository code and tests.

60|12|Updated Aug 1, 2013
One-click install
npx skills add https://github.com/vtex/front.phone --skill implementing-vtex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing
Source: https://github.com/vtex/front.phone/tree/main/.agents/skills/implementing
Command: npx skills add https://github.com/vtex/front.phone --skill implementing-vtex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an approved feature specification into a complete implementation without needing back-and-forth with a human, so the work can reliably ship to a PR.

Core Features & Use Cases

  • Autonomous spec-to-code implementation: Implements only what is described in an Approved specs/<feature-name>.md.
  • Evidence-driven completion: Generates tests from acceptance criteria, runs them, and iterates until they pass.
  • Blocked-by-design safety: If the spec is not Approved or implementation cannot be completed, it stops and files an issue instead of guessing.

Quick Start

Ask the AI to implement the approved specification file for your feature by reading specs/<feature-name>.md and delivering a feat/<feature-name> Pull Request with passing tests.

Frequently Asked Questions about implementing

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

FAQPage Schema
How do I convert an approved feature specification into a working pull request autonomously?

To convert an approved feature specification into a pull request, the Skill reads the spec file, implements the code, generates tests from acceptance criteria, and iterates until all tests pass for autonomous delivery.

How does test-driven development work during autonomous spec implementation?

Test-driven development during spec implementation requires generating tests from acceptance criteria, running them to fail first, and iterating on the code until all tests pass, ensuring evidence-driven completion before shipping a PR.

What happens if my feature specification is not marked as Approved?

If the feature specification is not marked as Approved, the autonomous implementation stops immediately and files a GitHub issue instead of guessing, enforcing strict constraints by not modifying the spec.

Do I need to manually write tests for the generated pull request?

You do not need to manually write tests, because the Skill generates tests directly from the spec's acceptance criteria and iterates through CI verification until they pass, ensuring requirements compliance autonomously.

What is the best way to handle blocked autonomous coding workflows?

To handle blocked autonomous coding workflows, the Skill terminates the process and reports blocks by filing a GitHub issue, preventing incorrect spec implementation when acceptance criteria cannot be met.

Can I modify the specification file during the code implementation process?

You cannot modify the specification file during implementation, because the Skill enforces strict constraints by reading the approved spec as-is and terminating if changes are required to proceed.