aops-cli-projectman

Manages server-canonical boards, sprints, issues, and review requests through the aops CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eeemzs/aops --skill aops-cli-projectman-eeemzs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aops-cli-projectman
Source: https://github.com/eeemzs/aops/tree/main/assets/skills/aops-cli-projectman
Command: npx skills add https://github.com/eeemzs/aops --skill aops-cli-projectman-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents working across sessions lose track of execution state: which tasks are doing or done, what sprint plans exist, and whether reviews were actually approved. This Skill gives agents a canonical, server-hosted project management workflow so status, issues, and review records stay truthful and consistent. ## Core Features & Use Cases - Board and Sprint Management: Create kanban tasks, bounded sprints with phases and microtasks, and track completion with evidence notes and status audits. - Issues, Feedback, and Reviews: Record defects and observations, create canonical review requests with append-only results, and open child re-review records instead of overwriting outcomes. - Cross-Session Handoff: Write and resume Projectman-bound handoffs so a new agent session can pick up exactly where the last one stopped. - Use Case: An agent starts a multi-step feature, creates a sprint with a NE/NICIN/DONE-WHEN goal, updates microtasks as evidence lands, requests a review, logs findings as issues, and hands off remaining work to the next session. ## Quick Start Ask your agent to use the aops-cli-projectman skill to run a bounded resume for your project slug and list the current doing sprints and open issues.

Frequently Asked Questions about aops-cli-projectman

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

FAQPage Schema
How do I create a sprint with the aops CLI?▼

Create a kanban task first, then run aops pm sprint create with the project slug, task id, a semantic name, and a goal containing NE, NICIN, and DONE-WHEN fields. Add the plan with sprint update-plan using a phases JSON file, always with --apply after previewing.

How do I track code review requests in aops Projectman?▼

Use aops pm review-request create with the task, sprint, target reviewer, and review scope. Results are append-only entries added via review-request result; for a changes-requested outcome, create linked issues and open a child re-review request rather than overwriting the original.

Why did all my microtasks change status at once?▼

The pm sprint set-status command is bulk by design and rewrites every nested microtask. To update a single item with evidence, use pm utask update with the sprint id, microtask id, status, and notes instead.

Can I edit the local .aops-cache projectman files directly?▼

No. The .aops-cache/projectman directory is a read-only derived cache. All writes must go through the hosted gateway via the aops pm commands; if the mirror disagrees with hosted state, the hosted server record wins.

What should I do when multiple projects are linked in aops?▼

Run aops project links list to inspect links, then always pass --project-slug explicitly for any material write. If you wrote to the wrong project, stop, re-inspect the links, and rerun the command with the correct slug.