Skip to content

sdlc-process 0.4.11 — explicit planning artifact ownership

Choose a tag to compare

@cchatfield cchatfield released this 07 Oct 20:59
79e5e86

Distribute the clarified planning-artifact routing in sdlc-process 0.4.11. Starting in Core is valid; work-item specs and other planning documents still belong in sidkik/planning. Preserve delivery evidence, implementation-session continuity and sufficient issue-owned repair briefs.

Regenerated from reviewed canonical Planning sources; this is instruction alignment, not a relocation of existing work or a skill-source migration. Retain 0.4.9 model-invocable workflows and 0.4.10 Haiku observer.

Canonical source: sidkik/planning#40, merge2a8e857d44d49f2cca29de9ea9bca12b4283e8ca. Independent Standards/Spec reviews: no findings, publication conditional on exact tree174957f5c3a2ab413c5f155cd9f617fbc2386626 and applicable checks/install verification. Validation: 88 Node tests, 9 packaging tests, 74-file generator check, manifest hashes and links.

One isolated Core-rooted native Claude trial successfully invoked work-artifacts and to-spec, read their complete sources and the planning convention, and wrote the spec under the separate Planning checkout. All65 original Core fixture hashes remained unchanged, with no added Core files. This is placement evidence only: entry/orchestrator calls were skipped, Bash was unavailable/rejected, and the missing-planning-checkout variant was not exercised. An initial isolated-config authentication failure is preserved, not counted as a behavior pass. No GitHub publication or full SDLC conformance was proved.

Trial client used candidate plugin0.4.11, Sonnet medium, actual Skill/Read/Write results, and existing maintained fixture input. Acceptance stayed outside the evaluator prompt. The trial pin and merged pin have identical source hashes; final differences are generated provenance/link pins. Disposable logs and fixture outputs are not committed.