A living record of architectural decisions, milestones, key insights, and strategic direction. Auto-maintained via claude-devlog-skill. Entries are reverse-chronological.
[2026-10-04] 0.1.3: /ck:brief becomes a gate-owning skill; the brief workflow checks after every revision; review pages render bold around code
Category: fix
Tags: ck, brief, review-page, drill
Risk Level: low
Breaking Change: no
The first real /ck:brief run (drill 22, on the ck Workbench project) wrote a good brief and left four things broken around it. All four are fixed here, and the fixes follow the shapes the other commands already use.
/ck:briefis now a skill (skills/brief/SKILL.md), and the workflow isck:brief-draft. The skill mints a timestamped run directory with arun.json, launches the workflow with absolute paths, and owns the review page, the same way/ck:opportunitydoes. Typed directly, the old workflow could not mint anything: the run landed in.ck/runs/brief-latestwith the run idbrief-directand a placeholder where the date should be.- The checker runs again after each revision (
validate -> revise -> validate, at most two revisions, word count first), as in the team and market-research workflows. Before, one check ran before the one revision, so a run that needed a trim always reportedvalid: falseon a valid file. - River is told the length first: about 1,000 words, never over the contract's 1,200. The cap stays; the target moved down so a normal draft lands under it instead of 200 words over and paying for a trim (drill 22: 1,403 words, then a $1.14 revision).
render-review.pylifts code spans out before it applies bold and emphasis. A bold phrase containing a code span rendered with literal asterisks because the line was split at the code span first. Test added.tests/run.shruns on macOS: the GNU-onlysed '0,/re/'form is replaced withawk, so the suite runs on the Mac where ck is now developed.
- Raising or dropping the 1,200-word cap. The content fits (1,173 words with eight sections and five sourced comparables); the hard edge was the problem, not the number.
[2026-09-09] Repository created from PRD revision 3: profiles imported, generator, four workflows, six contracts, tests
Category: milestone
Tags: ck, phase-1, skeleton, generator, workflows
Risk Level: low
Breaking Change: no
First commit of the ck plugin, built from the phase-one PRD (code-katz/.github, plans/2026-09-05-ck-plugin-prd-phase-1.md, revision 3) after Phase 0 answered seven of eight spikes. The 21 persona profiles are imported once from the old team tool at commit b4b211fbf4ec6f4d365a550b55e9981610ed7dda and owned here from now on.
- Source of truth:
profiles/<name>.mdandtiers.conf.scripts/generate.shderivesagents/<name>.md(subagent form, on its tier),skills/<name>/SKILL.md(session switch, verbatim), andprofiles/ROSTER.md. It refuses to overwrite uncommitted hand edits to generated files. - Tiers: Fable 5.1 for River, Akira, Morgan, Sage, Jordan, Reiner; Opus 5 for the eleven craft seats; Sonnet 5 for the four execution seats.
- Workflows, taken verbatim from the PRD appendices:
panel,brief,draft(serves the PRD and the architecture document),team. Nested workflows are called by name, as Phase 0 showed. - Skills:
prd,next,review-page(the one place the gate mechanics live), and the contractsbrief-artifact,prd-artifact,architecture-artifact,team-artifact,memo-artifact. - Hooks:
SubagentStarton^ck:writes the usage log;SessionStartwarns while the old team tool is installed. - Tests:
tests/run.sh, static checks 1 to 11 from PRD §9, with two fixture projects.
- Profiles are owned here. One-time import; no vendoring, no lock, no relationship to the old tool.
- Generated files are never hand-edited. The generator refuses to overwrite uncommitted changes to them unless forced.
- PRD:
code-katz/.github,plans/2026-09-05-ck-plugin-prd-phase-1.md - Phase 0 record:
code-katz/.github,plans/2026-09-09-ck-phase-0-spikes.md