PRD a RFCs

Descripción

Este prompt divide el proyecto en documentos RFC (Request for Comments) lógicos y manejables para implementación, organizados en un orden claro que tiene en cuenta dependencias y secuencia lógica de construcción.

Proceso

  • Análisis de orden de implementación: Determina la secuencia óptima de implementación
  • Agrupación de características: Agrupa características relacionadas que deben implementarse juntas
  • Estructura de RFC: Proporciona identificador único, título, resumen, enfoque técnico, etc.
  • Consideraciones de implementación: Destaca desafíos técnicos, casos límite, enfoques de prueba, etc.
  • Creación de prompts de implementación: Crea prompts de implementación en secuencia numérica estricta

Ejemplo de Estructura de RFC


# RFC-001: Configuración Inicial del Proyecto

## Resumen
Este RFC establece la estructura base del proyecto, dependencias clave y configuración inicial.

## Características Incluidas
- F12: Configuración del entorno de desarrollo
- F13: Sistema de Construcción
- F14: Estructura de carpetas

## Enfoque Técnico
El proyecto utilizará una estructura modular basada en características con:
1. Configuración de TypeScript para tipado estricto
2. Configuración de linting y formateo con ESLint y Prettier
3. Configuración inicial de Vite para desarrollo y construcción
4. Estructura de carpetas que sigue el patrón de arquitectura limpia

## Consideraciones de Implementación
- Asegurar que la estructura permita pruebas eficientes
- Configurar alias de importación para mejorar la legibilidad del código
- Establecer scripts de NPM consistentes para tareas comunes

Prompt Completo

You are an expert software architect and project manager tasked with breaking down the attached Product Requirements Document (PRD), features list, and project rules into manageable Request for Comments (RFC) documents for implementation.

Create a set of well-structured RFC documents that divide the project into logical, implementable units of work. Each RFC should represent a cohesive, reasonably-sized portion of the application that can be implemented as a unit. The RFCs MUST be organized in a clear implementation order that accounts for dependencies and logical build sequence. IMPORTANT: RFCs will be implemented strictly one by one in sequential order, so the ordering is critical.

If any critical information is missing or unclear in the provided documents that prevents thorough RFC creation, ask specific questions to gather the necessary details before proceeding.

Generate the RFCs files under RFCs folder including PROMPT CREATION md files by:

1. IMPLEMENTATION ORDER ANALYSIS:

  • Analyze the entire project to determine the optimal implementation sequence
  • Identify foundation components that must be built first
  • Create a directed graph of feature dependencies (described textually)
  • Determine critical path items that block other development
  • Group features into implementation phases based on dependencies
  • Assign sequential numbers to RFCs that reflect their strict implementation order (001, 002, 003, etc.)
  • CRITICAL: Each RFC will be implemented one at a time in numerical order, so the sequence must be logical and buildable
  • Each RFC must be fully implementable after all previous RFCs in the sequence have been completed
  • No parallel implementation will occur - RFC-002 will only begin after RFC-001 is complete
  • Map all dependencies between features to ensure the sequential order is feasible

2. FEATURE GROUPING:

  • Group related features that should be implemented together in a single RFC
  • Ensure each RFC represents a logical, cohesive unit of functionality
  • Balance RFC size - not too small (trivial) or too large (unmanageable)
  • Consider dependencies between features when grouping
  • Identify shared components or services that multiple features might depend on
  • Organize groups to align with the strict sequential implementation order
  • Ensure features that build upon each other are grouped in the correct sequence

3. RFC STRUCTURE:

  • Assign a unique identifier to each RFC that reflects implementation order
  • Provide a clear title that describes the functionality
  • Include a summary of what the RFC covers
  • List all features/requirements addressed in the RFC
  • Detail technical approach and architecture considerations
  • Explicitly identify which previous RFCs this RFC builds upon
  • Specify which future RFCs will build upon this RFC
  • Estimate relative complexity (Low, Medium, High)
  • Include detailed acceptance criteria for each feature
  • Specify any API contracts or interfaces that will be exposed

4. IMPLEMENTATION CONSIDERATIONS:

  • Highlight any technical challenges or considerations
  • Note any specific rules from RULES.md that particularmente apply to this RFC
  • Identify potential edge cases or special handling requirements
  • Suggest testing approaches for the functionality
  • Specify performance expectations and optimization considerations

First, provide a brief overview of how you've approached breaking down the project, with special emphasis on the sequential implementation order you've determined. Then create the comprehensive set of RFC documents and implementation prompts following the structure above, organizing them in strict numerical implementation order.

Ensure each RFC is specific enough to guide implementation but flexible enough to allow for engineering decisions during development. Focus on creating RFCs that represent logical, cohesive units of functionality that can be reasonably implemented one after another.

The goal is to provide AI implementers with complete, unambiguous specifications that enable them to produce high-quality code without requiring additional clarification, while following a strict sequential implementation order. Each RFC must be fully implementable after all previous RFCs have been completed, with no parallel implementation.