spec:project-structure

Name: spec:project-structure
Availability: InStock
Author: Martinffx

Organize project directories using the AgentOS 3-layer context model.

39|4|Updated Jan 11, 2026

Search Tags:#documentation #agentos #software-engineering #project-structure #spec-driven-development #directory-structure #beads-tracking

Ready to run

npx skills add https://github.com/martinffx/atelier --skill spec-project-structure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec:project-structure
Source: https://github.com/martinffx/atelier/tree/main/skills/spec%3Aproject-structure
Command: npx skills add https://github.com/martinffx/atelier --skill spec-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized directory layout to organize project documentation, change proposals, and task tracking using the AgentOS 3-layer context model.

Core Features & Use Cases

Defines a clear separation between standards (docs/standards), product context (docs/product), and specs (docs/spec), plus a Beads workspace (.beads) and project overview (CLAUDE.md).
Enables consistent documentation practices, change workflows, and dependency-aware task planning for both greenfield and brownfield projects.

Quick Start

Organize a new project using the AgentOS 3-layer structure in a project/ directory.

Frequently Asked Questions about spec:project-structure

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

FAQPage Schema

How do I organize project documentation for spec-driven development?▼

You can organize project documentation for spec-driven development by adopting the AgentOS 3-layer context model, which separates standards, product context, and specs into distinct directories.

What is the AgentOS 3-layer context model for directory structure?▼

The AgentOS 3-layer context model is a directory structure framework that separates project standards, product context, and specifications, while integrating a Beads task tracker and a project overview file.

Can I apply a spec-driven project structure to an existing brownfield codebase?▼

Yes, you can apply this spec-driven project structure to both greenfield and brownfield projects to establish clear documentation separation and dependency-aware task tracking workflows.

How do I set up a Beads task tracker workspace in my project?▼

You set up a Beads task tracker workspace by creating a .beads directory within your project root, enabling dependency-aware task planning alongside your organized documentation folders.

What's the best way to separate product context from technical standards in a project?▼

The best way to separate product context from technical standards is using a structured directory layout, placing them in docs/product and docs/standards respectively, with specs in docs/spec.

Why do I need a CLAUDE.md project overview file?▼

You need a CLAUDE.md project overview file to provide a centralized overview of the project, complementing the 3-layer documentation structure and the Beads task tracking workspace.