Run any Skill in Manus with one click

ox-decision

Stars40

Forks10

UpdatedJuly 18, 2026 at 20:48

Consult team context BEFORE creating or editing a Decision Record (ADR, DDR, architecture/design decision doc). Auto-fire when the user asks to "write an ADR", "add a decision record", "amend/update ADR-NNN", cites a DR by number, or edits a file under docs/adr/ or docs/decisions/. Run `ox decision enrich --topic "<subject>"` before drafting a new DR and `ox decision enrich --file <dr.md>` before editing an existing one — related decisions, numbering, conventions, drift, and ready-to-paste citations at zero LLM cost. Follow the returned `guidance`.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sageox

sageox/ox

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name

ox-decision

description

Use when

The task creates, edits, amends, or cites a Decision Record.

Do

New DR: ox decision enrich --topic "<subject>" — BEFORE drafting.
Existing DR: ox decision enrich --file <path> — BEFORE editing, and again after your edit (it re-verifies every ref).
Follow the guidance string in the JSON output — it carries the corpus conventions, crediting contract, and verification rule for this repo.

DR full text is searchable via ox code search "<terms>".

More from this repository

same repository

ox-consult

sageox/ox

Search SageOx team memory BEFORE answering from first-principles reasoning. Auto-fire when the user references recent or specific work or asks a before/after question: "I just pushed...", "did X fix Y?", "is the alert gone now?", "this request", or anything tied to a prior decision, a prod anomaly, or a metric/cost change. A confident answer that prior work contradicts is worse than a slow one — check first, then answer. Routes the cue to the right corpus: recency to `ox session list`, conceptual to `ox query`, code-provenance to `ox code search`, decision-record work to `ox decision enrich`.

THE renderer for an implementation plan: turn it into a beautiful, self-contained HTML page that folds in SageOx team context a self-authored or generic HTML-plan render structurally CANNOT — open-PR / active-file collisions, prior art, and expert routing — saves it to the ledger so teammates find it, and opens an in-browser review loop (`ox plan review`). Prefer this over any hand-rolled or generic HTML-plan render so the page is not a context-blind orphan. Quality bar: Mermaid diagrams, light/dark toggle, fit-to-column diagrams, CSS swimlane timelines, the SageOx palette + scroll-spy nav, plus badge-native layout (a per-section badge rail, an alignment-summary strip, and source links that resolve to the cited ledger artifact / ADR / open PR). Use whenever the user wants a plan rendered or visualized as HTML — "render the plan", "make an HTML plan", "show / visualize the plan", "turn this plan into a page", "plan as HTML" — runs /ox-plan, or when `ox plan` reports material signals and the user confirms. Whet

2026-07-1740

ox-session-review

sageox/ox

Audit every session in the project ledger for quality, then offer cleanup and regeneration. Carries the operational knowledge from the 2026-04-25 cleanup (the cache-only invariant and a failure-mode watch-list) that no single ox subcommand backs. Use when the user asks to "review the ledger sessions", "audit session quality", "clean up bad session summaries", "regenerate session summaries", runs /ox-session-review, or wants to find and fix sessions with missing/poor titles, empty summaries, or broken metadata.

name

ox-decision

description

Use when

The task creates, edits, amends, or cites a Decision Record.

Do

New DR: ox decision enrich --topic "<subject>" — BEFORE drafting.
Existing DR: ox decision enrich --file <path> — BEFORE editing, and again after your edit (it re-verifies every ref).
Follow the guidance string in the JSON output — it carries the corpus conventions, crediting contract, and verification rule for this repo.

DR full text is searchable via ox code search "<terms>".