init

Scaffold standardized documentation directory trees and docops.json configuration.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/murillodutt/cellm --skill init-murillodutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/murillodutt/cellm/tree/main/docops/skills/init
Command: npx skills add https://github.com/murillodutt/cellm --skill init-murillodutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a standardized documentation scaffold for new projects, eliminating manual setup and ensuring consistent structure from day one. It centralizes the doc root configuration and templates so teams can start documenting quickly with minimal boilerplate.

Core Features & Use Cases

  • Scaffolds a complete documentation directory tree including index.md, glossary.md, project-conveyor.md, specs/, reference/ (with code-evidence/ and conveyor-gaps.md), howto/, runbooks/, and decisions/.
  • Seeds templates and config (docops.json) to define docRoot and enable subsequent docops tooling.
  • Preserves existing files by never overwriting and resolves docRoot from existing .claude/docops.json when present.
  • Supports multi-language projects by templating language-specific structures.

Quick Start

Run the Init skill to scaffold the standard documentation structure in your project root.

Frequently Asked Questions about init

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

FAQPage Schema
How do I scaffold a standardized documentation directory structure for a new project?

To scaffold documentation structures, this tool generates a deterministic directory tree with index.md, glossary.md, specs/, reference/, howto/, runbooks/, and decisions/ while writing back a docops.json configuration file to consolidate your project setup.

What is an LLM-first documentation scaffold and when do I need one?

An LLM-first documentation scaffold establishes a standardized doc hierarchy and centralized docops.json configuration designed for automated tooling. You need one when starting projects that require consistent doc structures and minimal manual boilerplate from day one.

How do I set up multi-language project documentation templates without overwriting existing files?

To set up multi-language templates without data loss, the scaffolding process respects existing files by never overwriting them. It templates language-specific documentation structures while resolving the doc root from any existing .claude/docops.json configuration.

Can I use automated project setup tools to generate a docops.json configuration?

Yes, you can use automated project setup tools to generate a docops.json configuration. The scaffold seeds this file to define the docRoot and enable subsequent docops tooling, ensuring centralized configuration for your documentation hierarchy.

What is the best way to automate project setup for consistent documentation hierarchies?

The best way to automate consistent documentation hierarchies is using a scaffolding tool that applies deterministic directory layouts. This eliminates manual setup, ensures structural consistency across projects, and seeds necessary templates and configuration files automatically.

Does the documentation scaffold preserve existing files when generating templates?

Yes, the documentation scaffold preserves existing files by never overwriting them during generation. It safely resolves the docRoot from an existing .claude/docops.json file if present, ensuring your current project data remains intact while seeding new templates.