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

## Basic Identity

- Project ID:
- Task Group:
- Task ID:
- Related Tasks:
- Issue / Ticket:
  - If left empty, workers fall back to the `Task ID` (without a prefix, like `8852`). When a single run handles multiple tickets at once, separate them with commas (`TICKET-123, TICKET-456`). If neither can be identified, `unknown` is allowed.
- Requested Task Type:
- Requested Outcome:

## Current Context Summary

- What is the current state or request?
- What should happen instead?
- Why do you want cross verify now?
- Should this continue an existing task or start a new one?

## Current Evidence

- Main note or issue document:
- Existing analysis:
- Logs or raw samples:
- Related code paths:

## Constraints

- Known constraints:
- Known assumptions:
- Still uncertain:

- Adjacent areas deliberately excluded from this run:
- Items that look related but must be handled in a separate task:
- Reason for exclusion:

> Workers MUST NOT expand into items listed here.
> If left blank, any changes beyond the explicit requirements of the input will be treated as out of scope by default.
> Any exclusions that appear necessary will be recorded only as follow-up recommendations in the final report, and no further action will be taken.

## Config and Deployment References

- Related config files:
- Related deployment manifests:
- Expected values or invariants:
- What is still uncertain:

## Questions to Answer

1.
2.
3.

### Standing Scope-Discipline Questions (always answered)

- Which adjacent changes did you consider and **deliberately exclude** from this run? List each with a one-line reason.
- Did any part of your output go beyond what `Current Context Summary` and the `Out of Scope` block define? If yes, move it to follow-up recommendations and remove it from the main answer.

## Recommended Next Step

- Should this be converted into a full cross verify task brief?
- Is `requirements-discovery` the right first phase?
- If yes, what materials still need to be added?
- If this is a reopened task, should the same `Task Group` and `Task ID` be reused?