architecture-docs-maintainer

Maintain YAML frontmatter and cross-links across architecture and workflow documentation.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/likesjx/philotic-stack --skill architecture-docs-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-docs-maintainer
Source: https://github.com/likesjx/philotic-stack/tree/main/skills/architecture-docs-maintainer
Command: npx skills add https://github.com/likesjx/philotic-stack --skill architecture-docs-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that critical architecture and workflow documentation remains consistent, accurate, and well-linked, preventing outdated information and alignment issues.

Core Features & Use Cases

  • Metadata Management: Automatically applies and maintains a consistent YAML frontmatter schema across documentation.
  • Cross-Linking: Establishes and updates links between proposals, status documents, and task surfaces for clear traceability.
  • Truth Alignment: Verifies that documentation reflects current implementation status, design proposals, and workflow realities.
  • Use Case: When a new architectural proposal is made, this Skill ensures it's correctly tagged, linked to relevant status documents, and that the ARCHITECTURE_STATUS.md file is updated if the proposal impacts current truth.

Quick Start

Use the architecture-docs-maintainer skill to update the frontmatter and links for the 'docs/architecture/new-feature.md' file.

Frequently Asked Questions about architecture-docs-maintainer

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

FAQPage Schema
How do I keep architecture documentation in sync with workflow changes?

To keep architecture documentation in sync, use this Skill to automatically maintain frontmatter schemas, domain assignments, and cross-links between proposals and task surfaces within your docs directory.

How do I manage YAML frontmatter metadata for architecture proposals?

Manage YAML frontmatter metadata by using this Skill to apply a consistent schema, assign domains, and establish traceable links between new proposal documents and existing status truth files.

What is the best way to link architecture proposals to task surfaces?

The best way to link architecture proposals to task surfaces is to use this Skill to establish and automatically update bidirectional links between proposal documents, status files, and task lists.

Can I use this to verify documentation reflects current implementation status?

Yes, you can verify documentation reflects current implementation status by using the truth alignment feature to check that architecture docs accurately match current truth and near-future seams.

Does this work for updating the ARCHITECTURE_STATUS.md file when proposals change?

Yes, this works for updating the ARCHITECTURE_STATUS.md file by automatically modifying it whenever a new architectural proposal impacts current truth, ensuring status documents remain accurate.