Skip to content

manage-project-docs v0.3.0

Choose a tag to compare

View all tags
@junwei529 junwei529 released this 28 Aug 01:53
· 9 commits to main since this release
v0.3.0
02a1494

AI-native documentation architecture for growing projects

manage-project-docs gives coding agents and humans a shared documentation architecture that keeps a project understandable, governable, and resumable as it evolves.

It organizes project knowledge around five durable responsibilities:

  • purpose and scope;
  • work and verification;
  • authority and canonical write routing;
  • current state and supporting evidence;
  • next action and recovery.

For a new or under-documented project, the Skill can establish the smallest coherent architecture first, then expand it only when real product capabilities, modules, verification needs, authority boundaries, or recovery requirements emerge.

For an established project, it maps existing documents to the same logical responsibilities without requiring a replacement file tree. Existing filenames, document language, canonical owners, and working conventions can remain in place. The Skill identifies missing, conflicting, duplicated, or stale responsibilities and proposes only the minimum compatible additions or routing changes. A sufficient mature documentation system is preserved and returns NOOP rather than being migrated for appearance.

What this release provides

  • An AI-native logical documentation architecture that can grow with the project.
  • Compatibility mapping for repositories that already have their own documentation structure.
  • Explicit canonical ownership so each durable fact has one authoritative write location while remaining discoverable from multiple entry points.
  • Bounded audit and proposal behavior before any adoption, structural change, authority change, or write.
  • Starter and continuity-anchor templates for projects that genuinely need new documentation.
  • Repository-local conflict and mature-project no-op evaluation cases and fixtures.
  • Independent provenance and repository validation.

Migration

This is the first independently owned release of the Skill. Its public lineage was previously published from junwei529/skills at v0.2.0.

The v0.3.0 Skill package contains six files materialized from later source commit 80910a8b2375a11be897e9660c4b00a06d00dd13 and is not byte-identical to the legacy v0.2.0 tag. Use junwei529/manage-project-docs for v0.3.0 and later releases.

Existing projects do not need to replace a sufficient documentation layout merely to adopt this release. Begin by mapping current documents to the five logical responsibilities, preserve valid canonical owners, and introduce structural changes only when a real gap exists and the concrete effect is explicitly approved.

Evidence boundary

This release is bound to commit 02a1494e7dd22f9b598b752057c792aa3b2e3ae2 and package tree 21971e5d8872c9c131675a926e45fdcfad31d95c.

Local qualification verified the exact tracked package, repository checks, and two bounded SOURCE behavior slices: conflict governance and mature-project no-op.

Controller-observed selection/load attribution, broader negative-context coverage, persistent install/update/uninstall/rollback behavior, stable installed-copy behavior, and broad efficacy remain UNKNOWN and require separate evidence.

Assets 2
Loading