Which devloop files should be committed to Git?

You should commit plan.md, worklog.md, context.json, and the issues/ directory. Do not commit local.md or the spikes/ directory.

What is the difference between the .devloop/ and .claude/ directories?

.devloop/ is specifically for devloop plugin artifacts like implementation plans and worklogs, while .claude/ is reserved for core Claude Code configuration files.

How do I migrate my old devloop files to the new structure?

The skill includes a session-start hook that detects legacy files in .claude/ and provides an automated process to move them to the correct .devloop/ locations.

What are Spike reports in devloop?

Spikes are exploratory investigation reports used for technical research. They are kept in a local-only directory because they often contain transient notes rather than final project state.

Devloop File Locations

Name: Devloop File Locations
Author: Zate

byZate

Productivity & Workflow

Manages and documents the authoritative directory structure for devloop artifacts to ensure consistent project organization and Git workflows.

About

Devloop File Locations provides a standardized framework for managing development artifacts within the .devloop/ directory. It defines specific locations for implementation plans, worklogs, tech stack context, and issue tracking, while clearly distinguishing between Git-tracked project state and local-only preferences. By automating the migration from legacy paths and enforcing strict naming conventions, this skill ensures that development teams maintain a clean, predictable project structure that integrates seamlessly with AI-driven development workflows.

Key Features

Clear distinction between shared Git-tracked files and local-only settings
Standardized .devloop/ directory structure for development artifacts
Structured naming conventions for bugs, features, tasks, and spikes
0 GitHub stars
Comprehensive templates for implementation plans and worklogs
Automated migration paths from legacy .claude/ directory structures

Use Cases

Setting up a new software project with a standardized AI-assisted workflow
Migrating existing Claude Code projects to the modern .devloop/ standard
Managing complex issue backlogs and technical investigations within the repository

About

Key Features

Clear distinction between shared Git-tracked files and local-only settings
Standardized .devloop/ directory structure for development artifacts
Structured naming conventions for bugs, features, tasks, and spikes
0 GitHub stars
Comprehensive templates for implementation plans and worklogs
Automated migration paths from legacy .claude/ directory structures

Use Cases

Setting up a new software project with a standardized AI-assisted workflow
Migrating existing Claude Code projects to the modern .devloop/ standard
Managing complex issue backlogs and technical investigations within the repository