📝 任务完成后归档

Automating post-task learnings from complex debugging involves identifying direct and root causes, deciding whether to archive the insights, and generating a standardized knowledge artifact for future reference.

The best way to archive post-work analysis for iterative development is applying a structured workflow that captures insights and updates a reusable knowledge file at .agent/skills/post-work-analysis/SKILL.md.

No, this post-work archival workflow requires no external dependencies, operating independently to analyze task outcomes and generate standardized knowledge documentation.

You create a reusable knowledge artifact from post-task learnings by running the archival workflow, which generates or updates a SKILL.md file with a clear name, description, and guidance.

You should archive debugging insights as a Skill when a task involves complex iterative development where documenting direct causes, root causes, and rationale provides value for subsequent future work.

Yes, you can use this knowledge management workflow for research tasks, as it applies to any complex debugging, research, or iterative development scenario requiring documented post-work analysis.