Skip to content

Feature:

Status: Draft

Release Target: Unassigned

Problem

What workflow, safety risk, maintainability gap, or evidence gap does this feature address?

Rationale

Why is this feature worth doing for this repo now or later? Explain the connection to the roadmap themes and the tradeoff it improves.

Target Users

Who benefits from the change? Name the primary users and the workflow they are trying to complete.

Non-Goals

What should this feature explicitly not do?

Current Behavior And Evidence

List the current commands, files, docs, tests, issues, review notes, or runtime evidence that define the starting point.

Proposed Behavior

Describe the desired behavior from the user's point of view. Include command shape, outputs, generated artifacts, and failure behavior where relevant.

CLI, Docs, And API Impact

List command changes, option changes, JSON/report schema changes, compatibility wrappers, documentation updates, and release-note requirements.

Data And Credential Safety

Describe whether the feature reads or writes private model data, runtime service data, credentials, diagnostics, reports, run logs, or curated public examples. State the safety guardrails.

Validation Plan

List deterministic checks, docs checks, workflow checks, share checks, live evals, manual demos, or diagnostics evidence required before the work is done.

Acceptance Criteria

  • Criterion 1.
  • Criterion 2.
  • Criterion 3.

Rollout And Compatibility Notes

State whether the change is additive, warned-but-allowed, breaking, or gated by an explicit flag. Include migration notes for existing users if needed.

Open Decisions

  • Decision 1.
  • Decision 2.