spec-treat

Run preflight, execution, and outcome write-back for CellmOS checks.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/murillodutt/cellm --skill spec-treat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-treat
Source: https://github.com/murillodutt/cellm/tree/main/cellm/skills/spec-treat
Command: npx skills add https://github.com/murillodutt/cellm --skill spec-treat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Treat a CellmOS check end-to-end with SCE preflight, execution loop, and write-back to maintain consistent spec state.

Core Features & Use Cases

  • Orchestrates preflight before each phase and ensures proper transitions with context_preflight, context_certify, and context_record_outcome.
  • Executes leaf tasks in order, persists outcomes, and handles quality_gate checks across the spec DAG.
  • Supports spec search, tree loading, and automated remediation within an orchestrated workflow.

Quick Start

Invoke the spec-treat skill to run an end-to-end check on a target spec, triggering preflight, execution, and outcome write-back.

Frequently Asked Questions about spec-treat

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

FAQPage Schema
How do I automate end-to-end spec checks across a spec tree?

End-to-end spec treatment runs preflight, execution, and outcome write-back to maintain consistent spec state. It automates CellmOS check processing by applying context_preflight, context_certify, context_record_outcome, and quality_gate within an orchestrated DAG.

How does preflight validation work before executing tasks in a spec DAG?

Preflight validation runs before each phase of spec execution to ensure proper transitions. It applies context_preflight and context_certify checks, verifying that the spec tree is ready before executing leaf tasks in order and persisting outcomes across the DAG.

Can I use quality_gate checks to validate outcomes during spec orchestration?

Yes, quality_gate checks are applied during spec orchestration to validate outcomes across the spec DAG. After executing leaf tasks and persisting state, the quality_gate ensures that each transition meets the required context_record_outcome criteria before proceeding.

What's the best way to persist state across transitions in an orchestrated spec workflow?

Persisting state across transitions in an orchestrated spec workflow requires running preflight before each phase, executing leaf tasks in order, and writing back outcomes. This end-to-end treatment applies context_preflight, context_certify, and quality_gate to maintain state consistency.

When do I need automated remediation within an orchestrated spec workflow?

Automated remediation is needed within an orchestrated spec workflow when diagnostic runs on individual specs detect issues during execution. The orchestration handles tree loading, spec search, and applies quality_gate checks to trigger remediation across the spec DAG.

Does spec-treat require dependencies to run diagnostic checks on individual specs?

No dependencies are required to run diagnostic checks on individual specs. The skill operates independently to orchestrate preflight, execution, and outcome write-back, applying context_preflight, context_certify, and quality_gate within an orchestrated DAG.