Document PromptKit requirements discovery
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
# PromptKit requirements inspection
|
||||
|
||||
Status: accepted feature roadmap; implementation has not started. Command
|
||||
Status: accepted feature roadmap; implementation is in progress. Command
|
||||
placement, public API, caller-variable syntax, and initial presentation are
|
||||
settled.
|
||||
settled. The implementation plan records delivery and final validation status.
|
||||
|
||||
The [implementation plan](implementation.md) owns the ordered delivery steps and
|
||||
stage completion evidence.
|
||||
@@ -35,24 +35,25 @@ is the authority for discovery semantics. Descriptions below explain how
|
||||
CommandKit will expose that API, rather than establishing a separate discovery
|
||||
specification.
|
||||
|
||||
## Current baseline
|
||||
## Baseline at roadmap acceptance
|
||||
|
||||
Baseline: CommandKit commit
|
||||
This table records the pre-implementation state at CommandKit commit
|
||||
[`12b52b3`](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/12b52b3174545d22960c91c3a782a151ab813447).
|
||||
|
||||
| Area | Current implementation | Gap to target |
|
||||
| Area | State then | Gap the roadmap addressed |
|
||||
| --- | --- | --- |
|
||||
| Dependencies | ckprompt already adopts PromptKit v0.14.0, ConfigKit v0.7.1, and YAML v4. Modules require Go 1.26.0. | No dependency or toolchain upgrade is needed for this capability. |
|
||||
| Native capability | PromptKit exposes `Engine.InspectRequirements`, its request, and its structured result. | Adapt this existing public API. |
|
||||
| Public integration | `Suite[I, S]` provides optional prompt/profile inspection and prompt/profile catalog callbacks. `FromEngine` supplies those four callbacks. | Add an independently optional requirements callback and its engine adapter. |
|
||||
| Command assembly | `ckprompt.Command` installs available `show` and `list` operations beneath the owned `promptkit` namespace. | Assemble the requirements operation from its own capability. |
|
||||
| Public integration | The accepted baseline had optional prompt/profile inspection and prompt/profile catalog callbacks. | Add an independently optional requirements callback and its engine adapter. |
|
||||
| Command assembly | The accepted baseline installed available `show` and `list` operations beneath the owned `promptkit` namespace. | Assemble the requirements operation from its own capability. |
|
||||
| Invocation infrastructure | Typed selectors, configuration selection, input checks, shared state, diagnostics, and buffered report delivery already exist. | Apply those paths to the new operation. |
|
||||
| Presentation | Named prompt/profile reports support text and YAML; catalogs use YAML only. | Define a requirements report with the native evidence and discovery context identities. |
|
||||
|
||||
The [deferred-work record](deferred.md#promptkit-requirement-inspection) records
|
||||
this capability's prior deferral. This roadmap takes it up for planning;
|
||||
the command remains unimplemented. Existing configuration, catalog, and named
|
||||
definition operations are not prerequisites for enabling requirements inspection.
|
||||
The former deferral is retained as an
|
||||
[immutable historical record](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/ee038df530bfd3518906dc77e8e8f55eef237dda/docs/roadmap/deferred.md).
|
||||
This roadmap takes the capability up for delivery. Existing configuration,
|
||||
catalog, and named definition operations are not prerequisites for requirements
|
||||
inspection.
|
||||
|
||||
## Target ownership and package boundaries
|
||||
|
||||
|
||||
Reference in New Issue
Block a user