In short:
ak-project-managementtells you how much of a multi-phase plan is really done, keeps the checkboxes right, and keeps progress alive across sessions. Once tracking is done, you go back toak-cookto keep working, or openak-plans-kanbanto view the plan. It does not treat task status in the runtime as proof that work is done, and it does not edit docs itself: when docs are affected, it hands that to the docs-manager agent.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when the work has several phases, dependencies, parallel tracks, or several related items, especially when it spans several sessions or needs a handoff. You do not need it for a short change you finish in one go: in that case the skill skips tracking in the runtime.
flowchart LR
A["ak-plan creates the plan"] --> B["ak-cook works each phase"]
B --> C["ak-project-management"]
C --> D["Updated plan + pm-... report"]
C --> E["docs-manager, when docs are affected"]
C --> F["Next session: hydrate, then continue"]It rests on 4 ideas:
| Idea | Question | Example |
|---|---|---|
| The plan file is the source of truth | When the runtime and the plan disagree, which one wins? | The runtime shows 5 tasks done, the phase file has only 3 [x] boxes: the plan wins |
| Hydrate | New session, old tasks gone, how do you continue? | Read plan.md and the phase files, rebuild tasks from the items still [ ], keep dependency order |
| Sync-back | How do you close or hand off without misreporting progress? | Back-fill the old boxes in phase 1, then recompute status from the real checkboxes |
| Docs impact | Does finishing a phase mean editing docs? | A status change alone, no; a change to commands, config, API, architecture or security, yes |
A plan has 3 states: pending, in-progress, completed. Progress is the number of [x] boxes divided by the total. The key stop point: if a finished task does not match any phase, the skill reports it and does not mark the whole plan done.
Sample prompt for checking progress:
/ak-project-management status
Check the progress of every active plan in <project>.
For each plan: percent done, priority, branch, next step.
Say which plans are blocked and why.This skill has no flags. After the skill name you type a task: status, hydrate, sync or report. The skill also takes requests to update the status of items that just changed.
Below is the detailed version: the run flow, 5 situations with prompts, the tasks you type after the skill name, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-project-management: track plan progress and carry work across sessions" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-project-management". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-project-management
