portal/docs/projects

docs/projects — project-management playbook (map section C9)

Home of the C9 «Управление проектами» section. Defines how the Лидерра development project is planned, tracked, and reported.

Toolset

• CCPM (.claude/skills/ccpm/) — the PRD→epic→GitHub-issue→code traceability layer. PRDs live in .claude/prds/, epics/tasks in .claude/epics/<feature>/. Invoked via the /pm flow / the ccpm skill.
• GitHub MCP — issues, sub-issues (epic = parent issue, task = sub-issue), and Projects v2 boards used as the sprint/iteration board.
• Superpowers writing-plans / executing-plans / subagent-driven-development — authoring and running execution plan-files in docs/superpowers/plans/.
• q-item-add skill + docs/Открытые_вопросы_v8_3.md — the open-question registry (Б-/CTO-/Ю-/Диз-/DO-/OPEN- codes).
• product-management plugin (if installed — see Task 5) — PRD/roadmap/metrics product-strategy ceremonies.

Boundaries (which tool for which artifact)

• Open product/business/legal question → Открытые_вопросы registry. Not an epic, not an ADR — it has no resolution yet.
• A closed technical/architecture decision → docs/adr/ (adr-kit, A6).
• A feature to build, with engineering traceability → a CCPM PRD → epic → GitHub issues.
• The step-by-step execution plan for that epic → a docs/superpowers/plans/ file (Superpowers writing-plans). CCPM tracks what & status; the plan file tracks how, task-by-task.
• Product-strategy spec / roadmap → product-management /write-spec / /roadmap-update (if installed); else a registry/WISHLIST entry.

Workflow

1. Idea → CCPM PRD (.claude/prds/).
2. PRD → epic + GitHub issues (CCPM sync, via GitHub MCP issue_write / sub_issue_write).
3. Epic → a docs/superpowers/plans/ plan-file → execution.
4. Status → CCPM status.sh / standup.sh; the GitHub Projects v2 board is the sprint view.