---
title: OKSTRA Feature 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 Feature Analysis Input

## Identity

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

## User Intent and Confirmed Target

- Confirmed feature, journey, or capability to analyse:
- User intent and expected value:
- Explicitly excluded feature areas:

## Behavior Scope

- Normal flow to preserve or understand:
- Alternate flows:
- Failure flows:
- Rules, state changes, or external calls that need attention:

## Preserved Behavior

- Contracts or outcomes that must remain unchanged:
- Compatibility, security, or operational constraints:
- Unknown behavior that requires clarification:

## Questions for Analysers

1. What normal, alternate, and failure flows define the confirmed target?
2. Which rules, state transitions, and external calls are in scope?
3. What test coverage scope should a later task consider without proposing implementation changes?

## Input Limit

- Collect user intent, behavior 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`.