Menú
Parses workflow blueprints from .carryctx/workflows/ and automatically generates structured task steps. Helps agents translate high-level tasks into detailed standard operating procedures (SOPs).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Core CarryCtx capability. Persistent project context and continuity manager for coding agents. Helps agents manage structured tasks, track progress, save checkpoints, maintain context across sessions and Git worktrees. Use when starting work, tracking task progress, creating checkpoints, switching worktrees, scanning code dependency graphs, running MCP stdio servers, applying presets, or restoring project state.
Allows the agent to adopt specific personas and roles (e.g., Code Reviewer, Architect) defined in .carryctx/personas/. Modifies agent behavior, strictness, and code style output based on the active role.
Dynamic context-aware rule loader for CarryCtx. Teaches the agent to automatically load and apply domain-specific rules and guidelines from the project's .carryctx/rules/ directory depending on the task at hand. Use to enforce project guidelines and improve accuracy.
Basado en la clasificación ocupacional SOC
| name | carryctx-workflows |
| description | Parses workflow blueprints from .carryctx/workflows/ and automatically generates structured task steps. Helps agents translate high-level tasks into detailed standard operating procedures (SOPs). |
You are equipped with the ability to execute Standard Operating Procedures (SOPs) defined by the project.
Blueprint Discovery: When assigned a high-level task (e.g., "Add a new API route", "Create a new database migration"), check if the .carryctx/workflows/ directory exists in the project.
Parsing Blueprints: If a blueprint file matches the intent of the task (e.g., api-route.md, new-component.md), read it to understand the required sequence of steps.
Task Breakdown: Do not try to hold the entire workflow in your memory. To ensure absolute traceability, do not skip steps. Break down the workflow into Todo items in your current task:
todo_json="$(carryctx progress todo "Run unit tests" --json)"
progress_id="$(printf '%s' "$todo_json" | jq -r '.id')"
Sequential Execution:
carryctx progress complete "$progress_id"