Project Doc Initializer

Problem

Many code projects lack a single entry point for engineering and AI-assisted work: behavior rules, directory conventions, common commands, and API expectations are often scattered across chat threads or tribal knowledge. project-doc-init addresses this by inspecting the project itself, identifying the tech stack and architecture, and generating a maintainable AGENTS.md plus optional docs/ sub-docs with clear lookup paths.

How It Works

The skill runs without extra parameters. It reads configuration files and directory structure, detects project types such as Vue, React, Node, Go, and Python, and chooses documentation granularity based on project complexity:
- AGENTS.md: behavior rules, scenario-based navigation, and common commands as the primary entry point.
- docs/PROJECT.md: baseline information such as tech stack and directory layout.
- Specialized docs: docs/API.md, docs/COMPONENT.md, docs/ARCHITECTURE.md, or docs/DATA_MODEL.md are generated only when interfaces, components, architecture, or data models warrant separate documentation.
Paths use relative paths for portability; small projects may only produce AGENTS.md and docs/PROJECT.md.

Boundaries

This skill is intended for code projects with an existing structure and does not assume a fixed template. If key files such as package.json or go.mod are missing, or the tech stack cannot be identified, it generates only baseline documentation from confirmed information and asks the user about uncertain parts; when configuration is absent, it does not force dynamic specialized docs.