stone stonematt

Ready is ready: the executor isn't a kanban lane

Kanban boards have stuck around because they do one thing well: show work moving from idea to delivered. As agentic coding has taken off, I keep seeing teams give agents their own lane on the board, a ready-for-agent state parked next to ready-for-human. I don't think that's right, and we already learned why.

The assignee has never been a lane. Think about how a scrum team runs: you assign a ticket to team A or developer X, and it doesn't slide into a "ready-for-X" column. It's ready. The assignee is a filter you slice the board by, not a place the work sits. Nobody ships a "ready-for-Alice" lane beside a "ready-for-Bob" lane. An agent is that same assignee, generalized to a non-human consumer. Ready is ready. The thing that picks it up is a filter slice.

This isn't just tidier, it's cheaper where it counts. A triage vocabulary runs on a small budget of states, five or so before it stops being memorable. Spend two on ready-for-agent / `ready-for-huma

Upgrading Matt Pocock's skills v1.0 → v1.1 inside a repo that already wrapped them

Notes from a real upgrade, shared in case others adopted v1.0 deeply and hit the same friction.

The short version

The skills upgraded cleanly. What didn't upgrade was everything I'd built around them. Over a few months I'd wrapped the suite in my own layer: a WORKFLOW.md with the pipeline flowchart and a command map, CLAUDE.md process rules, forked commit and merge skills, a custom status:* kanban. That layer names and orchestrates Pocock's skills, and after the v1.1 pull it was still speaking v1.0. Nothing flagged the drift. The tell was concrete: I finished a Wayfinder map, went to run the next step, and my own project workflow didn't know /to-spec existed.

So the lesson I'd pass on: upgrading a skills suite in a system that already wraps it is a migration of your wrapping layer, not a swap of the skills.

	---
	title: 3.insertMeeting
	type: meeting-note
	append: <current>
	documentation: https://help.noteplan.co/article/134-meeting-notes
	---
	<%
	let attendeeNames = eventAttendees.match(/\[(.+?)\]\(mailto:(.+?)\)/gi)
	let emails_to_ignore = ['me@mycompany.com'];