Дмитрий
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# ADR-004: Project-management tooling (C9)
|
|
|
|
- **Status:** Accepted
|
|
- **Date:** 2026-05-17
|
|
- **Deciders:** Дмитрий
|
|
|
|
## Context
|
|
|
|
The `C9 «Управление проектами»` map section had zero tooling. Planning was done
|
|
ad-hoc via `docs/superpowers/plans/` files, the `Открытые_вопросы` registry, and
|
|
sprint notes in memory. GitHub Issues were barely used (FF-push workflow).
|
|
|
|
## Decision
|
|
|
|
- Project management adopts a **GitHub-issue-backed** model: CCPM
|
|
(vendored skill) drives PRD→epic→issue→code with traceability; epics are
|
|
parent issues, tasks are sub-issues.
|
|
- The **GitHub Projects v2** board (official GitHub MCP `projects` toolset) is
|
|
the sprint/iteration board.
|
|
- Execution plans stay as `docs/superpowers/plans/` files (Superpowers).
|
|
- The `Открытые_вопросы` registry remains the home of *open* questions; an ADR
|
|
records *closed* decisions; CCPM tracks *features in flight*.
|
|
- product-management (Anthropic) is added only if Claude-Code-installable.
|
|
|
|
## Consequences
|
|
|
|
- Positive: C9 populated; planning traceable; sprints visible on a board.
|
|
- Risk: CCPM is third-party (bus-factor) — mitigated by vendoring.
|
|
- Risk: a workflow shift toward GitHub Issues — accepted, this is the decision.
|
|
|
|
## Enforcement
|
|
|
|
None — C9 tools are advisory; verified by use and code review.
|