← ClaudeAtlas

docs-frameworklisted

This skill should be used when the user asks to "create a review report", "write a status log", "add documentation", "name this artifact", or creates files in the .devflow/docs/ directory. Provides naming conventions, templates, and directory structure for reviews, debug sessions, design docs, and all persistent Devflow documentation artifacts.
dean0x/devflow · ★ 17 · Code & Development · score 76
Install: claude install-skill dean0x/devflow
# Documentation Framework The canonical source for documentation conventions in Devflow. All agents that persist artifacts must follow these standards. ## Iron Law > **ALL ARTIFACTS FOLLOW NAMING CONVENTIONS** > > Timestamps are `YYYY-MM-DD_HHMM`. Branch slugs replace `/` with `-`. Topic slugs are > lowercase alphanumeric with dashes. No exceptions. Inconsistent naming breaks tooling, > searching, and automation. Follow the pattern or fix the pattern for everyone. --- ## Directory Structure All generated documentation lives under `.devflow/docs/` in the project root: ``` .devflow/docs/ ├── reviews/{branch-slug}/ # Code review reports per branch │ ├── .last-review-head # HEAD SHA of last completed review (for incremental) │ ├── {timestamp}/ # Timestamped review directory (YYYY-MM-DD_HHMM) │ │ ├── {focus}.md # Reviewer report (e.g., security.md, architecture.md) │ │ ├── review-summary.md # Synthesizer output │ │ └── resolution-summary.md # Written by /resolve (if run) │ └── {timestamp}/ # Second review (incremental) │ ├── {focus}.md │ └── review-summary.md ├── bug-analysis/{branch-slug}/ # Bug analysis reports per branch │ ├── .last-analysis-head # HEAD SHA of last analysis (for incremental) │ └── {timestamp}/ # Timestamped analysis directory (YYYY-MM-DD_HHMM) │ ├── {focus}.md # Analyzer