summarize-work
Write a detailed summary at the bottom of the spec/plan document of what was done, how, and why, and files worked on during the implementation.
The structure should look like this:
EXAMPLE of a single phase implementation summary:
Phase 1 Implementation Summary (Completed)
-
What was done
-
How it was done
-
Why it was done|
-
Files worked on
EXAMPLE of a multi phase implementation summary:
Phase 1-4 Implementation Summary (Completed)
-
What was done
-
How it was done
-
Why it was done
-
Files worked on
More from ferueda/agent-skills
review-spec
Review a spec document against codebase reality, identifying gaps and ensuring sound, robust implementations.
57research-codebase
Research codebase comprehensively using parallel sub-agents. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
46ask-questions
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
27create-plan
Create detailed implementation plans with thorough research and iteration. Use when the user asks to build a feature, create a plan, or specifically invokes this skill.
15implement-plan
Implement a spec document phase-by-phase, writing robust idiomatic code that follows codebase patterns.
15