Turn a skeleton PRD into a full, verifiable spec through a guided interview — run this on a Work Package right before building it. Never implement from a skeleton.
Regenerate the PRD dependency map from the frontmatter of every Work Package — the interactive map.html plus the GitHub-rendered ROADMAP.md. Run after any PRD changes status, dependencies or scope.
Add one new Work Package to an already-planned project — short interview, writes the skeleton PRD and refreshes the dependency map. Use /prd:setup instead if the project has no PRDs yet.
Plan an entire project as Work Packages — guided interview that decomposes the project into skeleton PRDs with explicit dependencies, then generates the dependency map. Run once at the start of a project (or when adopting prd-kit on an existing one).
Read-only progress report of a PRD-planned project — status counts, what is building, what is ready to start, what is blocked, and drift against the tracker if issues are linked.