What should I put in the thoughts/ directory?

The thoughts/ directory is for informal notes, experiments, brainstorming, and any information that isn't yet ready for formal documentation.

Can I use this for existing projects?

Yes, this skill can be applied to existing projects to help organize current knowledge and plan future feature development.

What is the primary goal of the Structured Project Documentation skill?

The primary goal is to prevent documentation clutter by enforcing a strict separation between objective research, architectural decisions, and implementation steps.

Where are the files stored in my project?

All documentation generated or managed by this skill is stored within the docs/plans/ directory of your repository.

What is the difference between research.md and design.md?

Research.md contains only facts about the codebase or external tools, while design.md is strictly for decisions and the rationale behind choosing specific options.

Structured Project Documentation

Name: Structured Project Documentation
Author: gvarela

bygvarela

生産性とワークフロー

Enforces a clear separation of concerns in project documentation by organizing research, design, and implementation into specific directories.

概要

The Structured Project Documentation skill provides a rigorous framework for managing project knowledge within Claude Code. By enforcing the use of specific files in the docs/plans/ directory—research.md for facts, design.md for decisions, and tasks.md for implementation—it ensures that technical documentation remains clean, searchable, and logical. This skill is essential for teams and solo developers who want to avoid documentation rot and maintain a clear distinction between what is known, what has been decided, and what needs to be built.

主な機能

Isolated implementation task lists to streamline coding workflows
Strict separation of factual research from architectural decisions
Dedicated thoughts/ directory for brainstorming and exploration
Standardized docs/plans/ directory structure
Prevents cognitive overload by categorizing information by intent
0 GitHub stars

ユースケース

Onboarding new developers by providing a clear trail of project rationale
Planning complex new features where research and design choices must be audited
Managing large-scale refactors with step-by-step implementation tracking

概要

主な機能

Isolated implementation task lists to streamline coding workflows
Strict separation of factual research from architectural decisions
Dedicated thoughts/ directory for brainstorming and exploration
Standardized docs/plans/ directory structure
Prevents cognitive overload by categorizing information by intent
0 GitHub stars

ユースケース

Onboarding new developers by providing a clear trail of project rationale
Planning complex new features where research and design choices must be audited
Managing large-scale refactors with step-by-step implementation tracking