@aidecisionops/decisionops 0.1.0

package/platforms/antigravity.toml

@@ -0,0 +1,29 @@
+id = "antigravity"
+display_name = "Antigravity"
+
+[skill]
+supported = true
+build_path = "skills/{skill_name}"
+install_root_env = "ANTIGRAVITY_SKILLS_DIR"
+install_root_default = "~/.antigravity/skills"
+install_path_suffix = "{skill_name}"
+
+[mcp]
+supported = true
+scope = "user"
+format = "json_map"
+root_key = "mcpServers"
+build_path = "mcpServers.json"
+install_path_env = "ANTIGRAVITY_MCP_CONFIG_PATH"
+
+[manifest]
+supported = true
+build_path = ".decisionops/manifest.toml"
+
+[auth]
+mode = "interactive_handoff"
+instructions = [
+  "Open {display_name} MCP settings and verify server '{mcp_server_name}' exists at '{mcp_server_url}'.",
+  "Invoke any Decision Ops MCP tool to trigger interactive login/consent.",
+  "Complete the prompted authentication flow, then retry the same MCP tool call.",
+]

package/platforms/claude-code.toml

@@ -0,0 +1,30 @@
+id = "claude-code"
+display_name = "Claude Code"
+
+[skill]
+supported = true
+build_path = "skills/{skill_name}"
+install_root_env = "CLAUDE_SKILLS_DIR"
+install_root_default = "~/.claude/skills"
+install_path_suffix = "{skill_name}"
+
+[mcp]
+supported = true
+scope = "project"
+format = "json_map"
+root_key = "mcpServers"
+build_path = ".mcp.json"
+install_path_env = "CLAUDE_MCP_CONFIG_PATH"
+install_path_default = "{repo_path}/.mcp.json"
+
+[manifest]
+supported = true
+build_path = ".decisionops/manifest.toml"
+
+[auth]
+mode = "interactive_handoff"
+instructions = [
+  "Open {display_name} MCP settings and verify server '{mcp_server_name}' exists at '{mcp_server_url}'.",
+  "Invoke any Decision Ops MCP tool to trigger interactive login/consent.",
+  "Complete the prompted authentication flow, then retry the same MCP tool call.",
+]

package/platforms/codex.toml

@@ -0,0 +1,31 @@
+id = "codex"
+display_name = "Codex"
+
+[skill]
+supported = true
+build_path = "skills/{skill_name}"
+install_root_env = "CODEX_HOME"
+install_root_default = "~/.codex"
+install_path_suffix = "skills/{skill_name}"
+
+[mcp]
+supported = true
+scope = "user"
+format = "codex_toml"
+build_path = "config.toml"
+install_path_env = "CODEX_CONFIG_PATH"
+install_root_env = "CODEX_HOME"
+install_root_default = "~/.codex"
+install_path_suffix = "config.toml"
+
+[manifest]
+supported = true
+build_path = ".decisionops/manifest.toml"
+
+[auth]
+mode = "interactive_handoff"
+instructions = [
+  "Open {display_name} MCP settings and verify server '{mcp_server_name}' exists at '{mcp_server_url}'.",
+  "Invoke any Decision Ops MCP tool to trigger interactive login/consent.",
+  "Complete the prompted authentication flow, then retry the same MCP tool call.",
+]

package/platforms/cursor.toml

@@ -0,0 +1,30 @@
+id = "cursor"
+display_name = "Cursor"
+
+[skill]
+supported = true
+build_path = "skills/{skill_name}"
+install_root_env = "CURSOR_SKILLS_DIR"
+install_root_default = "~/.cursor/skills"
+install_path_suffix = "{skill_name}"
+
+[mcp]
+supported = true
+scope = "project"
+format = "json_map"
+root_key = "mcpServers"
+build_path = ".cursor/mcp.json"
+install_path_env = "CURSOR_MCP_CONFIG_PATH"
+install_path_default = "{repo_path}/.cursor/mcp.json"
+
+[manifest]
+supported = true
+build_path = ".decisionops/manifest.toml"
+
+[auth]
+mode = "interactive_handoff"
+instructions = [
+  "Open {display_name} MCP settings and verify server '{mcp_server_name}' exists at '{mcp_server_url}'.",
+  "Invoke any Decision Ops MCP tool to trigger interactive login/consent.",
+  "Complete the prompted authentication flow, then retry the same MCP tool call.",
+]

package/platforms/vscode.toml

@@ -0,0 +1,26 @@
+id = "vscode"
+display_name = "VS Code"
+
+[skill]
+supported = false
+
+[mcp]
+supported = true
+scope = "project"
+format = "json_map"
+root_key = "servers"
+build_path = ".vscode/mcp.json"
+install_path_env = "VSCODE_MCP_CONFIG_PATH"
+install_path_default = "{repo_path}/.vscode/mcp.json"
+
+[manifest]
+supported = true
+build_path = ".decisionops/manifest.toml"
+
+[auth]
+mode = "interactive_handoff"
+instructions = [
+  "Open {display_name} MCP settings and verify server '{mcp_server_name}' exists at '{mcp_server_url}'.",
+  "Invoke any Decision Ops MCP tool to trigger interactive login/consent.",
+  "Complete the prompted authentication flow, then retry the same MCP tool call.",
+]

package/skills/decision-ops/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: decision-ops
+description: "Use this skill when a prompt implies a meaningful product, technical, or business tradeoff and the user needs project rationale captured or retrieved in Decision Ops. Trigger on prompts like 'should we...', 'which option...', 'choose between...', 'prioritize...', 'what should we cut', 'descope', 'migrate to...', 'how should we release this', 'staged rollout', 'change pricing/onboarding/KPIs', 'improve reliability/performance/security', 'change vendors', 'select a partner', 'allocate budget', 'change revenue model', 'enter new market', 'change go-to-market', or 'compliance requirement'. Skip typo fixes, doc spelling, pure reformatting, and version bumps with no architectural choice."
+compatibility: "Requires repository-local files and network access to the Decision Ops MCP service at https://api.aidecisionops.com/mcp."
+metadata:
+  maturity: "stable"
+---
+
+# Decision Ops
+
+This skill teaches AI coding agents when and how to log decisions. The canonical decision store is the DecisionOps MCP service — not a local markdown file.
+
+## Local Manifest Binding
+
+For IDE-driven usage, prefer a repository-local manifest at `.decisionops/manifest.toml`.
+
+- Read it first when present by running `scripts/read-manifest.sh <repo-path>` from the installed skill directory.
+- Required fields:
+  - `org_id`
+  - `project_id`
+  - `repo_ref`
+- Recommended fields:
+  - `default_branch`
+  - `mcp_server_name`
+  - `mcp_server_url`
+  - `repo_id` (optional local hint only; do not require it)
+- Treat the manifest as local binding/config only. The MCP service remains the canonical system of record.
+- If the manifest and central gate resolve to different org/project/repo values, stop and ask the user which context is correct before writing anything.
+
+## Workflow
+
+Use this workflow only when the task includes an explicit, non-trivial product, technical, or business tradeoff worth recording.
+
+1. Run the one-step gate.
+- If `.decisionops/manifest.toml` exists, read it first and use `repo_ref` plus `default_branch` as the preferred local binding context.
+- Call `do-prepare-decision-gate` to resolve project context and classify whether the task is recordable.
+- If central repository resolution fails but the manifest contains `org_id` and `project_id`, continue in manifest-bound mode and say so explicitly.
+- Show one user prompt with resolved `org/project/repo/branch`, the classification reason, and the choices `Quick`, `Comprehensive`, `Skip`, or `Other`.
+
+2. Gather evidence for the selected mode.
+- `Skip`: stop decision flow and continue implementation without a decision write.
+- `Quick`: fetch up to 3 relevant prior decisions.
+- `Comprehensive`: fetch up to 5 relevant prior decisions, including supersede candidates and prior outcomes.
+- `Other`: require brief custom instructions, then map them to explicit search and evaluation parameters.
+
+3. Evaluate options before acting.
+- Record at least 2 viable options, or include an explicit single-option justification.
+- Compare user impact, execution risk, reversibility, and hard constraints.
+- Choose and implement the preferred option.
+
+4. Validate the draft before publish.
+- Create the draft with `do-create-decision-draft`.
+- Run `do-validate-decision`.
+- Fix validation failures before publishing.
+
+5. Publish and trace the outcome.
+- Publish with `do-publish-decision`.
+- Apply supersede updates atomically where declared.
+- Return `decision_id` and reference it in PR or commit metadata.
+
+## Decision Triggers
+
+Record a decision when at least one of these is true:
+- Introduce, remove, or significantly upgrade a dependency, platform, or provider.
+- Change API shape, integration contract, schema, storage model, or data retention behavior.
+- Choose between non-trivial product directions (pricing, onboarding flow, rollout strategy, support model).
+- Adopt, defer, or waive a security/compliance/reliability control.
+- Set a non-obvious testing or release strategy with explicit risk tradeoffs.
+- Select, change, or terminate a vendor, supplier, or strategic partner.
+- Make a significant budget, headcount, or resource allocation decision.
+- Commit to a legal, contractual, or regulatory obligation, or change go-to-market strategy, customer segmentation, or revenue model.
+
+## Assumptions and Defaults
+
+- Central service is the only canonical source.
+- Local manifest is an optional binding layer for IDE/repository setup.
+- One-step gate is shown for every recordable decision attempt.
+- User chooses mode each time (`Quick|Comprehensive|Skip|Other`).
+- `Other` requires custom instructions and then continues.
+- Decision flow is fail-closed when validation fails. Project resolution may fall back to the local manifest when present.
+- PR/commit traceability must include `decision_id`.
+
+## References
+
+- Use the manifest contract in [references/decision-ops-manifest.md](references/decision-ops-manifest.md).
+- Use the MCP lifecycle contract in [references/mcp-interface.md](references/mcp-interface.md).
+- Use the markdown structure in [references/decision-register-format.md](references/decision-register-format.md).
+- Use the evaluation assets in [evals/trigger-queries.json](evals/trigger-queries.json) and [evals/evals.json](evals/evals.json) when validating activation and outcome quality.

package/skills/decision-ops/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Decision Ops"
+  short_description: "Capture repo rationale from tradeoff-heavy prompts."
+  default_prompt: "When a prompt implies a meaningful product, technical, or business tradeoff, use $decision-ops. First check for .decisionops/manifest.toml in the target repository and, when present, read it with scripts/read-manifest.sh from the installed skill directory. Use the manifest as the local binding context, then run a one-step gate that presents resolved org/project/repo/branch and asks Quick, Comprehensive, Skip, or Other. If do-prepare-decision-gate fails because the repo is not mapped centrally but the manifest provides org_id and project_id, continue in manifest-bound mode and say so explicitly. For Quick, Comprehensive, or Other, use the central MCP lifecycle: do-prepare-decision-gate -> do-search-decisions -> do-create-decision-draft -> do-validate-decision -> do-publish-decision -> do-get-decision, then return decision_id for PR/commit traceability."

package/skills/decision-ops/evals/evals.json

@@ -0,0 +1,87 @@
+{
+  "version": 1,
+  "methodology": {
+    "baseline": "Run each case without explicitly invoking $decision-ops and capture the output.",
+    "with_skill": "Run the same case with $decision-ops active and compare the result against the baseline output.",
+    "grader": "Use automated rubric checks when the expected behavior is deterministic. Keep human review for activation quality, missing context, and decision quality.",
+    "metrics": [
+      "activation_precision",
+      "activation_recall",
+      "workflow_fidelity",
+      "decision_quality",
+      "baseline_delta",
+      "latency",
+      "tokens"
+    ]
+  },
+  "cases": [
+    {
+      "id": "recordable-quick-rollout",
+      "task": "We need to choose whether to release a new pricing page behind a feature flag or switch all users at once. Review prior decisions, decide on a rollout, and prepare the decision draft.",
+      "expected_behavior": [
+        "Classifies the task as recordable.",
+        "Reads .decisionops/manifest.toml when present before calling the central lifecycle.",
+        "Shows or describes the one-step gate with Quick, Comprehensive, Skip, or Other choices.",
+        "Compares at least two rollout options before deciding.",
+        "Returns or references decision_id after a successful publish."
+      ],
+      "rubric": [
+        "Captures context, options, decision, and consequences clearly.",
+        "Uses the documented MCP lifecycle in the correct order.",
+        "Does not claim local markdown is the canonical store."
+      ],
+      "compare_to_baseline": true,
+      "requires_human_review": true
+    },
+    {
+      "id": "recordable-compliance-retention",
+      "task": "A new enterprise contract may require us to retain audit exports for one year instead of 30 days. Evaluate options, highlight compliance risk, and draft the decision.",
+      "expected_behavior": [
+        "Classifies the task as recordable.",
+        "Surfaces hard constraints such as compliance or legal obligations.",
+        "Compares retention options with reversibility and operational cost.",
+        "Produces a validation plan with metric, baseline, target, and by_date.",
+        "Fails closed if validation errors remain."
+      ],
+      "rubric": [
+        "Calls out compliance as a hard constraint rather than a soft preference.",
+        "Makes the tradeoff between storage cost and contractual risk explicit.",
+        "Uses single-option justification only if multiple viable options do not exist."
+      ],
+      "compare_to_baseline": true,
+      "requires_human_review": true
+    },
+    {
+      "id": "manifest-bound-fallback",
+      "task": "Choose whether to move from Elasticsearch to OpenSearch when the repository is not mapped centrally but a valid .decisionops/manifest.toml exists.",
+      "expected_behavior": [
+        "Explains that central repository resolution failed.",
+        "Continues in manifest-bound mode using org_id and project_id from the manifest.",
+        "Keeps the canonical store as the central MCP lifecycle rather than a local markdown fallback.",
+        "Compares at least two viable options before deciding."
+      ],
+      "rubric": [
+        "States manifest-bound mode explicitly.",
+        "Preserves the normal workflow after fallback.",
+        "Avoids silent context drift between manifest and central state."
+      ],
+      "compare_to_baseline": true,
+      "requires_human_review": true
+    },
+    {
+      "id": "non-recordable-typo",
+      "task": "Fix the typo in docs/getting-started.md and do not create a decision entry.",
+      "expected_behavior": [
+        "Classifies the task as non-recordable or selects Skip.",
+        "Does not attempt the central write lifecycle.",
+        "Continues with the implementation without decision output."
+      ],
+      "rubric": [
+        "Avoids false-positive activation.",
+        "Keeps the response brief and task-focused."
+      ],
+      "compare_to_baseline": true,
+      "requires_human_review": false
+    }
+  ]
+}

package/skills/decision-ops/evals/trigger-queries.json

@@ -0,0 +1,108 @@
+{
+  "version": 1,
+  "description": "Representative activation checks for the decision-ops skill. Positive cases should trigger the skill; negative cases should not.",
+  "positive": [
+    {
+      "id": "trigger-001",
+      "prompt": "Should we migrate from self-hosted Postgres to a managed database for our analytics service?",
+      "why": "Infrastructure migration with cost, reliability, and operational tradeoffs."
+    },
+    {
+      "id": "trigger-002",
+      "prompt": "Which rollout strategy should we use for the new pricing page: staged rollout or full launch?",
+      "why": "Release strategy with explicit product and risk tradeoffs."
+    },
+    {
+      "id": "trigger-003",
+      "prompt": "Choose between Stripe Billing and a custom invoicing flow for enterprise contracts.",
+      "why": "Vendor and operating-model decision."
+    },
+    {
+      "id": "trigger-004",
+      "prompt": "We need to prioritize either SOC 2 logging work or performance optimization this quarter. What should we cut?",
+      "why": "Resource allocation with compliance and customer impact implications."
+    },
+    {
+      "id": "trigger-005",
+      "prompt": "Should we keep the current onboarding flow or add an approval gate for regulated customers?",
+      "why": "Product and compliance tradeoff."
+    },
+    {
+      "id": "trigger-006",
+      "prompt": "Which option is better for search: stay on Elasticsearch or move to OpenSearch?",
+      "why": "Platform or provider choice with migration cost and reliability impact."
+    },
+    {
+      "id": "trigger-007",
+      "prompt": "How should we release the new audit log export feature without breaking existing customer workflows?",
+      "why": "Release strategy with customer-impact tradeoffs."
+    },
+    {
+      "id": "trigger-008",
+      "prompt": "Should we store customer documents for 30 days or 1 year to satisfy the new contract?",
+      "why": "Data-retention and legal obligation decision."
+    },
+    {
+      "id": "trigger-009",
+      "prompt": "Select a partner for KYC verification and explain the tradeoffs.",
+      "why": "Partner selection with compliance and cost implications."
+    },
+    {
+      "id": "trigger-010",
+      "prompt": "Do we keep the current monolith for another year or start a staged migration to services?",
+      "why": "Architecture and rollout decision."
+    }
+  ],
+  "negative": [
+    {
+      "id": "skip-001",
+      "prompt": "Fix the typo in the README heading.",
+      "why": "Trivial documentation edit with no meaningful tradeoff."
+    },
+    {
+      "id": "skip-002",
+      "prompt": "Rename this variable to match our lint rule.",
+      "why": "Local code cleanup only."
+    },
+    {
+      "id": "skip-003",
+      "prompt": "Reformat this file with prettier.",
+      "why": "Pure formatting task."
+    },
+    {
+      "id": "skip-004",
+      "prompt": "Bump the patch version of a dependency with no behavior change.",
+      "why": "Routine version maintenance without an architectural choice."
+    },
+    {
+      "id": "skip-005",
+      "prompt": "Translate this paragraph into Spanish.",
+      "why": "Non-decision content transformation."
+    },
+    {
+      "id": "skip-006",
+      "prompt": "Summarize the last team meeting notes.",
+      "why": "Summarization only."
+    },
+    {
+      "id": "skip-007",
+      "prompt": "Add a missing semicolon in src/cli.ts.",
+      "why": "Tiny code fix without tradeoff analysis."
+    },
+    {
+      "id": "skip-008",
+      "prompt": "Generate release notes from these commits.",
+      "why": "Documentation task unless the user asks for a release strategy decision."
+    },
+    {
+      "id": "skip-009",
+      "prompt": "Update the CONTRIBUTING guide to mention Node 20.",
+      "why": "Documentation update without a decision to record."
+    },
+    {
+      "id": "skip-010",
+      "prompt": "Sort these imports and remove unused ones.",
+      "why": "Mechanical code hygiene."
+    }
+  ]
+}

package/skills/decision-ops/references/decision-ops-manifest.md

@@ -0,0 +1,35 @@
+# Decision Ops Manifest
+
+Use `.decisionops/manifest.toml` in the target repository root to bind a local repository to central Decision Ops identifiers.
+
+## Required fields
+
+- `org_id`
+- `project_id`
+- `repo_ref`
+
+## Recommended fields
+
+- `default_branch`
+- `mcp_server_name`
+- `mcp_server_url`
+- `repo_id` (optional local hint; current MCP workflow should not require it)
+
+## Example
+
+```toml
+version = 1
+org_id = "org_123"
+project_id = "proj_456"
+repo_ref = "decisionops/decision-ops-skill"
+default_branch = "main"
+mcp_server_name = "decision-ops-mcp"
+mcp_server_url = "https://api.aidecisionops.com/mcp"
+```
+
+## Behavior
+
+- The manifest is local configuration, not the canonical decision register.
+- Agents should read the manifest before calling the central MCP lifecycle.
+- If central gate resolution succeeds, agents should compare the resolved context against the manifest.
+- If central gate resolution fails because the repo is unknown, agents may continue with manifest `org_id` and `project_id` for MCP read/write calls and should say that they are in manifest-bound mode.

package/skills/decision-ops/references/decision-register-format.md

@@ -0,0 +1,36 @@
+# Decision Register Format
+
+Use this structure for entries in `docs/decision-register.md` or the repository's chosen register path.
+It applies to both product and technical decisions.
+
+## Entry Template
+
+```markdown
+## DR-YYYYMMDD-HHMM-short-slug: Decision title
+- Date: YYYY-MM-DD
+- Status: Accepted
+- Related: <optional file paths, ticket IDs, URLs>
+
+### Context
+Problem statement, constraints, and why a decision is needed now.
+
+### Options Considered
+- Option A
+- Option B
+
+### Decision
+Chosen option and enough implementation detail for future contributors.
+
+### Consequences
+- Positive impact
+- Tradeoff or operational cost
+```
+
+## Authoring Rules
+
+- Use one canonical register file per repository.
+- Record product and technical decisions in the same register to preserve sequencing and rationale.
+- Keep titles concise and specific.
+- Explain tradeoffs, not just outcomes.
+- Add `Related` links when code paths, incidents, tickets, or benchmarks exist.
+- Update status to `Superseded` when later decisions replace older entries.

package/skills/decision-ops/references/mcp-interface.md

@@ -0,0 +1,100 @@
+# Decision Ops MCP Interface
+
+Use this reference only when you need the exact payload shape or error contract for the central MCP lifecycle.
+
+## Public APIs / Tools
+
+`do-prepare-decision-gate`
+- Purpose: combine project resolution and decision classification for one-step user prompting.
+- Input:
+  - `repo_ref` (path or URL)
+  - `branch`
+  - `task_summary`
+  - `changed_paths` (optional)
+- Output:
+  - `org_id`, `project_id`, `repo`, `branch`
+  - `recordable` (bool)
+  - `classification_reason`
+  - `tags[]`
+  - `risk_level` (`low|medium|high`)
+  - `suggested_mode` (`quick|comprehensive`)
+  - `canonical_store` = `central`
+
+`do-search-decisions`
+- Input:
+  - `org_id`, `project_id`
+  - `terms` (array)
+  - `mode` (`quick|comprehensive|custom`)
+  - `limit` (default `3` for quick, `5` for comprehensive)
+  - `include_body` (default `false` for quick, `true` for comprehensive)
+  - `custom` (object; optional, used when `mode=custom`)
+- Output:
+  - `items[]` with `id`, `title`, `status`, `date`, `score`, `snippet`, `superseded_by`, `related[]`
+  - `candidate_supersedes[]`
+
+`do-create-decision-draft`
+- Input:
+  - `org_id`, `project_id`
+  - `title`, `context`, `decision`
+  - `options`, `consequences`, `related` (arrays)
+  - `supersedes` (array)
+  - `single_option_justification` (string; required when only one option is supplied)
+  - `validation_plan` (`metric`, `baseline`, `target`, `by_date`)
+- Output:
+  - `decision_id`, `version`, `status` (`Proposed`)
+
+`do-validate-decision`
+- Input:
+  - `org_id`, `project_id`
+  - `decision_id` (string; optional when `draft` is provided)
+  - `draft` (object; optional when `decision_id` is provided)
+- Output:
+  - `valid` (bool)
+  - `errors[]` (`code`, `field`, `message`)
+  - `warnings[]`
+
+`do-publish-decision`
+- Input:
+  - `org_id`, `project_id`, `decision_id`, `expected_version`
+- Output:
+  - `decision_id`, `status` (`Accepted`)
+  - `supersede_updates[]` (`old_id -> Superseded by <new_id>`)
+  - `published_at`
+
+`do-get-decision`
+- Read-only API.
+- Input: `org_id`, `project_id`, `decision_id`
+- Output: full `DecisionRecord`
+
+## Public Types
+
+`DecisionRecord`
+- `id`, `org_id`, `project_id`, `repo`, `branch`
+- `title`, `status` (`Proposed|Accepted|Superseded|Rejected`)
+- `context`, `decision`
+- `options[]`, `consequences[]`, `related[]`
+- `supersedes[]`
+- `validation_plan` (`metric`, `baseline`, `target`, `by_date`)
+- `created_by`, `created_at`, `updated_at`, `version`
+
+## Error Contract
+
+- `AUTH_REQUIRED`
+- `PROJECT_NOT_FOUND`
+- `VALIDATION_FAILED`
+- `VERSION_CONFLICT`
+- `NOT_FOUND`
+- `RATE_LIMITED`
+
+## Evaluation Scenarios
+
+Use these scenarios when reviewing output quality:
+
+1. Non-recordable task returns `recordable=false`; selecting `Skip` performs no writes.
+2. Recordable task with `Quick` fetches at most 3 summaries and publishes successfully.
+3. Recordable task with `Comprehensive` fetches full entries, identifies supersede candidates, and publishes with atomic supersede updates.
+4. `Other` requires custom instructions; those instructions alter search and evaluation parameters for that run only.
+5. Wrong project context is caught at gate display before draft creation.
+6. Validation failure blocks publish until corrected.
+7. Version conflict on publish requires retry with the latest version.
+8. `do-get-decision` remains read-only and never creates records.