solo-pm-loop

Guides single-agent work through Projectman tasks, checkpoints, and risk-proportional reviews.

Updated Aug 23, 2026

Search Tags:#project management #code review #checkpoint #workflow discipline #sprint #aops #solo agent

One-click install

npx skills add https://github.com/eeemzs/aops --skill solo-pm-loop-eeemzs

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: solo-pm-loop
Source: https://github.com/eeemzs/aops/tree/main/assets/disciplines/solo-pm-loop
Command: npx skills add https://github.com/eeemzs/aops --skill solo-pm-loop-eeemzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When one AI agent works alone on a project, plans drift, progress gets lost between sessions, and reviews are skipped. This discipline keeps a solo agent aligned with a single source of truth for plans, issues, and reviews while preserving resumable context. ## Core Features & Use Cases - Projectman as truth: Plan, issue, and review state live in Projectman; memory only carries resume context. - Bounded microtask flow: Read the active task or sprint, work the smallest useful slice, validate behavior, and log issues for material findings. - Risk-proportional review: Request asynchronous review only when risk warrants it, and write checkpoints at meaningful phase boundaries. - Use Case: An agent resumes a half-finished feature, reads the current sprint, completes one microtask, files an issue for a discovered bug, and writes a checkpoint so the next session can continue cleanly. ## Quick Start Use the solo-pm-loop discipline to continue my current Projectman sprint, complete the next microtask, and write a checkpoint when done.

Frequently Asked Questions about solo-pm-loop

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

FAQPage Schema

When is solo-pm-loop not the right discipline?▼

It is designed for one agent handling low- or medium-uncertainty work. High-uncertainty work, multi-agent collaboration, or actions with operator effects like commits, publishes, or deletions require their own authority or a collaborative discipline.