bucle-agentico

Name: bucle-agentico
Availability: InStock
Author: jocdlc

Map real system context before generating subtasks for multi-phase feature work.

4|Updated Apr 2, 2026

Search Tags:#automation #mcp #blueprint #phases #subtasks #context-mapping #todo-write

Ready to run

npx skills add https://github.com/JocDLC/saas-factory-v5 --skill bucle-agentico

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bucle-agentico
Source: https://github.com/JocDLC/saas-factory-v5/tree/main/.claude/skills/bucle-agentico
Command: npx skills add https://github.com/JocDLC/saas-factory-v5 --skill bucle-agentico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill automatiza el trabajo de características complejas por fases mapeando el contexto real justo antes de cada fase, evitando la generación de subtareas basadas en suposiciones y facilitando una implementación coordinada tras la aprobación de PRP.

Core Features & Use Cases

Mapeo de contexto just-in-time: captura el estado real del sistema antes de generar subtareas.
Fases primero, subtareas luego: estructura el trabajo en fases coordinadas y genera subtareas solo al entrar en una fase.
Actualización y seguimiento con TodoWrite: mantiene el progreso visible y seguro entre fases.
Uso de MCPs durante la ejecución: valida y aprende durante la ejecución sin depender de pasos fijos.

Quick Start

Inicia una tarea que requiera cambios en DB, código y UI; entra a la Fase 1, mapea el contexto actual y genera subtareas basadas en ese contexto.

Frequently Asked Questions about bucle-agentico

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

FAQPage Schema

How do I automate multi-phase feature work spanning database, code, and UI changes?▼

Generate subtasks just-in-time by mapping the actual system context immediately before entering each phase. This prevents assumption-based planning and ensures subtasks reflect the true current state of the codebase, database schema, and UI components before execution.

What is just-in-time context mapping for phased software development?▼

Just-in-time context mapping captures the actual system state immediately before generating subtasks for a specific phase. This approach prevents stale assumptions by ensuring dependency-driven planning and TodoWrite tracking reflect the true current conditions of the codebase, database, and UI.

How do I track progress across coordinated phases of a complex feature implementation?▼

Track progress across coordinated phases using TodoWrite to maintain visible, safe state transitions between tasks. This ensures dependency-driven planning remains synchronized throughout multi-phase feature work spanning database, code, and UI changes.

Does this phased feature automation work with MCP-guided checks during execution?▼

Yes, MCP-guided checks validate and learn dynamically during execution without relying on fixed steps. This integrates with phased context mapping and just-in-time subtask generation to ensure coordinated DB, code, and UI changes remain accurate throughout the workflow.

When should I use phased mapping instead of generating all subtasks upfront?▼

Use phased mapping when tasks span multiple files and require coordinated changes across DB, code, and UI. Generating subtasks only upon entering a phase, after mapping real context, avoids assumption-based planning that becomes stale when dependencies shift between earlier and later phases.