VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:project-management

Manage durable plan progress

Track progress from durable plan files, mirror work into live task surfaces when available, sync completion back across every phase, and produce concise status reports.

01

Scan plans

02

Discover live tracking

03

Hydrate tasks

04

Track progress

Rule 01

Plan files are durable; runtime task views are optional mirrors

Rule 02

Discover task-management capability live at runtime

Rule 03

Trace every completed item back to its source phase

Rule 04

Reports should be concise, data-driven, and action-oriented

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Scan plans Read durable plan files, scan ./plans/*/plan.md, parse YAML status, priority, effort, branch, tags, and inspect phase checkboxes.
  2. 2 Discover live tracking Discover the task-management surface at runtime; use it only when present and never infer capability from client names or cached tools.
02

Work

Agent / skill execution

  1. 3 Hydrate tasks If the live view exists and is empty, mirror unchecked plan items with source context, ownership, dependencies, and status.
  2. 4 Track progress Track pending, active, blocked, and completed state in the live surface when available; otherwise update the active plan directly.
03

Verify

Gate, review, validation

  1. 5 Verify before marking done Cross-reference completed work against planned tasks and acceptance criteria before marking tasks, phases, or plans complete.
  2. 6 Sync back status On completion, sweep all phase files, reconcile runtime items to checklist entries, backfill earlier phases, and update plan.md frontmatter from real counts.
04

Close

Report, handoff, artifact

  1. 7 Generate report Write concise session, plan-completion, or multi-plan reports as tables with critical issues and unresolved questions.
  2. 8 Trigger docs updates Delegate docs updates when phase status, major features, API contracts, architecture decisions, security patches, or breaking changes warrant it.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:project-management [task: status, hydrate, sync, report]

Arguments

[task: status, hydrate, sync, report] Required

Oversight operation

Natural-language project-management intent, commonly status, hydrate, sync, or report. It names what to inspect or reconcile; it is not a mode flag and does not by itself prove work is complete.

/ak:project-management "Sync verified work back to the active plan, report any unmapped completed items, then create a concise session status report."

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Status across plans Recommended 
/ak:project-management status
Use when:
Use to check project status or progress across active plans.
Expected:
Scans durable plan files, counts phase checkboxes, parses plan.md frontmatter, and returns a concise data-driven status with critical issues and unresolved questions.
Hydrate live work 
/ak:project-management hydrate
Use when:
Use at session start when unchecked plan items should be mirrored into available live task tracking.
Expected:
Discovers the live task-management surface at runtime, mirrors unchecked plan items with source links and dependencies, and leaves plan files as the durable truth.
Sync completed work 
/ak:project-management sync
Use when:
Use after execution to reconcile runtime completion back into durable phase files and plan.md status.
Expected:
Sweeps every phase file, maps completed runtime items to checklist entries, backfills stale earlier phases, updates plan.md from real counts, and reports any unmapped work.
Write progress report 
/ak:project-management report
Use when:
Use when a session summary, plan-completion report, or multi-plan overview is needed.
Expected:
Creates a pm-{date}-{time}-{slug}.md report with tables over prose, completion data, status changes, critical issues, documentation triggers, and unresolved questions.

Handled Scope

  • Runtime work tracking
  • Hydration workflow
  • Full-plan sync-back
  • Progress percentages
  • Status reporting
  • Documentation triggers
  • Cross-session resume

Artifacts Produced

Project Management Output

Pattern

{reports-path}/pm-{date}-{time}-{slug}.md

Reports emphasize completion data, mapped work, status changes, critical issues, documentation triggers, and unresolved questions.

Next