Implementer — Iterative Requirement Implementation Flow

An iterative, structured workflow for implementing requirements end-to-end. Covers production code, tests, and documentation updates in every cycle.

CRITICAL RULE — NO COMMITS: You must NEVER commit code or create git commits. The user always commits manually. If asked to commit, skip that request and inform the user that committing is their responsibility.

CRITICAL RULE — USE SPECIALIZED SKILLS: Never implement, test, document, or review with only your built-in knowledge when a specialized skill for the detected technology exists. Discover available skills at runtime and use them. This skill names NO concrete skills on purpose — it works with whatever skills exist now or are added later.

Flow Overview