One-click install
npx skills add https://github.com/lc0rp/luke-agent-scripts --skill ia2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia2
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/parked-skills/archive/ia2
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill ia2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintains documentation structure across project stages to prevent drift and make pages easy to locate, with clear audience tagging and archiving.

Core Features & Use Cases

  • Enforces one doc type per page for consistency across the repository.
  • Keeps project-stage folders in a fixed order and archives replaced docs to 99-archive with a successor link.
  • Guides content creators to include audience and ownership metadata on each content page.

Quick Start

Open templates/docs-README.md and confirm the standard folder order is followed.

Frequently Asked Questions about ia2

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

FAQPage Schema
How do I organize documentation to prevent content drift across multiple project stages?

Documentation structure enforcement keeps pages easy to locate by requiring one doc type per page, fixed project-stage folder order, and archiving replaced docs with a successor link to prevent drift.

What is information architecture for large doc ecosystems and when do I need it?

Information architecture for docs dictates placement, tagging, and archiving across multiple stages and audiences. You need it when documentation drift and disorganization make pages hard to locate across large repositories.

How do I add audience metadata to markdown frontmatter for documentation pages?

Add audience and ownership metadata fields to markdown frontmatter on each content page. This tagging guides content creators to satisfy metadata requirements and clarify page relevance for different audiences.

What's the best way to archive replaced documentation pages in a repository?

Move replaced documentation pages to a 99-archive folder and include a successor link. This maintains a fixed information architecture folder layout and prevents confusion over outdated content.

Does this documentation organization approach work for large repositories with multiple audiences?

Yes, this documentation organization approach is designed for large doc ecosystems spanning multiple stages, pages, and audiences, guiding placement, tagging, and archiving to prevent drift and confusion.

Why does my documentation folder structure keep drifting out of order?

Documentation folder structure drifts without a fixed information architecture layout. Enforcing a standard folder order and archiving replaced docs with successor links prevents this structural drift.