aim-coordinator-guide

Formulate an approvable atomic POST /tasks/batch plan with create and delete operations.

4|1|Updated Apr 18, 2026

Search Tags:#coordinator #batch-operations #task-pool #manager-output #baseline-facts #rejected-feedback

Ready to run

npx skills add https://github.com/zccz14/AIM --skill aim-coordinator-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aim-coordinator-guide
Source: https://github.com/zccz14/AIM/tree/main/.agents/skills/aim-coordinator-guide
Command: npx skills add https://github.com/zccz14/AIM --skill aim-coordinator-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a decision entry for AIM Task Pool maintenance by forming an approvable POST /tasks/batch operations plan from Manager output, latest baseline facts, current Tasks, and rejected Task feedback before applying atomic Task Pool writes.

Core Features & Use Cases

Coordinates Manager signals, baseline facts, active Task Pool, and rejected feedback to produce a batch of create/delete operations.
Ensures batch writes are atomic and require explicit user approval; prevents partial updates and maintains task integrity.
Use Case: When Manager reveals gaps between README targets and baseline, this skill drafts a batch plan to add missing tasks or retire obsolete ones for a given project.

Quick Start

Review Manager outputs and baseline facts, then approve the proposed POST /tasks/batch plan to update the Task Pool.

Frequently Asked Questions about aim-coordinator-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an atomic batch operations plan for a task pool?▼

To generate an atomic batch operations plan for a task pool, you formulate a POST /tasks/batch plan from Manager outputs, baseline facts, and rejected feedback. The plan includes only create and delete operations and requires explicit approval before execution.

What is a batch-atomic task pool update?▼

A batch-atomic task pool update is a write operation that applies create and delete actions together as a single unit. This prevents partial updates and maintains task integrity by requiring explicit user approval before execution.

How do I coordinate manager output and baseline facts to update tasks?▼

To coordinate manager output and baseline facts to update tasks, you cross-reference README targets against the current Task Pool. This process drafts a batch plan to add missing tasks or retire obsolete ones based on rejected feedback.

Does the batch plan include task dependencies and planning metadata?▼

Yes, the batch plan includes per-entry details with task_id, title, spec, dependencies, and planning metadata. This ensures every create or delete operation in the atomic batch is fully specified before approval.

Why does my task pool update require explicit approval before execution?▼

Your task pool update requires explicit approval before execution to prevent partial updates and maintain task integrity. The batch-atomic design ensures that formulated create and delete operations are validated against baseline facts prior to applying writes.