update-project-meta

Update project documentation files with canonical formatting and conflict detection.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill update-project-meta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-project-meta
Source: https://github.com/meisijiya/ohMeisijiyaCode/tree/main/skills/update-project-meta
Command: npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill update-project-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps project-level documentation consistent, durable, and easy to update when a repository needs recorded decisions, glossary terms, gotchas, conventions, roadmaps, or project briefs.

Core Features & Use Cases

  • Decision capture: Adds or updates architectural decisions, decision logs, and supersession links without losing history.
  • Project memory maintenance: Updates glossary terms, knowledge entries, gotchas, and long-lived project context in canonical formats.
  • Operational documentation: Maintains project briefs, roadmaps, agent skills, and related metadata so future sessions can load the right context quickly.
  • Use Case: When a team agrees on a new naming convention or resolves a recurring bug pattern, this Skill records it in the correct document and keeps cross-references aligned.

Quick Start

Ask this skill to record a new decision, term, gotcha, or roadmap update for the current project.

Frequently Asked Questions about update-project-meta

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

FAQPage Schema
How do I maintain architectural decision records and project glossaries in a repository?

To maintain architectural decision records and project glossaries, use a skill that updates structured documentation files with duplicate checks, conflict detection, and canonical formatting to preserve single-writer consistency and cross-file links.

What is the best way to record gotchas and naming conventions for future context loading?

Recording gotchas and naming conventions is best handled by appending entries to long-lived project context files while applying supersession tracking and conflict detection to keep cross-references aligned.

How do I update a project roadmap and decision log without losing previous history?

To update a project roadmap and decision log without losing history, apply supersession tracking to link outdated entries to new ones, ensuring canonical formatting preserves the archival records.

Does this project metadata maintenance approach handle duplicate detection in knowledge bases?

Yes, project metadata maintenance handles duplicate detection in knowledge bases by requiring duplicate checks and conflict detection during updates to ensure canonical formatting and single-writer consistency.

When do I need to track supersession links in architectural decision records?

You need to track supersession links in architectural decision records when adding or updating decisions, ensuring that outdated decisions are properly linked to new ones without losing historical context.