---
title: OKSTRA Change Impact Analysis Input - {{TASK_KEY}}
id: {{FM_ID}}
tags: {{FM_TAGS}}
status: ready-for-agent
aliases: {{FM_ALIASES}}
date: {{TASK_DATE}}
task-id: "{{TASK_ID}}"
task-group: "{{TASK_GROUP}}"
project-id: "{{PROJECT_ID}}"
taskType: "{{FM_TASK_TYPE}}"
---

# OKSTRA Change Impact Analysis Input

## Identity

- Project ID:
- Task Group:
- Task ID:
- Related Tasks:
- Issue / Ticket:
- Task Type: `change-impact-analysis`
- Requested Outcome:

## Proposed Change and User Intent

- Change being assessed (without prescribing an implementation):
- User intent and decision this analysis should support:
- Explicitly excluded changes or systems:

## Impact Scope

- Directly affected components, interfaces, or integrations:
- Potential dependency propagation:
- Expected test and operational impact:

## Preserved Behavior and Constraints

- Behavior, contracts, or outcomes that must be preserved:
- Compatibility, security, or operational constraints:
- Open decisions that a later planning phase must resolve:

## Questions for Analysers

1. Which behaviors must be preserved and which items are affected?
2. How could impacts propagate through dependencies, tests, and operations?
3. Which constraints and open decisions should be passed to implementation-planning without producing an execution plan?

## Input Limit

- Collect user intent, impact scope, and preserved behavior only.
- Do not add worker-produced result tables to this input.
- The final report `data.json` is the result source of truth.

## Conversion Note

- This input can be used as a starting draft before creating `okstra-task-brief.md`.