engineer

Implement planned software changes with tests and build validation.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/ddobrin/plan-skills --skill engineer-ddobrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/plan/skills/engineer
Command: npx skills add https://github.com/ddobrin/plan-skills --skill engineer-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an approved implementation plan into tested, maintainable code while preventing scope creep, unverified changes, and broken handoffs.

Core Features & Use Cases

  • Plan-Driven Implementation: Executes tasks in the prescribed order and tracks progress directly in the plan file.
  • Test-Driven Development: Uses characterization tests, red-green-refactor cycles, incremental changes, and frequent verification.
  • Quality and Safety Controls: Enforces build checks, explicit blocker handling, strict scope boundaries, and preservation of file history during moves or renames.
  • Use Case: Give the Skill a feature plan and repository access so it can implement each step, add or update tests, verify the build, and mark completed work without committing changes.

Quick Start

Use the engineer skill with the path to an approved plan file to implement its steps, verify the tests, and update progress.

Frequently Asked Questions about engineer

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

FAQPage Schema
How do I implement planned software changes with test-driven development without scope creep?

Test-driven development implements planned software changes by applying red-green-refactor cycles and frequent verification, ensuring each step produces tested code while tracking progress directly in the plan file to prevent scope creep.

What is the best way to refactor legacy code while preserving file history during moves?

Refactoring legacy code uses characterization tests to capture existing behavior before changes, applying incremental modifications validated by build checks. File history is preserved during moves or renames by using git mv without committing changes.

Do I need an approved implementation plan before starting test-first software implementation?

Yes, an approved implementation plan is required. Test-first software implementation executes tasks in the prescribed order from the plan file, tracking completed work and verifying builds to deliver maintainable code without committing changes.

Can I use incremental repository maintenance for bug fixes without committing changes?

Incremental repository maintenance supports bug fixes through test-first verification and build validation, updating progress without committing changes. It performs git mv file moves and code updates while leaving version control operations to the user.

How does build validation work during feature development with frequent verification?

Build validation enforces quality controls by running checks after each incremental change during feature development. Frequent verification ensures tests pass and builds succeed, requiring explicit blocker handling before proceeding to the next planned task.