festina-directive

Translate conversational inputs into structured XML directives for Festina Lente workflows.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattfletcher94/festinalente --skill festina-directive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: festina-directive
Source: https://github.com/mattfletcher94/festinalente/tree/main/apps/festinalente/src/content/skills/festina-directive
Command: npx skills add https://github.com/mattfletcher94/festinalente --skill festina-directive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to capture directive context, purpose, rules, validations, and examples through a guided conversational flow, producing a structured XML directive stored at .festinalente/directives/{name}.xml and linked to skills via .festinalente/config.yaml.

Core Features & Use Cases

  • Conversational capture: Guides users to articulate principles, process rules, validations, and examples, then translates them into a machine-readable directive.
  • XML artifact generation: Automatically generates and stores the directive as .festinalente/directives/{name}.xml.
  • Skill linkage: Associates directives with existing skills via .festinalente/config.yaml to enable loading by the relevant workflow phases.

Quick Start

Run /festina-directive with a name and answer the guided prompts to generate a new directive.

Frequently Asked Questions about festina-directive

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

FAQPage Schema
How do I create structured XML directives for workflow automation through a guided process?

You can create structured XML directives by running a guided conversational Q&A flow that translates your inputs into machine-readable artifacts. This captures principles, rules, validations, and examples, then stores the output at .festinalente/directives/{name}.xml.

How do I link generated XML directives to specific workflow phases like scope and implement?

You link generated directives by updating the project's .festinalente/config.yaml file. This associates the XML artifacts with existing skills, enabling the relevant workflow phases such as scope, plan, implement, and check to load them.

Can I use conversational inputs to define validation rules and principles for my automation config?

Yes, conversational capture guides you to articulate process rules, validations, and examples, which are then translated into a structured XML directive. This ensures your automation config accurately reflects your team's principles.

What is the best way to capture and store project directives as machine-readable XML artifacts?

The best way to capture project directives is through a conversational flow that translates your team's context and purpose into structured XML. The generated artifact is automatically stored at .festinalente/directives/{name}.xml and validated by the project's tooling.

Do I need an existing .festinalente directory structure before generating directives?

Yes, the directive generation process requires the project's tooling and config structure to be present. The resulting XML is stored at .festinalente/directives/{name}.xml and linked via .festinalente/config.yaml, meaning these paths must exist or be created.