feat(agent-dev): on Trinity the project skills use the platform — project-init 1.4 + the task skills (ent#588, ent#673) — agent-dev 1.21.0

[dolho]

Summary

Both re-scopes from 2026-09-29 (ent#661: projects on Trinity are platform-owned). The project skills stay the process: on Trinity they call the platform, and without Trinity the folder, canon and GitHub modes from #21–#23 are the offline mode, unchanged.

PROJECT_STANDARD §17, "Platform projects": the one rule every project skill uses.

• On Trinity or not: list_projects answers → platform. An OSS or unlicensed build → offline, said once. --offline → offline, on purpose.
• Where each concept lives on the platform: a mapping table in the same shape as §16's.
• Never: people, visibility, or a project the agent isn't active on.

ent#588: project-init 1.4 (commit d692624)

• New project:
  • creates it with create_project, so the agent's owner is creator and first member, the agent is steward, and it's members-only;
  • records the success criteria, owners and cadence as the first log entry;
  • checks for name collisions with list_projects.
• adopt <folder>: import_project, once. After that the platform is the project's home, and nothing syncs back.
• Without the Start projects permission: says so and names the two ways forward (an admin grants it in the agent's Settings, or the person creates the project in the Workspace). It never falls back to a folder or an epic to get around the refusal.

ent#673: the task skills on the platform task list (commit 19a8632). On Trinity, tasks live in the platform's task list, with the same fields as the offline task file.

• project-task 1.6: create_project_task, with the same anatomy. The Validation rows go at the end of Context. The reference is <project id>/T-NNN.
• project-intake 1.5:
  • dedupes on list_project_tasks;
  • creates tasks through project-task's Platform path;
  • writes state news with add_project_log_entry.
• project-steward 1.6:
  • takes its project list from get_steward_digest;
  • has a translation table from each GitHub step to the MCP call;
  • updates health with set_project_health at least every two weeks;
  • skips the quarantine pass and the publish step for platform projects.
• project-reconcile 1.3: platform tasks join the registry map, and gestures apply through update_project_task / add_project_task_note.

agent-dev 1.21.0. Every edited SKILL.md frontmatter parses, with its version bumped and a changelog entry on top.

Platform half

• feat(projects): an agent can start a project for its owner — projects.manage + create_project / import_project (abilityai/trinity-enterprise#588) trinity#3339: the projects.manage capability, the create_project / import_project MCP tools, and the Settings toggle.
• Abilityai/trinity-enterprise#835: the agent create/import routes, which check projects.manage first.

The task, log, health and digest tools that the ent#673 half uses are already on dev (ent#661 v2/v3). So that half works on any Trinity running projects today, while create_project / import_project need #3339 and #835.

Not done here

• ent#673's proof run (one real project through a full steward cycle) is still on trinity-pm's list, as agreed on the issue.
• After merge, trinity-pm reinstalls the project skills, and the trinity-skills mirrors refresh through /sync-skill-library.

Refs abilityai/trinity-enterprise#588, abilityai/trinity-enterprise#673

🤖 Generated with Claude Code

[vybe]

Closing as superseded, on Eugene's call (2026-10-10). The same work — platform mode for the project skills on Trinity Projects — shipped on main as d826887 (agent-dev 1.22.0, abilityai/trinity-enterprise#788) and is mirrored into trinity-skills@43d04e8. The branch is left in place in case anything here is worth porting (the --offline flag, success criteria as the first log entry).

— trinity-pm