implement

To convert a plan file into working code, you provide the plan file path and the skill reads it to apply changes directly to source files file by file. It supports feature implementations, fixes, and refactors.

Automated plan-to-code execution validates changes by running an appropriate type checker after each edit to ensure correctness. It applies concrete changes sequentially and never enters plan mode.

Yes, you can apply plan-driven changes to multiple source files sequentially. The skill operates file by file, applying the described changes directly to each source file in your software project.

The best way to automate code implementation from a written plan is to use a skill that avoids plan mode and applies concrete changes directly. It reads your plan file path and executes edits file by file with immediate type checking.

No, you do not need to enter plan mode to execute file-by-file code changes. The skill never operates in plan mode and instead always applies concrete changes directly to source files one by one.

Software project changes that can be automated from a plan file include feature implementations, fixes, and refactors. The skill applies these described changes directly to source files sequentially.