festina-plan

Generate an executable plan.xml from a scoped task's functional specification.

1|Updated Feb 26, 2026

Search Tags:#automation #spec #plan #project-management #task-planning #xml-plan

Ready to run

npx skills add https://github.com/mattfletcher94/festinalente --skill festina-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: festina-plan
Source: https://github.com/mattfletcher94/festinalente/tree/main/apps/festinalente/src/content/skills/festina-plan
Command: npx skills add https://github.com/mattfletcher94/festinalente --skill festina-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a plan document that converts scoped task specifications into a detailed, executable implementation plan, enabling deterministic progress.

Core Features & Use Cases

Generate a self-contained plan.xml from FRs, dependencies, and risks described in the spec.
Link plan to the original spec and task, including inventory, testing, edge-cases, and pitfalls for a complete implementation roadmap.
Provide guidance for developers with atomic tasks, verification steps, and clear done criteria to ensure traceability and repeatability.

Quick Start

Provide a scoped task ID to generate a complete XML plan from its specification and related task data.

Frequently Asked Questions about festina-plan

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

FAQPage Schema

How do I convert functional specifications into an executable implementation plan?▼

You can convert functional specifications into an executable implementation plan by automating the generation of a plan.xml file. This plan includes tasks, testing steps, edge-cases, and dependencies to guide deterministic development progress.

What is the best way to structure a project plan from functional requirements and constraints?▼

The best way to structure a project plan from functional requirements is to generate a self-contained XML document. This document links back to the original spec and provides an inventory, approach, and pitfalls for a complete implementation roadmap.

How do I generate a plan.xml from a scoped task specification?▼

To generate a plan.xml, provide a scoped task ID defined in your tasks directory. The system reads the functional requirements, affected files, and dependencies to produce a complete, executable XML plan.

Can I use automated task planning for development tasks with strict dependencies and edge-cases?▼

Yes, automated task planning handles strict dependencies and edge-cases by explicitly mapping them in the output. The generated plan.xml defines atomic tasks, verification steps, and clear done criteria to ensure traceability.

Does project-management automation work without defining affected files and constraints?▼

No, project-management automation requires a scoped task specification containing functional requirements, affected files, constraints, and dependencies. Without this input data, the plan.xml cannot accurately map the implementation roadmap.

What limitations should I expect when turning specs into actionable implementation plans?▼

A key limitation is that the process requires tasks to be pre-scoped in a specific directory format with functional requirements and constraints. It generates a plan.xml roadmap rather than executing the actual code implementation itself.