Guides the feature implementation cycle and routes requests through the six-stage contract. Use only for routing, unknown state, contract and gate questions. Do not conciliate, generate tasks, implement code or audit. Use operational skills for those actions.
Audits an implementation stage against closed acceptance criteria and the principal TAREAS.md using reproducible evidence. Use when implementation is said to be complete, the user asks to close a stage, or requests an audit. Do not implement repairs or…
Generates TAREAS.md (principal task list) after an implementation stage conciliation is cerrada, traced to CONCILIACION.md and the spec. Use when the user asks for the task file, listado principal, or says conciliation is done. Do not invent tasks outside…
Conciliates one implementation stage: updates CONCILIACION.md with in/out of scope, chat clarifications, and open questions. Use when the user is discussing a stage or clarifying product/feature decisions, or closing conciliation. Do not generate TAREAS.md,…
Splits a product specification into an implementation-stage folder tree with a README index and per-stage CONCILIACION.md drafts. Use when the user wants implementation stages or needs to divide an existing or new feature specification into stages. Do not…
Implements an approved implementation stage from its principal TAREAS.md or a TAREAS-delta-NN.md, verify the requested work, and leave evidence ready for a separate audit. Use when the user asks to implement or execute an approved stage or delta. Do not…