od-new-generation by nexu-io

Decision brief

What it does—and where it fits

Spec §10.1 / §23.3.3: when a plugin omits od.pipeline, the daemon falls back to this scenario plugin's pipeline. Replacing the default for an enterprise / vertical edition is now a content edit rather than a code change.

Best for

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-new-generation"

Safe inspection promptEditorial

Inspect the Agent Skill "od-new-generation" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/scenarios/od-new-generation/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Default pipeline
The discovery stage gives the agent a clean surface for clarifying questions; the plan stage commits to a TodoWrite-backed plan; the generate stage produces the artifact; the critique stage devloops until the score converges or the iteration ceiling is hit.
The discovery stage gives the agent a clean surface for clarifying questions; the plan stage commits to a TodoWrite-backed plan; the generate stage produces the artifact; the critique stage devloops until the score conv…
02
Plugins that customise this scenario
A plugin can override or extend by declaring its own od.pipeline. The default applies only when the plugin's pipeline is absent.
A plugin can override or extend by declaring its own od.pipeline. The default applies only when the plugin's pipeline is absent.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	55/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	82,073	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	catalog record	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: plugins/_official/scenarios/od-new-generation/SKILL.md
Commit: 89d6d4ef21baf80f871595abdf6f7de6e941dd44
License: Apache-2.0
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

od-new-generation (scenario)

Spec §10.1 / §23.3.3: when a plugin omits od.pipeline, the daemon falls back to this scenario plugin's pipeline. Replacing the default for an enterprise / vertical edition is now a content edit rather than a code change.

Default pipeline

{
  "stages": [
    { "id": "discovery", "atoms": ["discovery-question-form"] },
    { "id": "plan",      "atoms": ["direction-picker", "todo-write"] },
    { "id": "generate",  "atoms": ["file-write", "live-artifact"] },
    {
      "id": "critique", "atoms": ["critique-theater"],
      "repeat": true,
      "until": "critique.score>=4 || iterations>=3"
    }
  ]
}

The discovery stage gives the agent a clean surface for clarifying questions; the plan stage commits to a TodoWrite-backed plan; the generate stage produces the artifact; the critique stage devloops until the score converges or the iteration ceiling is hit.

Plugins that customise this scenario

A plugin can override or extend by declaring its own od.pipeline. The default applies only when the plugin's pipeline is absent.