base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Close the completed initial planning checklist

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 18:26:22 +00:00
parent 6c04dceb85
commit b98845bae9
2 changed files with 21 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
docs/roadmap/initial-plan.md
View File

@@ -1,30 +1,25 @@
# Preparing the initial CommandKit feature roadmap # Preparing the initial CommandKit feature roadmap
Status: roadmap review complete; ready to prepare the staged implementation plan. Status: roadmap preparation and implementation-plan handoff complete.
Date: 2026-10-07. Date: 2026-10-07.
Progress is recorded in [the initial roadmap](initial.md). Roadmap review selected The [feature roadmap](initial.md) records the selected initial target and its
the delivery scope, typed API/outcome model, selectors/report behavior, and full completion. The [implementation plan](implementation.md) was prepared from that
profile coverage including `ExtraParams`. Exact Go declarations will be specified review and has been executed. Checked entries below record the completed
in the staged implementation plan using those selections. Checked entries record preparation process; they are not assignments to restart planning.
completed planning work; the staged plan remains the next deliverable.
## Purpose and use ## Historical preparation process
Use this checklist to prepare `docs/roadmap/initial.md`, which will describe the The checklist below was used to select the initial feature target and prepare an
targeted end state of CommandKit's initial implementation: its packages, features, ordered Luna implementation plan. Its instructions and suggested outline are
integration contracts, and ownership boundaries. After reviewing that roadmap, retained as planning history. Current public contracts belong in Go declarations
use it to prepare a separate, ordered implementation plan for a Luna agent. and GoDoc, operator behavior in the [CLI reference](../cli.md), and usage guidance
in the [consumer guide](../consumers/guide.md).
Work through the sections below in order. Check an item when its result is
recorded in the draft or its supporting planning notes. Record unresolved choices
with a recommendation, alternatives, and the decision needed. Revisit earlier
sections when later evidence affects their conclusions.
The [architecture policy](../policy/architecture.md) and accepted ADRs control The [architecture policy](../policy/architecture.md) and accepted ADRs control
architectural choices. This document owns the preparation process; `initial.md` architectural choices. This document owns the preparation process; `initial.md`
will own the initial feature targets. Exact implemented contracts will belong in owns the initial feature targets. Exact implemented contracts belong in
Go declarations, GoDoc, and the CLI reference under the Go declarations, GoDoc, and the CLI reference under the
[documentation policy](../policy/documentation.md). [documentation policy](../policy/documentation.md).
@@ -188,13 +183,13 @@ resolved to the depth needed by the later implementation plan.
- [x] Review the complete draft against its requirements checklist and package map. - [x] Review the complete draft against its requirements checklist and package map.
- [x] Make upstream work, deferrals, and unresolved decisions visible in the draft. - [x] Make upstream work, deferrals, and unresolved decisions visible in the draft.
- [x] Review the targeted end state before translating it into implementation tasks. - [x] Review the targeted end state before translating it into implementation tasks.
- [ ] Prepare the subsequent staged plan with ordered tasks, prerequisites, precise - [x] Prepare the subsequent staged plan with ordered tasks, prerequisites, precise
deliverables, and completion checks mapped to the roadmap's feature identifiers. deliverables, and completion checks mapped to the roadmap's feature identifiers.
**Result:** a reviewed feature roadmap that can be translated into a strictly **Result:** a reviewed feature roadmap and the completed staged implementation
ordered implementation plan suitable for Luna. plan suitable for Luna.
## Recommended outline for `initial.md` ## Historical outline for `initial.md`
1. Authority and initial scope. 1. Authority and initial scope.
2. Target package layout and dependencies. 2. Target package layout and dependencies.

8
docs/roadmap/remediation.md
View File

@@ -121,13 +121,15 @@ Owner: [04-facade.md](04-facade.md).
Owner: [initial-plan.md](initial-plan.md). Owner: [initial-plan.md](initial-plan.md).
- [ ] Mark roadmap preparation and implementation-plan handoff complete. - [x] Mark roadmap preparation and implementation-plan handoff complete.
- [ ] Remove claims that exact declarations still await specification and that - [x] Remove claims that exact declarations still await specification and that
the staged plan is the next deliverable. Link to the completed plan and current the staged plan is the next deliverable. Link to the completed plan and current
API owners. API owners.
- [ ] Check the completed final handoff item and label the preparation process - [x] Check the completed final handoff item and label the preparation process
and recommended outline as historical planning material. and recommended outline as historical planning material.
**Completion:** Closed the planning handoff, checked its final item, and labeled the retained process and outline as historical.
## D-06: clarify completed feature and implementation records ## D-06: clarify completed feature and implementation records
Owners: [initial.md](initial.md) and [implementation.md](implementation.md). Owners: [initial.md](initial.md) and [implementation.md](implementation.md).