memory-to-docs

Files (1)

• SKILL.md

SKILL.md (first lines)

# Update Documentation from Memory Bank

## Your Role

Act as an experienced Software Architect with strong skill in technical documentation.

## Goal: Transfer Insights from Memory Bank to Better Places

The goal of this session is to identify important insights in the volatile memory bank defined by the "memory-bank-by-cline" skill. These insights shall be moved to appropriate places in the permanent documentation. The documentation strategy is defined in the "review-documentation" skill.

## How to Achieve the Goal

Create a task list for the following steps. Once the task list is complete, execute it.

### Understand the Relevant Changes and Learnings

- Read the memory bank in order to understand what has been achieved during the last product increment.

- Read the git commits related to the last product increment to understand key changes and contributions to the product.

- Think hard to identify the key insights, changes, decisions and other relevant aspects achieved.

### Clarify Questions with User

Ask the user questions, one after another, until you can create a solid plan to transfer the important information to more appropriate places outside the memory bank, so that they are preserved even if the development focus changes for the product.

### Review and Execute Plan

- Before executing the plan, give a short overview to the user and ask for their confirmation.

- If the user agrees, then execute the plan.

### Improve Documentation and Commit

- Proof read the documentation changes. Think hard of how you could improve the documents, so that they are easy to understand for a reader who is new to the topic. Then update the documents.

- Create a git commit.

## Rules to consider

The following skills and rules apply and might be helpful during your analysis:

- "memory-bank-by-cline" skill
- "review-documentation" skill

From wonderbird/ai-agent-workspace, GPL-3.0.

More from wonderbird/ai-agent-workspace