Extract retrospective learnings, propose documentation updates, and archive completed plans.
npx skills add https://github.com/mattjefferson/agents --skill dev-wrapup
Please help me install this Agent Skill. Skill: dev-wrapup Source: https://github.com/mattjefferson/agents/tree/main/skills/dev-wrapup Command: npx skills add https://github.com/mattjefferson/agents --skill dev-wrapup
Capture learnings from completed plans, propose updates to project docs, and archive the plan to close the dev-work loop so future runs benefit from what was learned.
Review a completed plan and run the dev-wrapup process to extract learnings, propose documentation updates, and archive the plan.
High-intent search queries and answers about installing and using this skill.
To extract learnings from a completed plan, review the finished work to identify actionable improvements, propose updates to project documentation like ARCHITECTURE.md, and apply those changes to close the development loop.
The best way to archive completed development plans is to move them to a dedicated completed plans directory after stamping them with completion, ensuring the knowledge is stored for future reference and reuse.
You should run a retrospective to capture learnings immediately after a development plan is finished or following a dev-review, allowing you to extract lessons while the context is fresh and prevent reopenings.
Yes, you can automatically propose updates to CONVENTIONS.md and AGENTS.MD by analyzing the completed plan for actionable improvements and generating targeted documentation change proposals for user approval.
Yes, the plan archiving process requires manual user approval and guardrails before stamping completion and applying documentation updates, ensuring you maintain control over the retrospective changes.
You need to archive plans after a project retrospective to stamp completion, prevent task reopenings, and feed extracted learnings into future runs so subsequent development cycles benefit from past knowledge.
DFilipeSAnalyze plans, ideas, and git history to generate structured learning files.
tilework-techUpdate docs.md files after code changes using the nori-change-documenter subagent.
AngelP17Document decisions and learnings across planning, work, review, and compound loops.
mattjeffersonConvert post-release outcomes into documentation and automated guardrails.
