intent-finish

To automate intent completion, this Skill marks a development intent as complete by generating a concise summary, capturing code changes via git diff, and updating the task status. It systematically handles the documentation required for finished features.

The best way to archive completed development tasks is using a structured intent workflow that automatically updates the status to "Completed" and moves the intent files to an archive directory within your git repository.

Yes, you need a predefined intent directory structure for status management. The Skill relies on this existing structure to locate your active intents, update their status, and move them to the archive upon completion.

Yes, you can document code changes for finished features without manual git commands. The Skill requires git and automatically captures the code diff for the completed intent, appending it directly to the generated documentation.

No, this workflow does not work without git installed. The Skill explicitly requires git for diff generation to capture the code changes needed for the automated intent completion documentation.

You should use an automated intent completion tool when your software engineering workflow requires structured task completion and documentation. It is ideal for ensuring consistent summaries and code diffs are archived immediately after finishing a feature.