interlocks

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.

create a phased implementation plan based on research and design decisions

Explore ideas, investigate code, and clarify direction before implementation. Thinking-only mode for pre-proposal or mid-change discovery.

end-to-end research → design → plan → implement → review → commit workflow for a single chunk. Driven by spok-apply.

phased implementation of a structured plan you must use this skill when asked to implement a plan file in a task directory

Propose a new change: scaffold proposal/specs/design via the Spok CLI artifact graph, then invoke spok-create-scoped-chunks to slice the work into independently shippable chunks and write tasks.md.

Simplify the implementation of the current chunk. Vendored stub — relies on the user-installed simplify tooling.

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

Run interlocks quality gates on a Python project — lint, format, typecheck, test, coverage, acceptance, properties, audit, deps, arch, CRAP, mutation — via the `interlocks` CLI (alias `il`).