project-manager
Project Manager
Version: 1.1.0
Repository: https://github.com/yysun/rpd
Source: https://github.com/yysun/rpd/tree/main/skills/project-manager
Manage the selected project through plan → coordinate → track → report.
Treat a project as a first-class folder containing structured Markdown state. Never infer that a repository is the project. Require the user or calling context to select the project folder explicitly, except that Studio may select from a validated projects root. Multiple project folders may live in one repository or workspace; read and write only the selected one. The default workspace container is .projects, never projects.
Project Manager uses unique marker-bound .project-manager-work-<24-hex> siblings for same-filesystem atomic work and crash recovery. They are internal recovery roots, not projects; valid explicitly selected projects are never rejected merely for a similar basename.
Operating boundary
- Project Manager owns project state, decomposition, dependency coordination, prioritization, blockers, evidence ingestion, impact analysis, and reporting.
- Executors own task work. Governed execution and lightweight human completion both persist through the same Task Contract → Evidence Manifest boundary.
- RPD is optional and owns
understand → implement → test → correct → verifyfor a software task. Do not reproduce RPD inside this skill. - Git, source code, issue trackers, and storage providers are optional context. Never make them authoritative project state.