project-manager
Project Manager
Version: 1.13.0
Repository: https://github.com/yysun/project-manager
Source: https://github.com/yysun/project-manager/tree/main/skills/project-manager
Manage the selected project through plan → coordinate → execute → track → report.
Treat a project as a first-class folder containing structured Markdown state. Never infer that a repository is the project. For a new project, require an explicitly selected workspace root or target project folder; workspace-default placement derives <root>/.projects/<safe-project-slug>. For an existing project, use an explicit project folder when the user or calling context supplies one. If no project is selected, discover valid project folders only below the calling context's selected workspace root: select the sole valid project directly without asking, ask for selection when more than one is valid, and ask for a folder when none is valid. Studio and execute-rpd may also resolve one exact name, ID, or folder from a validated projects root; ambiguity is not selection. 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.
- Project Manager owns
.projectsdelivery coordination, not QA case design, test execution, Run history, or.testsstate. Quality evidence may inform a project task without making project state authoritative for testing. - 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.