# Build Spec Kit codec You were asked to build the spec `dwrtz/spec-kit-codec`, version 0.1.1, from Spekkr. Converts a Spekkr spec folder to a GitHub Spec Kit feature folder and back, byte for byte. One Python script and an agent skill. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/dwrtz/spec-kit-codec/start.md`, before you go on. Published by dwrtz, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `spec-kit-codec`, inside the project you are working in. ```sh mkdir -p spec-kit-codec && curl -fsSL https://spekkr.com/dwrtz/spec-kit-codec/bundle.tar.gz | tar -xz -C spec-kit-codec ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/dwrtz/spec-kit-codec/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `dwrtz/spec-kit-codec` and the person's choices. ## 2. Record the person's choices Write `spec-kit-codec/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/spec-kit-codec", "version": "0.1.1", "inputs": {} } ``` This spec has nothing to customize, so the file stays as it is. ## 3. Build The files named below are the ones now in `spec-kit-codec`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements R1-R12 with acceptance checks: feature folder, byte-for-byte copies, plan.md and the safety block, the design.md stub, --activate, the hand-written fixed point, the filled-in manifest, collisions, no reformatting, edge bytes, all-or-nothing writes, the agent skill. - `design.md`: Command line, mapping, folders, activation, the exact safety block and stub bytes, filled-in manifest rules, reading and writing, every error message, and what the checker checks. - `tasks.md`: Build order, each step with a check. - `reference`: The reference build, MIT: spec_kit_codec.py, the SKILL.md agent skill, the check.py checker and fixtures.tar.gz (the 26 synthetic golden fixtures — a pebble jar and a lantern — matching tests/fixtures/ in github.com/dwrtz/spec-kit-codec).