skills.rest
gvarela
gvarelaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

project-structure

Enforce standardized documentation structure in docs/plans directories.

1|1|Updated Oct 8, 2025
Search Tags:#design#planning#documentation#research#structure#tasks
One-click install
npx skills add https://github.com/gvarela/prompts --skill project-structure-gvarela
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-structure
Source: https://github.com/gvarela/prompts/tree/main/claude-code/skills/project-structure
Command: npx skills add https://github.com/gvarela/prompts --skill project-structure-gvarela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a consistent project documentation structure across the docs/plans directory to prevent ad-hoc documentation and miscommunication.

Core Features & Use Cases

  • Enforces separation of research.md for facts, design.md for decisions, tasks.md for implementation, thoughts/ for explorations.
  • Helps teams maintain a predictable documentation workflow for software projects, enabling faster onboarding and audits.
  • Use Case: When starting a feature, create or update docs/plans with these files to reflect research, decisions, and tasks.

Quick Start

Create or organize the files under docs/plans/ as follows: research.md, design.md, tasks.md, thoughts/; start by documenting factual information in research.md, architectural decisions in design.md, actionable steps in tasks.md, and any open questions in thoughts/.

Frequently Asked Questions about project-structure

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

FAQPage Schema
How do I structure project documentation for software planning?▼

To structure project documentation, organize files under docs/plans: research.md for facts, design.md for decisions, tasks.md for implementation, and a thoughts/ directory for explorations. This separation enforces a predictable workflow for software planning and enables faster onboarding and audits.

What is the best way to separate software design decisions from research notes?▼

The best way to separate design decisions from research notes is maintaining distinct files: research.md for factual information and design.md for architectural decisions. This standardized documentation structure prevents ad-hoc files and miscommunication during project planning.

Why does my software project need a standardized docs directory structure?▼

A standardized docs directory structure is needed to prevent ad-hoc documentation and miscommunication. Enforcing consistent file roles and naming conventions within docs/plans enables consistent reviews and seamless handoffs across the team.

How do I organize implementation tasks and open questions in a software project?▼

Organize implementation tasks and open questions by placing actionable steps in tasks.md and exploratory content in the thoughts/ directory. This file organization under docs/plans ensures actionable items are tracked separately from open explorations.

Does this documentation structure work for teams handling frequent project handoffs?▼

Yes, this documentation structure works for teams handling frequent project handoffs. By enforcing predictable file roles for research, design, and tasks, it enables consistent reviews and faster onboarding for new team members taking over the project.

Related Skills

Explore More Software Engineering Skills→
asermaxasermax
1

init-framework

Initialize katachi framework directories and CLAUDE.md baseline in projects.

Community
Intermediate
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
zbyzby
82

cp-skill-validate

Validate frontmatter, schema, links, and required sections in knowledge base notes.

Community
Advanced
hgflimahgflima
1

documentation-and-adrs

Create and manage architectural decision records using markdown templates.

Community
Advanced