pm-update

Name: pm-update
Availability: InStock
Author: AMDResearch

Persist durable project knowledge into Project Memory after meaningful work.

3|3|Updated Aug 19, 2024

Search Tags:#documentation #workflows #knowledge-management #project-memory #persist #pm-update

Ready to run

npx skills add https://github.com/AMDResearch/dh_comms --skill pm-update-amdresearch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-update
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/pm-update
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill pm-update-amdresearch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist durable knowledge back into Project Memory after meaningful work. Use this to ensure future sessions start from an accurate project truth and to prevent loss of critical decisions, boundaries, and context.

Core Features & Use Cases

Updates affected PM units (pm-current-state.md, pm-decisions.md, glossary, and terminology) so they reflect new truths.
Refreshes code-navigation references and boundaries when decisions impact future work.
Improves long-term project continuity by recording decisions, open questions, and verified facts for subsequent sessions.

Quick Start

Run the pm-update action after completing a meaningful task to persist relevant durable knowledge.

Frequently Asked Questions about pm-update

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

FAQPage Schema

How do I persist durable project knowledge after a work session?▼

You persist durable project knowledge by updating affected Project Memory units like pm-current-state.md and pm-decisions.md to reflect new truths, ensuring future sessions start from accurate project context.

What is the best way to maintain project memory across multiple sessions?▼

Maintaining project memory across sessions is achieved by recording decisions, boundaries, and verified facts with timestamps directly into Project Memory artifacts after meaningful work is completed.

When should I update project memory units and documentation?▼

Update project memory units and documentation immediately after completing a meaningful task, specifically when decisions impact future work or alter code-navigation references and project boundaries.

Can I refresh code-navigation references after changing project boundaries?▼

Yes, you can refresh code-navigation references and boundaries during the project memory update process, ensuring structural documentation stays synchronized with any architectural decisions made during the session.

Does persisting project knowledge require updating a glossary?▼

Yes, persisting project knowledge requires updating the glossary and terminology units alongside current state and decision logs to prevent loss of critical domain context in subsequent sessions.