skills.rest
Dimon94
Dimon94COMMUNITY
Explore all skills by this author →
GitHub

devflow-file-standards

Enforce standardized file naming, directory structures, and YAML frontmatter for CC-DevFlow.

111|21|Updated Sep 17, 2025
Search Tags:#documentation#standards#conventions#YAML#naming#file structure#devflow
One-click install
npx skills add https://github.com/Dimon94/cc-devflow --skill devflow-file-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devflow-file-standards
Source: https://github.com/Dimon94/cc-devflow/tree/main/.claude/skills/devflow-file-standards
Command: npx skills add https://github.com/Dimon94/cc-devflow --skill devflow-file-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates confusion and inconsistencies in file naming, directory structure, and document formatting across the CC-DevFlow project. It ensures all agents and users follow a unified convention, making the codebase easier to navigate, understand, and maintain.

Core Features & Use Cases

  • Standardized IDs: Defines consistent formats for Requirement IDs (REQ-XXX) and Task IDs (TXXX) used throughout the project.
  • Unified Directory Structure: Prescribes consistent paths for requirements, bugs, and generated documents, improving discoverability.
  • YAML Frontmatter Rules: Specifies required YAML fields for key documents like PRD.md, TECH_DESIGN.md, and TASKS.md, ensuring metadata consistency.
  • Use Case: A new developer needs to quickly understand where to find the PRD.md for REQ-001 or what fields are required in the TASKS.md frontmatter. This skill provides a single, authoritative source of truth for all such conventions.

Quick Start

Ask "What's the format of REQ-ID?" or "Where does PRD.md go?" to get quick answers on project file standards.

Frequently Asked Questions about devflow-file-standards

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

FAQPage Schema
How do I standardize file naming and directory structure across my project?▼

Standardized file naming conventions enforce consistent ID formats (REQ-XXX, T###) and directory paths (devflow/requirements/REQ-XXX/) across your entire project. This eliminates confusion, improves navigation, and ensures all agents and developers follow unified rules for requirements, tasks, and documentation.

What YAML frontmatter fields are required for project documents?▼

YAML frontmatter rules specify required metadata fields for PRD.md, TECH_DESIGN.md, EPIC, and TASKS.md files. Enforcing consistent frontmatter across documents ensures metadata consistency and makes documents discoverable and machine-parseable throughout the workflow.

Where should I store requirements and generated documents in my project?▼

Unified directory structure prescribes consistent paths for requirements, bugs, and generated documents within the devflow layout. Clear paths improve discoverability and make it trivial for new developers to locate PRD.md, technical designs, and task files for any requirement.

Can I validate file naming and structure compliance automatically?▼

File standards are validated via check-prerequisites.sh, which enforces naming conventions, directory paths, and YAML frontmatter across all flow commands and agents. Automated validation prevents non-compliant files from entering the workflow and consolidates standards that would otherwise be duplicated across agents.

Why should I enforce consistent ID formats like REQ-XXX and T### across my team?▼

Consistent ID formats eliminate ambiguity and enable reliable cross-referencing throughout the project. Standardized formats ensure all agents and developers use the same notation, making it possible to trace requirements through tasks, design documents, and implementation without manual interpretation.

Related Skills

Explore More Software Engineering Skills→
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
ezagent42ezagent42
1

prd-analyze

Extract modules, user stories, NFRs, constraints, and dependencies from a PRD into YAML.

Official
Advanced
peopledearpeopledear
1

Global Tech Stack

Enforce global tech stack standards across code files, build scripts, and project configurations.

Official
Basic
jperezdelrealjperezdelreal

project-conventions

Standardize coding conventions across codebase modules, naming, and documentation.

Community
Intermediate