kata-pov-scope-define

Agent scope definition prevents scope creep by generating complementary pov.md and scope.md documentation that specifies a single primary use case, explicit out-of-scope items, and a pre-operational persona for downstream design contracts.

An operational exit criterion is a discontinuation rule based on a time window plus a metric threshold, ensuring learning is archived if the agent does not reach its value metric within the specified timeframe.

Scaffolding pov.md and scope.md requires providing your context, agent name, literal customer problem, value metric, and kind to generate the contract files under docs/{context}/agents-pov/{agent}/ with stabilization notes.

Overwriting existing pov.md or scope.md documentation requires a --force flag, as the scope validation process enforces safety rails that warn against existing files to prevent accidental data loss.

A pre-operational persona stage is required for agent PoV documentation, as the persona block must include stage: pre-operational to satisfy downstream directive checks and establish the stabilization contract.

Strict input validation is required because agent PoV scope definition enforces mandatory inputs like context, agent name, customer problem, and value metric to ensure consistent persistence and prevent incomplete scope contracts.