atelier-spec-project-structure

Organize project documentation into AgentOS standards, product, and spec layers.

39|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/martinffx/claude-code-atelier --skill atelier-spec-project-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atelier-spec-project-structure
Source: https://github.com/martinffx/claude-code-atelier/tree/main/plugins/atelier-spec/skills/atelier-spec-project-structure
Command: npx skills add https://github.com/martinffx/claude-code-atelier --skill atelier-spec-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Directory structure implementing the AgentOS 3-layer context model to help teams organize project docs, specs, and change proposals.

Core Features & Use Cases

  • Directory layout for the 3-layer model: docs/standards, docs/product, and docs/spec
  • Built-in support for Beads task tracking via a dedicated .beads folder
  • Clear overview through CLAUDE.md and a structured workspace for specs and documentation

Quick Start

Create the project folder following the AgentOS 3-layer structure shown (docs/standards, docs/product, docs/spec, a .beads directory, and a CLAUDE.md overview).

Frequently Asked Questions about atelier-spec-project-structure

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

FAQPage Schema
What is the AgentOS 3-layer project structure for documentation?

The AgentOS 3-layer project structure organizes repository documentation into distinct directories for standards, product context, and specifications, ensuring clear separation of concerns for software teams.

How do I organize project docs and specs using the AgentOS directory layout?

Organize project docs by creating folders for standards, product, and spec layers, then add a dedicated directory for Beads task tracking and a root overview file to map the workspace.

Does this project structure support Beads task tracking?

Yes, the project structure includes a dedicated hidden directory specifically designed to integrate Beads task tracking directly within the repository alongside your specification layers.

When do I need a 3-layer spec layout for my software project?

You need a 3-layer spec layout when your software project requires strict separation between team standards, product context, and change proposals to maintain clear documentation.

What is the best way to separate standards, product context, and specifications in a repository?

The best way to separate these concerns is implementing the AgentOS 3-layer context model, which uses dedicated directories for standards, product, and spec documentation alongside a root overview file.