file-locations

Name: file-locations
Availability: InStock
Author: Zate

Define and document the .devloop directory structure and file locations.

9|2|Updated Dec 5, 2025

Search Tags:#templates #project structure #devloop #file locations #git-tracked

Ready to run

npx skills add https://github.com/Zate/cc-plugins --skill file-locations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-locations
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/devloop/skills/file-locations
Command: npx skills add https://github.com/Zate/cc-plugins --skill file-locations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thisskill acts as an authoritative reference for the .devloop/ directory structure, clarifying which files are git-tracked versus local-only, their purposes, and naming conventions to reduce confusion and save time.

Core Features & Use Cases

Location clarity: quickly understand where plans, issues, and logs live.
Migration aid: helps teams move from older paths to new ones like .claude/ or similar.
Sharing conventions: standardizes artifact placement across projects.

Quick Start

Refer to the directory mapping to place new plan.md, worklog.md, and issues files correctly.

Frequently Asked Questions about file-locations

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

FAQPage Schema

How should I organize files in the .devloop directory for project templates and structure?▼

The .devloop directory centralizes project artifacts with a standardized structure: plan.md for planning documents, worklog.md for development logs, context.json for project context, issues/ subdirectory for issue tracking, and spikes/ for experimental work. This organization clarifies file purposes and enables consistent project management across teams.

Which files in .devloop should be git-tracked versus kept local-only?▼

Git-tracking rules vary by file type: plan.md and issue files are typically git-tracked to share project direction, while worklog.md and local context.json remain local-only to avoid merge conflicts. The Skill specifies exact conventions so teams maintain consistent artifact placement without confusion.

How do I migrate from older .claude paths to the new .devloop directory structure?▼

Migration involves mapping existing artifacts from legacy .claude paths to corresponding .devloop locations—plans to plan.md, logs to worklog.md, and context files to context.json. The Skill provides authoritative path mappings and naming conventions to ensure no artifacts are lost during transition.

What naming conventions and purposes define each artifact type in .devloop?▼

Each artifact serves a distinct function: plan.md documents project roadmaps, worklog.md tracks development progress, context.json stores project metadata, issues/ holds structured issue records, and spikes/ contains experimental explorations. Standardized naming prevents duplication and clarifies intent across the devloop workflow.

How do I troubleshoot file location issues when devloop artifacts aren't being recognized?▼

File location problems typically stem from incorrect directory paths or naming mismatches. Reference the .devloop structure definition to verify artifacts follow enforced conventions—correct paths, proper subdirectory placement, and git-tracking status—then move or rename files accordingly.