adding openspec scaffold

[TomCC7]

Problem

Adding a openspec (https://openspec.dev/) template for dimos.

Solution

Adds an openspec template to prompt agents to generate more dimos focused plans. Should be transparent to non-openspec users.

How to Test

Contributor License Agreement

• I have read and approved the CLA.

[greptile-apps]

Greptile Summary

This PR adds an OpenSpec scaffold (openspec/) to DimOS, providing a structured workflow schema and templates that guide AI coding agents in generating proposals, specs, design docs, documentation plans, and task checklists for DimOS changes. Two tool-generated directory patterns are also added to .gitignore.

• Introduces openspec/config.yaml with DimOS-specific context, terminology boundaries, and per-artifact authoring rules for the dimos-capability schema.
• Adds openspec/schemas/dimos-capability/schema.yaml defining the full proposal → specs/design/docs → tasks → apply artifact pipeline with instructions, dependency ordering, and template references.
• Provides five markdown templates (proposal.md, spec.md, design.md, docs.md, tasks.md) as starting points for each artifact type.

Confidence Score: 5/5

This PR adds only documentation scaffolding and tooling config files with no executable code changes; it is safe to merge.

All changes are markdown templates, YAML configuration, and .gitignore additions. Nothing in the diff touches runtime behaviour, APIs, or build artifacts. The schema dependency ordering (proposal → specs/design/docs → tasks → apply) is internally consistent, and the per-artifact instructions align with the templates.

No files require special attention.

Important Files Changed

Filename	Overview
.gitignore	Adds .opencode/ and .omo/ to the ignore list; straightforward tooling entries with no issues.
openspec/config.yaml	Project-level OpenSpec configuration with context block, terminology boundary, and per-artifact authoring rules; well-aligned with the schema and templates.
openspec/schemas/dimos-capability/schema.yaml	Defines the five-artifact workflow with correct dependency ordering and detailed instructions; no structural issues found.
openspec/schemas/dimos-capability/templates/spec.md	Spec template with ADDED Requirements section and a single scenario block; optional delta sections are grouped in one comment (addressed in prior review thread).
openspec/schemas/dimos-capability/templates/tasks.md	Tasks template with three numbered sections and checkbox format required by the apply phase parser; aligns with schema instructions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[proposal.md] --> B[specs/**/*.md]
    A --> C[design.md]
    A --> D[docs.md]
    B --> E[tasks.md]
    C --> E
    D --> E
    E --> F[apply phase\ntracks tasks.md]

    style A fill:#d0e8ff,stroke:#336
    style B fill:#d0ffd8,stroke:#363
    style C fill:#d0ffd8,stroke:#363
    style D fill:#d0ffd8,stroke:#363
    style E fill:#fff0c0,stroke:#663
    style F fill:#ffd8d8,stroke:#633

Loading

_{Reviews (3): Last reviewed commit: "Merge branch 'main' into cc/feat/openspe..." | Re-trigger Greptile}

[greptile-apps]

The three optional delta sections are all wrapped inside a single HTML comment block. A user who wants to add a ## MODIFIED Requirements section has to manually cut it out of the surrounding comment rather than just deleting the comment delimiters for that one section. Splitting them into individual comments makes each section independently removable.

Suggested change

	<!-- Optional sections for deltas:
	## MODIFIED Requirements
	## REMOVED Requirements
	## RENAMED Requirements
	-->
	<!-- ## MODIFIED Requirements -->
	<!-- ## REMOVED Requirements -->
	<!-- ## RENAMED Requirements -->

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Flag	Coverage Δ
OS-ubuntu-24.04-arm	64.88% <ø> (+<0.01%)	⬆️
OS-ubuntu-latest	65.79% <ø> (+<0.01%)	⬆️
Py-3.10	65.78% <ø> (-0.01%)	⬇️
Py-3.11	65.78% <ø> (+<0.01%)	⬆️
Py-3.12	65.78% <ø> (+<0.01%)	⬆️
Py-3.13	65.78% <ø> (+<0.01%)	⬆️
Py-3.14	65.79% <ø> (+<0.01%)	⬆️
Py-3.14t	65.77% <ø> (-0.01%)	⬇️
SelfHosted-Large	30.62% <ø> (+<0.01%)	⬆️
SelfHosted-Linux	38.36% <ø> (-0.01%)	⬇️
SelfHosted-macOS	37.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[leshy]

I don't know what this is? can you demo to us or something? many of us have our own private scaffolding like this I assume

[TomCC7]

I don't know what this is? can you demo to us or something? many of us have our own private scaffolding like this I assume

Yes I can demo this tomorrow during the manipulation meeting.