Implementation phase procedures - fix protocol, code writing rules, review issue handling

Implement workflow plans while resolving numbered review issues with fix-by-ID reports.

1|1|Updated Feb 1, 2026

Search Tags:#workflow orchestration #code changes #API verification #self verification #implementation phase #review issue fixing #fix-by-id

Ready to run

npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill implementation-phase-procedures-fix-protocol-code-writing-rules-review-issue-handling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Implementation phase procedures - fix protocol, code writing rules, review issue handling
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/phases/implementation
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill implementation-phase-procedures-fix-protocol-code-writing-rules-review-issue-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps agents complete the implementation phase by turning a workflow plan into real code changes while ensuring every numbered review issue is addressed and re-verified.

Core Features & Use Cases

Plan-to-code execution: Implements steps in order based on the workflow state file, writes files immediately after changes, and reports all modified/created files.
Mandatory review fix protocol: Resolves or disputes every required [ISSUE-N] with a fix-by-ID format, including line-level diagnosis and self-verification.
Optional skill loading for conventions: Attempts to load recommended code-convention skills (e.g., PHP/Laravel) when the codebase indicates they exist, without failing if unavailable.
Library API verification guardrails: Verifies external library/API signatures against available MCP context or declared dependency versions before using APIs.

Quick Start

Use the implementation phase skill to implement the current workflow plan and respond to any review issues using the required FIXED or DISPUTE reporting format.

Frequently Asked Questions about Implementation phase procedures - fix protocol, code writing rules, review issue handling

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

FAQPage Schema

How do I enforce a fix-by-id protocol for code review issues in a staged workflow?▼

To enforce a fix-by-id protocol, you must resolve or formally dispute every numbered `[ISSUE-N]` from the review feedback. This requires providing a fix-by-ID format with line-level diagnosis and self-verification to ensure every issue is addressed.

What is the best way to implement a workflow plan into code changes step by step?▼

The best way to implement a workflow plan is to execute steps sequentially based on a workflow state file, write files immediately after changes, and report all modified or created files to ensure reliable plan-to-code execution.

How do I verify external library and API signatures before using them in my code?▼

To verify external library and API signatures, check them against available MCP context or declared dependency versions before use. This acts as a guardrail to prevent errors from unverified API calls during implementation.

Can I load code convention skills automatically when implementing workflow changes?▼

Yes, you can attempt to load recommended code-convention skills, such as PHP or Laravel, when the codebase indicates they exist. The process will not fail if the recommended convention skills are unavailable.

How do I formally dispute a numbered review issue during the implementation phase?▼

To formally dispute a numbered review issue, you must use the required DISPUTE reporting format instead of the FIXED format. This allows you to systematically handle review feedback by either resolving or contesting each `[ISSUE-N]`.

What should I do if code changes are not being written immediately during workflow orchestration?▼

If code changes are not written immediately, the implementation phase is failing its core execution rule. You must ensure the workflow enforces writing files immediately after changes and reports all modified files to maintain state integrity.