team-memory

Analyzes commits, pull requests, and team discussions to compile a project memory file.

18|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/iankiku/forwward-teams --skill team-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-memory
Source: https://github.com/iankiku/forwward-teams/tree/main/skills/team-memory
Command: npx skills add https://github.com/iankiku/forwward-teams --skill team-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps maintain a detailed and shared history of a team's work, consolidating critical information such as decisions, fixes, and learnings into a centralized file for future reference.

Core Features & Use Cases

  • Consolidation of Team Work: Gather and organize team knowledge from commits, PRs, and conversations.
  • Memory Management: Store project history in a structured, append-only format that is easy to navigate.
  • Use Case: Use the /team-memory command after completing a project phase to capture all significant developments and decisions made during that period.

Quick Start

Run /team-memory to update the team memory file with the latest project insights.

Frequently Asked Questions about team-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract project history and decisions from git commits?

You can extract project history from git commits by parsing commit messages and pull requests to compile decisions, bugs, and learnings into a centralized team memory file for future reference.

What is the best way to consolidate team knowledge from pull requests and discussions?

The best way to consolidate team knowledge from pull requests and discussions is by analyzing this data to organize critical project insights into a structured, append-only team memory format.

How do I maintain a centralized record of project learnings and bug fixes?

To maintain a centralized record of project learnings and bug fixes, run an update command after completing project phases to capture significant developments and decisions in an append-only file.

Do I need a specific git integration to capture team memory?

Capturing team memory requires parsing git history and extracting relevant information from commits and pull requests, meaning your environment must support git history parsing to compile historical documentation.

When should I update the team memory file during a project lifecycle?

Update the team memory file after completing a project phase to capture all significant developments and decisions made during that period, ensuring comprehensive historical documentation.