bucle-agentico

Coordinate phased feature implementation with context mapping and TodoWrite workflows.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/arroyo2009jose-max/civradar-autoridades --skill bucle-agentico-arroyo2009jose-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bucle-agentico
Source: https://github.com/arroyo2009jose-max/civradar-autoridades/tree/main/.claude/skills/bucle-agentico
Command: npx skills add https://github.com/arroyo2009jose-max/civradar-autoridades --skill bucle-agentico-arroyo2009jose-max

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates end-to-end feature delivery by mapping real context before each phase, enabling safe progression when tasks touch multiple files and require coordinated DB, code, and UI changes.

Core Features & Use Cases

  • Phased planning and execution for complex features.
  • Real-context mapping to inform subtasks and dependencies across phases.
  • MCP-guided execution with guarded transitions and audit trails.

Quick Start

Map the real context before starting each phase and generate subtasks accordingly.

Frequently Asked Questions about bucle-agentico

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

FAQPage Schema
How do I coordinate phased feature implementation across multiple files requiring DB, code, and UI changes?

Phased feature implementation maps real context before each phase to coordinate DB, code, and UI changes. It generates subtasks based on dependencies, enabling safe progression across multiple files.

What is context mapping in phased software development workflows?

Context mapping in phased development analyzes real project state before each phase to inform subtask generation and dependency tracking. This ensures coordinated changes across DB, code, and UI layers.

How do I implement an approved PRP with guarded transitions and an auditable workflow?

An approved PRP is implemented using an auditable TodoWrite-driven workflow with guarded transitions. Selective MCP usage guides execution while phase delineation ensures structured progression.

Does MCP-guided execution support selective tool usage during phased development?

MCP-guided execution supports selective tool usage during phased development by applying guarded transitions between phases. This creates an auditable workflow that tracks progress through TodoWrite integration.

When should I use a phased development workflow for software engineering tasks?

Phased development workflows apply to tasks touching multiple files requiring coordinated DB, code, and UI changes, or after a PRP is approved. Complex features benefit from real-context mapping before each phase.

What's the best way to plan subtasks and dependencies for complex multi-file features?

Planning subtasks and dependencies for complex features requires mapping real context before each phase. This approach informs coordinated DB, code, and UI changes through MCP-guided execution with audit trails.