claudboard

Generates a tailored `.claude/skills/feature-workflow/` skill into any project by reading the claudboard analysis report, gathering config from the user, and rendering Markdown templates with capability blocks and substitution variables. Produces a complete, project-aware feature-workflow skill (SKILL.md, agents, scripts, config.json) ready to drive `/start-feature` flows. Use when: /claudboard-workflow, "set up feature workflow", "install start-feature skill", "generate feature-workflow", "configure feature workflow for this repo", "add the feature workflow skill", "generate my start-feature skill", "create the feature workflow for me", "I want a start-feature skill", "bootstrap feature workflow", "generate workflow skill", "set up my workflow skill", "add start-feature to this project".

Deep-analyzes a project repository: detects tech stack, architecture patterns, coding conventions, testing strategies, CI/CD pipelines, quality signals, and anti-patterns. Default mode produces a convention catalog (.claudboard/catalog.json) and a thin human-readable summary (.claude/reports/claudboard-analysis.md). Use --audit for per-service deep analysis (per-service reports, full Watch findings, cross-service Kafka graphs). Written to .claudboard/audits/ when --audit is passed. Use when: /analyse, "analyze this codebase", "scan this repo", "project health check", "audit this project", "what patterns does this repo use", "understand this project", "code quality review", "architecture audit".

Deep-analyzes an existing project or repository and bootstraps Claude Code's understanding by generating production-ready .claude/ artifacts: CLAUDE.md, rules with paths: frontmatter, full-scope skills (with references/ and scripts/), and memories. Goes beyond surface scanning to detect architecture patterns, coding conventions, testing strategies, CI/CD pipelines, infrastructure, good patterns, anti-patterns, and tech debt. Use this skill whenever the user says /claudboard, "onboard this project", "bootstrap Claude for this repo", "set up Claude Code for this project", "analyze this codebase", "generate rules for this project", "create CLAUDE.md", "scan this repo", "understand this project", "help me onboard to this codebase", or asks for a project health check, architecture audit, or code quality review. Also triggers on "what patterns does this repo use", "generate coding rules from this codebase", or when starting work on an unfamiliar or brownfield project. Also routes: "set up feature workflow", "instal

Generates Claude Code artifacts (CLAUDE.md, rules, full-scope skills) from a claudboard convention catalog. Reads .claudboard/catalog.json as primary input; falls back to legacy .claude/reports/claudboard-analysis.md with one-time migration. Requires a prior `/analyse` run — does not analyse inline. Use when: /generate, "generate rules", "create CLAUDE.md", "bootstrap Claude for this repo", "generate skills for this project", "set up Claude Code for this project", "onboard this project".

Refreshes Claude Code artifacts for a project that already has .claude/ context. Performs delta discovery against existing artifacts, identifies what's new, stale, or missing, and updates only what changed. Use when: /refresh, "update my rules", "refresh Claude context", "sync .claude/ with codebase changes", "what's changed since last scan", "are my rules up to date", "re-scan this project".

Deep tech debt analysis of a codebase. Produces a module-grouped, ticket-ready report with severity, effort estimates, and fix suggestions for every item. Detects code smells, missing design patterns, performance debt, and architecture flaws. Use when: /techdebt, "tech debt", "technical debt analysis", "what needs refactoring", "code quality report", "debt scan", "refactoring candidates", "find tech debt", "architecture debt", "performance issues in code", "generate refactoring tickets".

Kick off intentional feature work with the full ticketed workflow: clarify scope, create a goal-oriented JIRA ticket, set up the branch, develop the solution, commit, and open a PR. Use this skill when the user says "start feature: X", "start a feature", "kick off work on X", or "full workflow for X". This is a deliberate mode the user enters — do NOT trigger for casual coding requests, experiments, spikes, or when the user just asks to "add X" or "implement X" without explicit feature framing. The phrase "start feature" is the signal.

Bootstrap a workspace meta-repo that holds the shared `.claude/` directory for a multi-repo workspace (a parent directory containing N independent git repos). Creates a child git repository inside the workspace root, migrates any existing workspace `.claude/` contents into it, and symlinks the workspace root's `.claude/` to the meta-repo's `.claude/`. Run once per workspace — teammates use `/claudboard-workspace-link` afterwards. Use when: /claudboard-workspace-init, "bootstrap workspace", "set up workspace meta-repo", "create workspace .claude repo", "initialise workspace .claude", "share my .claude across the team", "make .claude versioned for this workspace".

Link a teammate's machine to an existing workspace meta-repo. Clones the meta-repo as a child directory inside the workspace root and runs setup.sh to create the symlink. One-command teammate bootstrap after the first developer has run /claudboard-workspace-init. Use when: /claudboard-workspace-link, "join workspace", "link to workspace meta-repo", "bootstrap workspace on this machine", "set up workspace .claude from remote", "clone workspace meta-repo", "connect to shared .claude".