---

name: doc-numbering description: Automatically number new markdown documentation files in the docs/ folder using a sequential numbering system (e.g., 00_, 01_, 02_).

Documentation Numbering System

Instructions

When creating or generating markdown documentation files in the project:

1. Always place documentation files in the docs/ directory (not in the project root)
2. Search for all markdown files in the docs/ directory that start with a number
3. Find the highest number currently in use
4. Add 1 to that number
5. Prefix the new markdown file with that number followed by an underscore (e.g., 00_, 01_, 02_)
6. Use a two-digit format (e.g., 01_ not 1_)

Examples

Example 1: First documentation file

Existing files in docs/: None with number prefixes

Creating: setup_guide.md

Result: docs/00_setup_guide.md

Example 2: Adding to existing numbered files

Existing files in docs/:

Copy00_E2E_TEST_REPORT.md
01_SANDBOX_SETUP.md
02_RAY_SETUP_GUIDE.md
03_UV_SETUP.md
04_things_to_change.md
20_TEST_TRAJECTORY_EXAMPLE.md
21_onboarding_docs.md

Creating: troubleshooting.md

Result: docs/22_troubleshooting.md (highest is 21, so use 22)

Example 3: Typical workflow

User request: "Create an implementation plan"

Claude actions:

1. Checks docs/ directory, finds files with highest number = 21
2. Creates file named docs/22_implementation_plan.md (21 + 1 = 22)

Important Notes

• README.md and CLAUDE.md remain in the project root (these are special files)
• All other markdown documentation goes in docs/
• Always use the numbering system for consistency
• If a specific range is full (e.g., 00-09), use the next logical number (10+)
• Keep filenames descriptive and use underscores for spaces