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

## Identity

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

## User Intent

- What decision or understanding should this project map support?
- Who will use the analysis and for what next action?

## Scan Scope

- Repositories and directories to inspect:
- Entry points or components to prioritise:
- External systems or integrations to include:
- Explicitly excluded repositories, directories, or systems:

## Preserved Boundaries

- Behavior or contracts that must be treated as unchanged:
- Ownership, security, compatibility, or operational boundaries:
- Unknown boundaries that require clarification:

## Questions for Analysers

1. Which components, dependency directions, entry points, repositories, and external integrations are in scope?
2. What shallow feature index best helps a later task navigate this area?
3. Which scan boundaries prevent the analysis from becoming a detailed feature or implementation plan?

## Input Limit

- Collect user intent, scan scope, and preserved boundaries 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`.