task-board-initlisted

[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] # task-board-init 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,TRACKER,TASK_TEMPLATE,INDEX}.md` + `{backlog,todo,progress,closed,specs}/` | brewpage `.claude/features/**` | This skill ORCHESTRATES. It does not hand-do the bulk analysis or the doc sweep -- it spawns subagents (Task) for those passes and integrates their output. All emitted artifacts are PARAMETRIZED from Step 1 findings; templates live in `references/`. > **Spawn from MAIN only.** This skill is inline (no `context`), so its Task spawns are first-level. Do not nest. > **Read reference templates** with the `Read` tool using `${CLAUDE_SKILL_DIR}/references/<file>` to load them into context. --- ## P0: Resolve target repo + parse directive `$ARGUMENTS` carries TWO optional, order-independent things: (a) a target repo PATH, (b) a free-t