aops-cli-mission

Guides agents through aops-cli mission commands for policy, resume, and start integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working with the aops CLI need clear rules for managing hosted Agentspace missions—creating them, seeding policy, resuming sessions, and keeping ownership boundaries straight between Mission, Projectman, and Memory. ## Core Features & Use Cases - Mission Command Map: Provides exact commands for mission create, list, get, update, resume, and the start --resume bridge with JSON output flags. - Policy Seeding: Explains how to pass the policyJson emitted by aops-cli start into mission create and update calls using the working-discipline convention. - Ownership Boundaries: Defines which system owns execution truth (Projectman), durable context (Memory), and decision truth (Discuss), with explicit anti-patterns to avoid. - Use Case: An agent resuming a long-running project runs aops-cli mission resume with a mission id to get a compact, token-efficient pack of active plan refs, review refs, and session guidance before continuing work. ## Quick Start Ask the agent to create an aops mission with an objective and the policy JSON from aops-cli start, then resume it later with aops-cli mission resume.

Frequently Asked Questions about aops-cli-mission

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

FAQPage Schema
How do I create an aops mission with a policy?▼

Run aops-cli mission create with --objective, --policy-json containing the policy seed, --apply, and --json flags. Obtain the policy JSON from the result.mission.policyJson field emitted by aops-cli start --json.

How do I resume an aops mission in a new session?▼

Use aops-cli mission resume --id <mission-id> --json for a compact, token-efficient pack, or aops-cli start --resume <mission-id> --json to start work directly. Use --full only when the raw hosted skeleton is truly needed.

What is the difference between aops Mission and Projectman?▼

Mission owns durable intent and policy in Agentspace, while Projectman owns execution truth including kanban tasks, sprint-backed implementation plans, microtasks, issues, and review requests. Do not store task progress in mission body or policy.

Can I use aops mission policy as a typed schema?▼

No, mission policy is currently free-form and advisory, following the working-discipline convention with groups like discipline, guardrails, review, and memory. It is not a typed enum or validated schema yet.

When should I use aops-cli start --reminder instead of mission resume?▼

Use aops-cli start --reminder --task and --area when a running session only needs a rules, playbook, or experience refresh. This path is read-only and does not mutate the mission, unlike resume.