festina-map-engineering

Map codebase subsystems, data flows, and dependencies into engineering docs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill addresses the challenge of documenting codebase architecture, systems, and patterns by coordinating parallel exploration and Socratic QA to preserve decisions and prevent context rot.

Core Features & Use Cases

  • Parallel agent-driven discovery to map subsystems, data flows, and dependencies.
  • Generation of system docs, patterns, conventions, and risks with diagrams and cross-references.
  • Automated validation, glossary updates, and integration-ready engineering overview.

Quick Start

Launch festina-map-engineering to generate and validate engineering documentation for a codebase.

Frequently Asked Questions about festina-map-engineering

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

FAQPage Schema
How do I automatically generate architecture documentation from a codebase?

You can automatically generate architecture documentation by running the festina-map-engineering skill, which uses parallel agent-driven discovery to identify major subsystems, data flows, and dependencies in the codebase and produce validated engineering system docs.

What is the best way to map codebase dependencies and data flows for engineering docs?

Mapping codebase dependencies and data flows is best handled through parallel exploration by specialized agents that identify system patterns and risks, feeding findings into a cohesive overview with diagrams and cross-references.

How does parallel agent discovery work for codebase architecture mapping?

Parallel agent discovery works by coordinating specialized agents that simultaneously explore the codebase to identify conventions, patterns, and risks, validating findings and persisting them to a dedicated engineering directory with glossary updates.

Can I generate engineering diagrams and risk analyses automatically for my software systems?

Yes, you can generate engineering diagrams and risk analyses automatically by launching the skill, which produces cross-referenced system docs and prepares a validated overview with automated glossary updates.

Does this approach require any specific dependencies or external tools to document software patterns?

No external dependencies or tools are required to document software patterns, as the skill operates independently to identify conventions and generate integration-ready engineering overviews directly from the codebase.

When should I use automated codebase discovery to prevent documentation context rot?

You should use automated codebase discovery to prevent context rot when you need to preserve architectural decisions and system patterns through Socratic QA and persistent, validated engineering documentation.