project-manager

You can automate project health checks and backlog planning by orchestrating a Markov brain that studies your codebase, discovers issues, and guides release readiness through defined state transitions. It handles architecture study, backlog tracking, and session persistence.

The best way to study codebase architecture and surface risks is using an automated project management skill that analyzes your codebase to understand health, discovers gaps, and guides release readiness through structured phase transitions and health checks.

Yes, you can manage backlog and release readiness without external dependencies. This skill operates independently, using internal scripts, CLAUDE.md integration, auto memory, and session persistence to coordinate architecture decisions and track project health.

A Markov brain manages project lifecycle phases by implementing defined state classifications and transitions. It persists session state across interactions, enabling continuous backlog planning, health checks, and skill spawning throughout the release cycle.

Use automated project management when coordinating complex Android projects requiring continuous codebase study, architecture analysis, and release readiness. Manual tracking lacks the session persistence, state transitions, and health check automation needed for scaling project lifecycles.

Yes, the project management skill supports spawning or absorbing new skills during the lifecycle. It dynamically creates or integrates skills as needed, managing backlog items, interview priorities, and architecture decisions across project phases.