project-doc-modes

Automates scaffolding, migrating, and archiving repository documentation by mode and governance workflows.

2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/verycafe/project-doc-modes --skill project-doc-modes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-doc-modes
Source: https://github.com/verycafe/project-doc-modes/tree/main
Command: npx skills add https://github.com/verycafe/project-doc-modes --skill project-doc-modes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the organization and governance of repository documentation by scaffolding, migrating, and archiving docs.

Core Features & Use Cases

  • Scaffolds and migrates repository documentation into mode-based structures (collaboration or iterative) with governance guidance
  • Supports SDD-RIPER workflows for team governance and AI-assisted coding standards
  • Keeps root governance at AGENTS.md and provides Claude Code bridge via CLAUDE.md for cross-agent coordination
  • Preserves existing code directories unless otherwise requested, and archives historical materials in docs/archive/

Quick Start

Scaffold the repository's docs in the chosen mode and language, then review AGENTS.md and CLAUDE.md as the governance entrypoints.

Frequently Asked Questions about project-doc-modes

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

FAQPage Schema
How do I scaffold repository documentation into collaboration or iterative modes?▼

Scaffolding repository documentation into collaboration or iterative modes automates organizing, migrating, and archiving docs into structured governance formats. It enforces a PRD -> PHASE -> SPEC workflow to standardize your project's files.

What is the SDD-RIPER governance workflow for repository docs?▼

SDD-RIPER governance is a workflow standard for AI-assisted coding that structures repository documentation through a strict PRD -> PHASE -> SPEC pipeline. It centralizes root governance rules at AGENTS.md for team coordination.

Does this documentation governance approach work with both Codex and Claude Code?▼

Yes, the documentation governance supports both Codex and Claude Code integrations. It maintains root governance at AGENTS.md and provides a specific Claude Code bridge via CLAUDE.md to ensure cross-agent coordination.

How do I archive historical repository docs during a mode migration?▼

Archiving historical repository docs during a mode migration automatically preserves existing code directories while moving previous materials into docs/archive/. This ensures historical context is retained without cluttering the new structure.

Where should root governance rules be placed when scaffolding repo docs?▼

Root governance rules should be placed at AGENTS.md when scaffolding repository docs. A corresponding CLAUDE.md file acts as a bridge for Claude Code integrations, ensuring AI agents follow the standards.

Are generated documentation files kept locally or committed to the repository?▼

Generated documentation files are kept local by default. The scaffolding process enforces this constraint to prevent automated doc generation from cluttering the repository's commit history while maintaining the PRD -> PHASE -> SPEC workflow.