kata-pov-system-prompt

Generate a pre-operational agent PoV system prompt from pov.md into system-prompt.md.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-pov-system-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-pov-system-prompt
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-pov-system-prompt
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-pov-system-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably produce a minimum viable system prompt for an agent’s Persona of Vision (PoV) during the pre-operational stage, ensuring the prompt follows the required structure and includes the literal stage declaration needed for downstream validation.

Core Features & Use Cases

  • Pre-operational PoV prompt authoring: Creates the required four blocks (Identity, Capabilities, Restrictions, Style) with an explicit stage: pre-operational line.
  • Scope-constrained capability writing: Ensures capabilities remain minimal (max 3) and aligned to the primary use case extracted from pov.md.
  • Safety and consistency validation: Runs a minimal adversarial validation step in minimum-viable mode before persisting system-prompt.md for the agent.

Quick Start

Ask the AI to run the kata workflow to read docs/{context}/agents-pov/{agent}/pov.md and generate docs/{context}/agents-pov/{agent}/system-prompt.md with the required four blocks and stage: pre-operational declared literally.

Frequently Asked Questions about kata-pov-system-prompt

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

FAQPage Schema
How do I generate a pre-operational system prompt for an agent persona?

To generate a pre-operational system prompt, the workflow reads your agent's pov.md file and outputs a system-prompt.md containing Identity, Capabilities, Restrictions, and Style blocks with an explicit stage declaration.

What is a pre-operational PoV system prompt and when do I need it?

A pre-operational PoV system prompt is a structured prompt defining an agent's persona scope before deployment. You need it when translating persona vision, value metrics, and out-of-scope restrictions into a constrained prompt for agent construction.

How do I structure system prompt capabilities and restrictions during agent construction?

Structure system prompt capabilities and restrictions by defining a maximum of three scope-constrained capabilities aligned to your primary use case, followed by explicit out-of-scope restrictions to ensure safety and consistency.

Does the system prompt generation workflow include prompt injection validation?

Yes, system prompt generation includes prompt injection validation by invoking an adversarial validation step in minimum-viable mode before persisting the final system-prompt.md file.

Can I use placeholders in my agent system prompt file?

No, you cannot use placeholders in your agent system prompt file. The generation workflow ensures all placeholders are removed and the literal stage: pre-operational text is included before the prompt is persisted.

What are the limitations of minimum viable system prompts for agents?

Limitations of minimum viable system prompts include strict capability limits of three functions, mandatory pre-operational stage declarations, and required adversarial validation before persistence to ensure safe agent behavior.