cdp
cnos.cdp package entrypoint — Coherence-Driven Product. Use when structuring a body of work into owned workstreams and tracks, deciding a single source of truth per initiative, or reasoning about planning nomenclature and ownership.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- cdp
- calls
- [ "skills/cdp/planning-hierarchy/SKILL.md" ]
- scope
- global
- inputs
- [ "a body of work to structure (issue backlog, initiatives)", "existing ownership and canonical-doc assignments" ]
- outputs
- [ "workstream/track planning doctrine", "owned initiatives, each with a single canonical doc" ]
- triggers
- [ "workstream", "track", "planning hierarchy", "single-threaded owner", "canonical document", "extreme clarity", "roadmap", "prioritization" ]
- visibility
- public
- description
- cnos.cdp package entrypoint — Coherence-Driven Product. Use when structuring a body of work into owned workstreams and tracks, deciding a single source of truth per initiative, or reasoning about planning nomenclature and ownership.
- kata_surface
- none
- artifact_class
- skill
- governing_question
- What owns product-management doctrine — planning hierarchy, canonical sources of truth, single-threaded ownership — and how does it realize as issue labels and the board?
02 资源文件 7
- 参考文档cn.package.json140 B
- 参考文档references/.gitkeep—
- 参考文档references/token-cost-model.md4.2 KB
- 脚本scripts/.gitkeep—
- 脚本scripts/estimate-tokens.sh2.4 KB
- 脚本scripts/format-audit-report.sh5.4 KB
- 脚本scripts/inventory-context.sh5.3 KB
03 SKILL.md 正文
cnos.cdp
Core Principle
cnos.cdp (Coherence-Driven Product) is the package home for product-management doctrine: how a body of work is structured, owned, and made legible, distinct from how it is developed (cnos.cdd), researched (cnos.cdr), or shipped as software (cnos.cds).
cnos.cdp owns:
- planning hierarchy — the
workstream ⊃ track ⊃ issuestructure, single-threaded ownership per level, and one canonical source of truth per initiative (skills/cdp/planning-hierarchy/SKILL.md).
Boundary
cnos.cdp owns the doctrine; it does not own the label mechanics or the board. The workstream/* and track/* labels, their definitions, and the treemap render are owned by cnos.issues (canonical docs/development/issues/TAXONOMY.md, cn issues map). The planning-hierarchy skill cites that realization; it does not fork it. If doctrine and taxonomy ever disagree, extend TAXONOMY.md to match the doctrine, then let the board consume it.
Source
The planning hierarchy adapts Naomi Gleit's "Canonical Everything" / "Extreme Clarity" program-management practice (workstreams with single-threaded owners, each with its own canonical doc, recursively). This package names the source; it does not restate her essays.
Source: Naomi Gleit, "Canonical Everything" — https://naomi.com/canonical-everything-c85441a84e70 (workstreams, single-threaded owners, recursive canonical docs). Interview context: Lenny's Newsletter, "Meta's Head of Product … Naomi Gleit" — https://www.lennysnewsletter.com/p/metas-head-of-product-naomi-gleit ("Extreme Clarity", single-threaded owners).
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.