AgentSkillsCN

post-implementation

在完成实施后，通过总结工作、更新文档、归档待办事项，并对外传达变更内容，为项目画上圆满句号。

SKILL.md
--- frontmatter
name: post-implementation
description: Use after completing implementation to wrap up work, update documentation, archive TODOs, and communicate what was changed.

Post-Implementation

This skill focuses on the closure phase: update documentation, archive or remove completed TODOs, and communicate the changes so the team and codebase stay synchronized.

Closure Flow

  1. •Verify completion. Confirm the work matches the original plan and acceptance criteria.
  2. •Update TODO.md. Mark completed tasks as done, remove them, or move them to a "Done" section. Add follow-up tasks if needed.
  3. •Update documentation. Revise relevant docs (READMEs, API docs, design docs) to reflect changes. Update timestamps and authors.
  4. •Summarize changes. Prepare a clear summary of what was done, why, and any breaking changes or migrations needed.
  5. •Communicate. Share the summary with the team, link to PRs/commits, and note any follow-up work.

Documentation Update Strategy

  • •Update docs that describe the changed functionality.
  • •Remove outdated information or mark as deprecated.
  • •Add examples if new features were introduced.
  • •Update diagrams, schemas, or data flow descriptions.
  • •Keep a changelog entry for significant changes.

TODO.md Cleanup

  • •Move completed items to a "Done" or "Archived" section with completion date.
  • •Remove fully completed items if keeping history elsewhere.
  • •Add new TODOs for discovered issues or technical debt.
  • •Update priorities and assignments for remaining items.

Change Communication

Include in your summary:

  • •What was implemented (features, fixes, refactors).
  • •Files/modules touched.
  • •Breaking changes or migrations required.
  • •Performance impacts or considerations.
  • •Known issues or limitations.
  • •Follow-up work or debt items.

Deliverables After Implementation

  • •Updated TODO.md with completed items marked/archived.
  • •Updated documentation reflecting the current state.
  • •Written summary of changes.
  • •Communication to stakeholders (PR description, Slack message, etc.).

When to Use

Apply this skill whenever you finish implementation work—features, bug fixes, refactors, or documentation updates—to ensure proper closure and team alignment.

Check for Existing Documentation

Before proceeding, check if documentation was created during implementation:

Look for these directories:

  • •_docs/draft/(feature)/
  • •_docs/plan/(feature)/
  • •_docs/intent/(feature)/
  • •_docs/survey/(feature)/
  • •_docs/guide/(feature)/ (may need creation/updates)
  • •_docs/reference/(feature)/ (may need creation/updates)

Branching Logic

If NO documentation exists:

  • •Update TODO.md with completion status
  • •Summarize changes for communication
  • •Skip documentation-specific cleanup

If documentation EXISTS:

  1. •Update existing documents to reflect final implementation
  2. •Create guide/ and reference/ if they don't exist (recommended for public APIs)
  3. •Archive temporary documents (draft/plan/survey) after intent approval
  4. •See .codex/skills/docs-cleanup/SKILL.md for full documentation workflow