Projects and kanban board

Projects with stages and tasks on a six-column board, computed progress and reversible deletion.

  • Category: Projects and companies
  • Status: Available
  • Requirements: An ArduMaker account; To associate companies on creation: be an admin of those companies
  • MCP tools (Read only): listar_proyectos, ver_proyecto, buscar_en_proyecto, listar_proyectos_eliminados
  • MCP tools (Write or modify): crear_proyecto, crear_proyecto_con_etapas, editar_proyecto

Markdown

What can you do with it?

A project groups stages and tasks, with members, roles, attachments, calendar and linked resources. Stages and tasks are shown on a kanban-style board.

ColumnHow it is reached
backlogAutomatic with 0 progress
listoOnly by moving the card by hand
en_cursoAutomatic with progress between 1 and 99
en_revisionBy hand only
testingBy hand only
hechoAutomatic with 100 progress

When should you use it?

  • To organize the work for a client or product into stages and tasks.
  • To give an AI agent a place to read and update the state of the work.
  • To archive a finished project without deleting it.

How does it work in ArduMaker?

  1. On creation, ArduMaker seeds 14 roles with full permissions, adds the creator with the Manager role and creates "Etapa 1" with "Tarea 1" so it does not start empty.
  2. If companies are associated, you must be an admin of each one. By default the template marked as default by each company is applied.
  3. Progress rolls up from the bottom: a task's is manual or comes from its checklist; a stage's is the average of its tasks; the project's is the average of its stages.
  4. As long as nobody moves a card, its column is derived from progress. Moving it by hand pins it; setting it back to auto returns it to the computed value.

Project status is active or archived. Archiving hides it from the default list without deleting anything.

What actually changes?

  • Creating a project creates its roles, the creator's membership, one stage and one task.
  • Every deletion is logical: the project, a stage or a task goes to the trash for 30 days and can be fully restored.
  • Every creation, edit or deletion is recorded in the project history.

Diagram

  1. Checklist: done items / total
  2. Task: progress 0-100
  3. Stage: average of its tasks
  4. Project: average of its stages
How progress rolls up — The board column is derived from that progress unless someone moves the card.

Expected result

The project becomes visible to its members and to the members and admins of the associated companies, each with what their role allows.

Errors and troubleshooting

MessageCause
nombre is requiredThe name was empty.
Template not foundThe requested template does not exist or is deactivated.
That template belongs to a company that is not part of this projectA template from a non-associated company was chosen.

If the template fails, the project has already been created: the template is applied afterwards, outside the creation.

MCP access

An MCP agent lists, creates and edits projects within the scope its owner granted. It can never delete an entire project.

  • Read: listar_proyectos, ver_proyecto, buscar_en_proyecto, listar_proyectos_eliminados.
  • Write: crear_proyecto (accepts plantilla_id), crear_proyecto_con_etapas and editar_proyecto (includes archiving).
  • crear_proyecto_con_etapas creates the project and its stages in one call; if the stages fail, the project stays created and the response reports it in residuo.

More at /mcp/proyectos and /mcp/docs.

Related features