spec:project-structure

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.

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.

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.

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.

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.

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.