# Od Next Strategy

> Bundled OD Next V2 strategy entrypoint for request-led planning and Build execution.

Bundled OD Next V2 strategy entrypoint for request-led planning and Build execution.

- Page: https://ss33.ai/skills/nexu-io/od-next-strategy-40209032459
- Publisher: nexu-io
- Category: [AI & Agents](https://ss33.ai/skills/category/ai-and-agents-y6jz7i) › [Orchestration & multi-agent](https://ss33.ai/skills/category/ai-and-agents-y6jz7i/orchestration-and-multi-agent-tlbx40)
- License: Apache-2.0
- Source: https://github.com/nexu-io/open-design/blob/78d5637cb49da07e81314d1544b5fc6d37c95084/plugins/_official/scenarios/od-next-strategy/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/nexu-io/od-next-strategy-40209032459

# OD Next Strategy V2

This bundled scenario packages the stable content used by the internal OD Next
planning and Build recipe. It is not a portable strategy selector and does not
activate itself.

When Open Design supplies a validated V2 binding, load the assets in this order:

1. `assets/core-system-prompt.md`
2. `assets/general-orchestration.md`
3. exactly one task profile selected through
   `references/task-profile-mapping.md`

A task profile may declare `resources` — non-prompt files such as the
prototype profile's handheld device shells under
`assets/task-profiles/prototype/device-frames/`. They enter the package
identity with their profile, are never concatenated into the prompt head, and
are staged by Open Design into the project directory (`.od-frames/`) for the
rule card to reference.

The Agent chooses whether the request needs a plan or direct work. The runtime
owns task state and session continuation. A ready plan ends with the current
host-keyed production-ready marker; no machine contract is required.