0xjgv

Ship the next unchecked chunk from spok/changes/<name>/tasks.md end-to-end via the vendored spok-flow skill. Use when the user wants to implement the next chunk of a Spok change.

Archive a completed Spok change. Applies any delta specs to the main specs unconditionally, then moves the change directory under changes/archive/.

Commit Changes in CI with no user interaction

first step of planning

convert structure outline into a detailed implementation plan

generate research questions based on a task, spec, or ticket

research the codebase

break a medium/large change into cross-layer, independently shippable chunks. emits a single tasks.md checklist that spok-apply can iterate through.

end-to-end problem validation → research → design → plan → implement → review → commit workflow for a single chunk, with an optional post-commit self-learn gate. Driven by spok-apply.

Produce an advisory post-commit review of workflow friction, issues, weak evidence, and improvement opportunities for a completed Spok flow chunk.

first step of planning

convert structure outline into a detailed implementation plan

generate research questions based on a task, spec, or ticket

research the codebase

create a phased implementation plan based on research and design decisions

validate an implementation against a task plan and current code. use this when given a plan path from a task directory or when asked to verify implemented work before review or PR

Bootstrap or align a repo with the harness-templates contract: the 5-script quality harness (check, pre-commit, ci, audit, post-edit) plus the behavior contract (task sizing, human-owned commits, Gherkin-first, arch-config integration guard). Use when starting a new python/bun/go/rust/monorepo project, adding a quality harness to an existing repo, or asked to match ~/Code/harness-templates conventions. Triggers: "add a harness", "set up check/ci/pre-commit", "align with harness-templates", "bootstrap quality gates", "add the behavior contract", "wire the engineering principles".

kern development pipeline.