artifact-management

Name: artifact-management
Availability: InStock
Author: matrixfounder

Manage .AGENTS.md, TASK.md, and ARCHITECTURE.md files with write permissions and archiving protocols.

4|Updated Dec 17, 2025

Search Tags:#documentation #version control #task management #project memory #code documentation #artifact management

Ready to run

npx skills add https://github.com/MatrixFounder/Agentic-development --skill artifact-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: artifact-management
Source: https://github.com/MatrixFounder/Agentic-development/tree/main/.agent/skills/artifact-management
Command: npx skills add https://github.com/MatrixFounder/Agentic-development --skill artifact-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidelines and protocols for managing critical project documentation like TASK.md, ARCHITECTURE.md, and local .AGENTS.md files, ensuring consistency and preventing data loss.

Core Features & Use Cases

Defines artifact roles: Specifies which agent is responsible for creating or updating which document.
Establishes writing protocols: Outlines rules for updating and archiving documents, especially TASK.md.
Ensures consistency: Mandates reading relevant artifacts before starting work and updating them immediately after changes.
Use Case: Before starting a new development task, the Planner agent reads the ARCHITECTURE.md and TASK.md to understand the project's scope and requirements. After completing the task, the Developer agent updates the relevant .AGENTS.md file to reflect the changes made.

Quick Start

Follow the defined protocols for managing project artifacts and memory.

Frequently Asked Questions about artifact-management

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

FAQPage Schema

How do I manage project artifacts and ensure code documentation consistency across multiple agents?▼

Project artifact management enforces consistency by defining agent-specific write permissions for local .AGENTS.md files and global documents, preventing data loss. This ensures all agents follow strict guidelines for reading and updating critical project memory like TASK.md and ARCHITECTURE.md.

What is the best way to track development tasks and maintain project memory during software development?▼

Task tracking and project memory are maintained through a dual-state protocol linking internal agent memory with external documentation. Agents must read relevant artifacts before starting work and update TASK.md immediately after completing changes, enforcing version control and data integrity.

How does artifact management handle version control and archiving for active project tasks?▼

Version control for project tasks is handled through a strict archiving protocol mandated for TASK.md. This protocol enforces agent-specific write permissions and requires immediate documentation updates after changes, ensuring data integrity and preventing the loss of development progress.

Can I use local .AGENTS.md files to track code documentation changes made by different development agents?▼

Yes, local .AGENTS.md files are used to track code documentation and specific changes made by individual agents. The system enforces agent-specific write permissions for these files, ensuring that only the responsible agent updates its local memory after completing a development task.

Do I need to read ARCHITECTURE.md before starting a new development task in a multi-agent workflow?▼

Yes, agents must read relevant artifacts like ARCHITECTURE.md and TASK.md before starting work to understand project scope. This required reading ensures consistency, prevents conflicting changes, and aligns new development tasks with the established project architecture and memory.

What are the limitations of enforcing dual-state tracking between internal agent memory and external project documentation?▼

The limitation of dual-state tracking is the strict requirement for immediate manual updates to external documentation after internal agent changes. Failure to adhere to the archiving protocol for TASK.md or agent-specific write permissions can break project memory synchronization and compromise data integrity.