Repository navigation
v4.70.0
Minor, cut from 4.69.0. A high-level spec becomes a detailed one you accept before the plan.
Added
kj spec refine --task-file spec.md [--e2e <tests...>](KJC-TSK-1251): the spec reviewer looks for gaps and kj writes a detailed spec next to yours (<spec>.detailed.md): goal, behaviour, edge cases and errors, out of scope, acceptance criteria (Given/When/Then), assumptions and open questions. With e2e tests each criterion names the test that covers it; without them, each one proposes the e2e scenario to write. What the spec does not decide goes to assumptions or open questions, never invented scope. It stops there, works without a terminal (--jsonfor agents) and never overwrites a file; once accepted,kj plan generate --task-file spec.detailed.mdturns it into user stories.