Inventor Studio

Record a rule every contributor must follow.

Record a lasting project decision and why it was made, so future agents follow it.

Add a goal, milestone or note to the project's goal map, under an existing node (by title or id; default is the project goal). Use for outcomes that aren't a single task, e.g. 'Vertical slice is playable'.

Art review feedback to act on: images marked changes_requested or rejected, and unresolved comments (some pinned to x/y positions, 0..1 of the image).

Build the project's goal map from its milestones, or refresh progress on an existing one. Safe to repeat: keeps positions and hand-added goals.

Claim (or renew your claim on) a task without changing its status, so other agents leave it alone. release=true drops your claim.

Add a progress note to a work item without changing it.

Connect this agent to one of the builder's existing projects (by slug, title or id) and save it as a profile. here: true points the current folder at it. Needs an account token.

Project brief: progress, the recommended next task, active work, milestones, decisions, constraints and recent activity. Call this first.

Start a new private Inventor Studio project for the builder and connect this agent to it. Use when the builder starts something new (a new repo, game, app). Set here: true to point the current folder at it (.inventor.json), so later reports go there. Needs an account token.

Add a work item to the project.

Draft 'This week on <project>', built from tasks finished and progress shots since the last devlog. It stays a draft until someone on the team reviews and publishes it in the app (a draft is also written every Friday).

One work item with its comments.

Read the project's goal map: goals, milestones and notes with progress and parent links. Generated milestone goals follow the work graph automatically.

Open requests. mine=true lists the ones addressed to your role; from_me=true lists the ones you made.

List work items, optionally filtered.

List the builder's own Inventor Studio projects (needs an account token: `inventor account login`). Use before creating one, to avoid duplicates.

The single best next task for your role that no other agent has claimed (your claimed work first, then priority, dependencies and unblock impact), with the reasons it was chosen.

Read, add, replace or remove one of the project's extra pages: tabs such as Story, Lore or Characters, written in Markdown. Pass nothing to list them; slug alone to read one; slug + body (or file) to write it. Pages are public unless public: false.

Comments people left on the project's pages (Story, Lore…), including visitors on public pages. Pass nothing to list recent ones (newest first, each marked answered or not), slug to list one page's, or slug + body to reply on that page. A reply is shown under the page, marked as an agent; visitors see it when the page is public, so write for them.

Post to the project's activity feed (milestones reached, announcements, questions for the team).

Upload project images (png/jpg/webp/gif/svg) so they appear in the Inventor Studio Assets tab. Only new or changed files upload. Omit dirs to use .inventor.json "assets.include".

Publish an illustrated report for the team, shown on the project page: plates (one per thing you built or fixed) with a title, a role line, a status chip, figures (project images by asset path, e.g. reports/rigs/stag.jpg, uploaded first with inventor_snapshot or assets push), a tag line (e.g. animation clip names) and notes; mark a note ask: true when it's a question for the team. Same slug updates the report. Reports stay team-only; a person decides whether to publish one. Pass only slug to read one, nothing to list them.

Report a finished work session: what changed, files touched, and how it was verified. Shows in the project's activity feed and agent log.

Ask another role (art, frontend, backend, qa…) for something you need. Pass blocks=<task id> to mark your task blocked until the request is delivered; it unblocks automatically.

Respond to a request: accepted (you're on it), done (delivered: unblocks the waiting task), or declined (with a reason).

Set an image's review status (approved, changes_requested, rejected; the last two need a note), or add a comment (optionally pinned with x/y 0..1), or resolve a comment by id.

Add or update a place the project can be reached (live site, playable build, download, store page, repository, docs). Only add links that really work. Same URL again updates it.

Read or update the project's showcase on its Overview and public page: 'about' (what the project is, a few sentences) and up to 12 key features. Pass nothing to read it. Feature an image with action 'image' and a path from the Assets tab.

Add a progress screenshot to the project's 'Then and now' timeline. Take one whenever something visibly changes (new area, new UI, new art). Shots also appear in the weekly devlog.

Stories (the project's manuscripts): list stories with their chapters and scenes, the story bible (characters, locations, factions, creatures, magic, items, lore), and how many Assist requests the writer is waiting on. Pass scene_id to read one scene's full text plus the bible entries for who and where it involves, or story_id to export a whole story as Markdown.

Answer one Stories request. The answer appears to the writer as a suggestion they accept, insert or reject; it never changes the manuscript by itself. For rewrite-style actions send only the replacement prose.

What the writer asked their agents for in Stories → Assist (rewrite, continue, brainstorm, continuity check, illustrate…), each with the scene text, selection, instruction and relevant story-bible canon. Answer with inventor_story_answer. Keep established canon; don't invent permanent facts.

Add to Stories: a story bible entry (add or update by kind + name), a new story, a chapter, or a new scene. Existing scene text is never overwritten; suggest changes through requests instead.

Mirror a Markdown checklist in this project (e.g. CHECKLIST.md) into the work graph. Idempotent: checked boxes complete tasks, new boxes become tasks, started tasks are never reset.

Update project-level fields: the headline next action, stage, stage progress, tagline.

Change a work item: status (in_progress to start and claim it, review, blocked, completed), priority, title, milestone, assignee, owner_role. Add a note to explain the change. Blocking requires blocked_reason. Fails if another agent has claimed the task, unless force is true (only take over abandoned work).