skills.rest
mauriciodelrio
mauriciodelrioCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

docs-structure

Create a standardized .docs folder structure with markdown subfolders and iteration logs.

3|Updated Apr 12, 2026
Search Tags:#documentation#markdown#project-setup#knowledge-management#folder-structure#iteration-logs
One-click install
npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill docs-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-structure
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/agent-workflow/docs-structure
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill docs-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a clear, standardized way to organize all project documentation, ensuring the agent and developers know where to read context and record decisions, features, and iteration logs.

Core Features & Use Cases

  • Defines the .docs/ hierarchy with folders for features, brainstorming, rules, context logs, and permanent memory.
  • Guides the agent on when to read or write each folder during the development lifecycle.
  • Includes templates for iteration logs and monthly memory entries to keep a reliable project history.
  • Ideal for software teams that need consistent documentation practices across sprints and feature development.

Quick Start

Ask the agent to create the .docs folder with the standard subfolders for your current project.

Frequently Asked Questions about docs-structure

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

FAQPage Schema
How do I organize project documentation into a standardized folder structure?▼

You can organize project documentation by establishing a standardized .docs folder structure with dedicated subfolders for features, brainstorming, rules, context logs, and permanent memory.

What's the best way to keep iteration logs and project history in markdown?▼

The best way to keep iteration logs in markdown is to use predefined templates for daily entries and append-only monthly memory records, ensuring a reliable and consistent project history.

How does a standardized .docs folder structure improve software development?▼

A standardized .docs folder structure improves software development by providing consistent locations for context and rules, so agents and developers always know where to read and write decisions.

Does this .docs documentation structure work for software teams across multiple sprints?▼

Yes, this .docs documentation structure is ideal for software teams that need consistent documentation practices across multiple sprints and ongoing feature development.

When do I need a dedicated folder structure for project knowledge management?▼

You need a dedicated folder structure for project knowledge management when your team requires consistent locations for brainstorming ideas, iteration logs, and historical memory to avoid scattered context.

How to set up the .docs folder for my current project?▼

To set up the .docs folder, ask your agent to create the directory with standard subfolders for features, brainstorming, rules, context logs, and permanent memory for your current project.

Related Skills

Explore More Software Engineering Skills→
alansmelloalansmello

speckit-git-initialize

Initialize a Git repository with an initial commit in Bash or PowerShell.

Community
Intermediate
garagongaragon
204

compound

Extract sprint artifacts into structured markdown solution documents with frontmatter and metadata.

Community
Intermediate
zzafergokzzafergok
1

markdown-to-html-skill

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.

Community
Intermediate
Goblin1024Goblin1024
6

wiki

Store and retrieve project knowledge in a Markdown wiki under .omk/wiki with cross-reference links and searchable pages.

Community
Intermediate