[DICT: TT=task-tracker agent (generated), TB=task-board skill (generated), BRD=board.md, FEAT=.claude/features, EXCL=source-path exclusions, REL=release style (vX.Y.Z tag | commit SHA | no tag), DOM=domain id segment, FM=frontmatter, TS=task-spec skill (generated), SPEC_MODE=spec+design layer opt-in, PS=status phase, PU=upgrade phase, PR=uninstall/purge phase]

task-board-setup

Generator. Run from the MAIN conversation in (or pointed at) a TARGET repo. Deploys a self-contained, file-based Kanban into that repo:

Emits	Path	Mirrors etalon
Curator agent	`.claude/agents/task-tracker.md`	brewpage `task-tracker.md`
Dashboard skill	`.claude/skills/task-board/SKILL.md`	yasna `task-board` SKILL
Paths-scoped rule	`.claude/rules/tasks.md`	brewpage `tasks.md`
Board + control files	`.claude/features/{board,PROGRESS,TRACKER,TASK_TEMPLATE,INDEX}.md` + `{backlog,todo,progress,closed,specs}/`	brewpage `.claude/features/**`
Spec skill (SPEC_MODE only)	`.claude/skills/task-spec/SKILL.md`	`references/08-task-spec-skill.md`
Spec template (SPEC_MODE only)	`.claude/features/specs/SPEC_TEMPLATE.md`	`references/09-spec-templates.md`
Design template (SPEC_MODE only)	`.claude/features/specs/DESIGN_TEMPLATE.md`	`references/09-spec-templates.md`

SPEC_MODE (confirmed in P1) gates the three rows above AND every spec-related addition inside the other emitted artifacts. SPEC_MODE=off -> nothing spec-related is emitted and every artifact is byte-identical to the pre-spec-layer generator.