ai4kanban 0.6.1 → 0.7.0

package/README.md

@@ -65,7 +65,7 @@ akb skill install    # add it, or bring an older copy up to date
 That writes one file into `.claude/skills/kanban/` (Claude Code) and
 `.agents/skills/kanban/` (Codex): `SKILL.md`, a short note telling a coding agent the board
 is here and that `akb` owns it. The board app does the same thing from a button:
-**Configuration → Skill**.
+**Configuration → Agent setup**.
 
 Nothing else is copied in. The flows ship inside the command (`akb guide`), so a newer
 command is newer flows in every project at once — and the command itself stays where npm put

package/bin/ai4kanban.mjs

@@ -329,7 +329,7 @@ function cmdInstall(root, tracks) {
   say('That is the board. Nothing was written outside docs/kanban/.')
   say('')
   say('To drive this board from your coding agent, add the skill — from the button in the')
-  say('board UI (Configuration → Skill), or here:')
+  say('board UI (Configuration → Agent setup), or here:')
   say('')
   say(`    ${PROGRAM} skill`)
 }
@@ -538,7 +538,7 @@ Options
 
 Installing writes the board and nothing outside docs/kanban/. Driving that board from a
 coding agent is a later extra — \`akb skill install\`, or the button in the board UI under
-Configuration → Skill. The flows the agent works by are not copied anywhere either: they
+Configuration → Agent setup. The flows the agent works by are not copied anywhere either: they
 ship inside this command (\`akb guide\`), so updating the command updates every flow in
 every project at once.
 
@@ -627,6 +627,8 @@ const RUN_COMMANDS = new Set([
   'setup',
   'archive',
   'reject',
+  // Put a spec agent on a card — a named agent that fills one part of its spec (#187).
+  'spec',
   'runs',
   'log',
   'stop',