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 to DimOS, providing structured templates and schema definitions that guide AI coding agents through a proposal → specs/design/docs → tasks → apply workflow tailored to DimOS conventions. It also adds .opencode/ and .omo/ to .gitignore.

• openspec/config.yaml sets the active schema to dimos-capability and injects DimOS-specific context (stream types, blueprint terminology, Spec Protocol disambiguation) into every OpenSpec session.
• openspec/schemas/dimos-capability/schema.yaml defines five ordered artifacts (proposal, specs, design, docs, tasks) with explicit dependency chains and per-artifact instructions; an apply phase then drives task execution.
• Templates (proposal.md, spec.md, design.md, docs.md, tasks.md) provide skeleton markdown matching each artifact's section structure.

Confidence Score: 5/5

This PR adds only documentation templates, schema definitions, and two gitignore entries — no executable code or runtime logic is changed.

All changes are static configuration and markdown templates for the OpenSpec tooling scaffold. The artifact dependency chain in schema.yaml is internally consistent, template sections match their schema instructions, and the gitignore additions are scoped to tool-specific directories. Nothing here touches DimOS runtime behavior.

No files require special attention.

Important Files Changed

Filename	Overview
openspec/config.yaml	Top-level OpenSpec config binding the dimos-capability schema with DimOS-specific context strings and per-artifact rules; well-structured and consistent with schema.yaml.
openspec/schemas/dimos-capability/schema.yaml	Defines the five-artifact workflow (proposal → specs/design/docs → tasks) with correct dependency chains, template references, and an apply phase; no structural issues found.
openspec/schemas/dimos-capability/templates/spec.md	Spec template with ADDED Requirements section and GIVEN/WHEN/THEN scenario format; optional delta sections are grouped in a single comment block (previously flagged).
openspec/schemas/dimos-capability/templates/tasks.md	Task checklist template with checkbox format required by the apply phase; verification tasks cover openspec validation, pytest, docs checks, and manual QA.
.gitignore	Adds .opencode/ and .omo/ tool directories to gitignore; straightforward and correct.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[proposal\nproposal.md] --> B[specs\nspecs/**/*.md]
    A --> C[design\ndesign.md]
    A --> D[docs\ndocs.md]
    B --> E[tasks\ntasks.md]
    C --> E
    D --> E
    E --> F[apply\nExecute tasks.md checkboxes]

    style A fill:#4a90d9,color:#fff
    style B fill:#5ba05b,color:#fff
    style C fill:#5ba05b,color:#fff
    style D fill:#5ba05b,color:#fff
    style E fill:#d97a4a,color:#fff
    style F fill:#9b59b6,color:#fff

Loading

_{Reviews (2): 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.

📢 Thoughts on this report? Let us know!

[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.