implementation-engineer

Name: implementation-engineer
Availability: InStock
Author: ylxmf

Implement approved Story Specs and bug fixes with traceable changes and evidence capture.

11|1|Updated Mar 3, 2026

Search Tags:#implementation #blockers #engineering #code-review #dev-process #story-spec

Ready to run

npx skills add https://github.com/ylxmf2005/AgentCorp --skill implementation-engineer-ylxmf2005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-engineer
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/implementation-engineer
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill implementation-engineer-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates a disciplined approach to turning approved Story Specs or bug diagnoses into concrete, verifiable code changes, ensuring scope, traceability, and auditability.

Core Features & Use Cases

End-to-end guidance for implementing a story or bugfix from plan to handoff, including traceable changes, evidence collection, and blocker handling.
Diff-minimization discipline: reuse existing code, avoid scope creep, and document deviations with clear rationale.
Verification readiness: prepare implementation-result artifacts, tests, and thorough notes for code review.

Quick Start

Instruct the team to implement the approved story in the repository, then document changes and evidence in the implementation-result artifact.

Frequently Asked Questions about implementation-engineer

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

FAQPage Schema

How do I implement an approved story spec with verifiable code changes?▼

To implement an approved story spec, this Skill coordinates end-to-end guidance from planning to handoff, enforcing diff-minimization, evidence capture, and thorough documentation for code review readiness.

What is the best way to minimize code diffs when implementing a bug fix?▼

Minimizing code diffs during a bug fix requires reusing existing code, avoiding scope creep, and documenting any deviations with clear rationale to maintain strict traceability and auditability across the development process.

How do I handle blockers during the software implementation process?▼

Handling blockers during the implementation process involves capturing them systematically within the implementation-result artifact, ensuring traceable documentation of issues encountered while turning approved specs into code changes.

What artifacts do I need for a code review after implementing a story?▼

For a code review after story implementation, you need to prepare implementation-result artifacts, comprehensive tests, and detailed notes that capture evidence and document the verifiable code changes made.

Does this implementation workflow support traceable changes for software delivery projects?▼

Yes, this implementation workflow supports software delivery projects by providing strict diff-minimization and evidence capture across plan, code, and review phases to ensure scope compliance, traceability, and auditability.