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

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.

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.

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.

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.

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]`.

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.