festina-scope

Identify architectural decisions and patterns to produce a scoped functional specification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps researchers scope Festina Lente's codebase and generate a functional specification through iterative conversational Q&A, focusing on engineering decisions, patterns, and risk awareness.

Core Features & Use Cases

  • Guided, multi-agent reconnaissance to gather product context, engineering patterns, and codebase references.
  • Structured synthesis to present a cohesive spec and scope for implementation.
  • Pitfall detection and decision logging to manage trade-offs and ensure traceability.

Quick Start

Describe your task and run the scope workflow to generate a scoped functional specification.

Frequently Asked Questions about festina-scope

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

FAQPage Schema
How do I research a codebase to write a technical specification?

Generate a functional specification from an existing codebase through iterative conversational Q&A, which gathers product context, detects engineering pitfalls, and logs decisions to manage trade-offs and ensure traceability.

How do I identify architectural risks and scope before starting implementation?

Identify architectural risks and scope by conducting guided reconnaissance on product documentation and codebase references, synthesizing the findings into a structured specification with actionable tasks and decision logs.

Can I use conversational Q&A to scope engineering tasks for a complex codebase?

You can use conversational Q&A to scope engineering tasks by iteratively querying the codebase and documentation to inform a precise specification, capturing architectural decisions and potential pitfalls along the way.

What's the best way to translate codebase patterns into actionable development tasks?

Translate codebase patterns into actionable development tasks by applying discovered architectural decisions to determine required files and implementation steps, delivering a structured synthesis for a formal spec.

Does this approach require existing product documentation to generate a spec?

Generating a spec benefits from existing product documentation to inform the scope, but the workflow also directly researches the codebase to identify patterns and determine required files for a robust specification.