kata-pov-scope-define

Name: kata-pov-scope-define
Availability: InStock
Author: Guardia

Generate pov.md and scope.md contract files for pre-operational agent planning.

Updated Sep 3, 2025

Search Tags:#documentation #scope definition #value metrics #agent planning #scope validation #pov #stabilization contract

Ready to run

npx skills add https://github.com/guardiatechnology/design-system --skill kata-pov-scope-define

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kata-pov-scope-define
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-pov-scope-define
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-pov-scope-define

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents agents from starting implementation without a precise, testable scope—avoiding scope creep and “zombie” PoVs that never prove value.

Core Features & Use Cases

PoV scope scaffolding: Generates a complementary pov.md + scope.md pair under docs/{context}/agents-pov/{agent}/.
Validation & safety rails: Enforces required inputs, warns on existing pov.md/scope.md, and requires --force to overwrite.
Operational exit criterion: Writes a discontinuation criterion based on a time window plus a metric threshold to ensure learning is archived if value is not reached.
Stage-gated persona definition: Requires the persona block to include stage: pre-operational to satisfy downstream directive checks.

Quick Start

Run kata-pov-scope-define with your context, agent name, literal customer problem, value metric, and kind so it creates the pov.md and scope.md contract files for that agent.

Frequently Asked Questions about kata-pov-scope-define

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define agent scope and prevent scope creep during pre-operational planning?▼

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.

What is an operational exit criterion for an agent proof of value?▼

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.

How do I scaffold pov.md and scope.md contract files for agent planning?▼

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.

Can I overwrite existing pov.md and scope.md documentation during scope validation?▼

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.

Do I need a pre-operational persona stage to generate agent PoV documentation?▼

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.

Why does agent PoV scope definition require strict input validation?▼

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.