Agentic-Assembly-Line-System

Use when the user wants a plan or design stress-tested before implementation, or asks to be grilled, interviewed, or interrogated about a decision tree.

Disciplined root-cause investigation for hard bugs and performance regressions, with findings pinned to the case board. Use when user reports a bug, says something is broken/throwing/failing, describes a performance regression, or asks to diagnose/debug/investigate something.

Use when writing a commit message — "write a commit", "commit message", "generate commit", "/commit", or invokes /faceless-commit, or when staging changes. Legacy alias: "/caveman-commit".

Use when reviewing code or a diff — "review this PR", "code review", "review the diff", "/review", or invokes /faceless-review. Legacy alias: "/caveman-review".

Use when the user wants terse, compressed, low-token responses — "faceless mode", "talk faceless", "be brief", "less tokens", "compress", or invokes /faceless. Also when token efficiency is explicitly requested. Legacy aliases: "caveman mode", "use caveman".

Use when turning raw material — research, notes, interview answers, fragments, or investigation findings — into a sourced written report or article, or when shaping, drafting, restructuring, or tightening such a draft. Triggers: "write up the findings", "investigative report", "turn these notes into an article", "draft the report", "shape this into an article", "edit the article", "help me write this up".

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `investigate`, `tdd`, `improve-codebase-architecture`, or `zoom-out` -- or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

Use when encountering environment, config, infrastructure, CI, or build issues -- not application-layer bugs (use investigate for those). Requires root cause investigation before any fix.

Use for Auth0 provider guidance in this project.

Use for Neon provider guidance in this project.

Use the Stripe Projects CLI in this repository to manage deploying and access to third party services.

Create, review, audit, and list Architectural Decision Records for any software project. Trigger on: "create an ADR", "document this decision", "ADR for...", "what ADRs exist", "review this ADR", "update INDEX.md", architectural trade-offs, or design pivots affecting multiple layers or files. Project-agnostic -- works with any tech stack. Backed by Karpathy principles: think before deciding, simplest sufficient ADR, surgical scope.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Apply Karpathy coding discipline to any task: think before coding, simplicity first, surgical changes only, goal-driven execution with verifiable success criteria. Invoke before any non-trivial implementation. Use /karpathy plan <task> to produce a verifiable step plan. Use /karpathy review to audit recent work. Auto-triggers when user asks to plan an approach, requests a step-by-step breakdown, or when the assistant is about to start a multi-file or multi-step change.

Convert Claude's persisted memory into a structured high-level outline and save it to the project Obsidian vault. Use to archive and organize accumulated session knowledge as a navigable vault note.

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

Interactive first-run experience for new Claude-ITect installs. Asks 3 short questions about workflow style, project type, and communication preference. Generates a personalized 5-skill starter roadmap. Runs once per install via sentinel file; re-run manually with /onboard --reset.

Track project phase lifecycle: status snapshots, transitions, and ADR impact analysis. Trigger on: "what phase are we in?", "is phase X unblocked?", "did ADR-### move any phase?", "give me a status snapshot", "what's next?", "what's blocked?", "phase status", creating or editing phase documents, or comparing phase state across plan revisions. Project-agnostic -- binds to any project with a Phase Registry. Backed by Karpathy principles: surface state truthfully, no silent assumptions.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Scan the active project to discover relevant MCP servers, CLI tools, libraries, and repositories that would benefit it. Presents candidates to the user for approval before implementing anything. Helps configure approved tools in .claude/settings.json. Trigger on: "what tools should I add?", "find me an MCP server for X", "set up tools for this project", "audit my MCP config", "what's missing from my toolset", or any request to discover, add, or review Claude Code tooling for the current project. Backed by Karpathy principles: think first, simplicity, surgical changes only. NEVER auto-implements -- proposes then waits for explicit user approval.

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Command set for the project wiki (Obsidian vault). Handles read, approve, reject, add, search, and graph subcommands against the docs/Obsidian Vault/ directory. Use when reading or modifying wiki content, approving suggestions from _suggestions/, or exploring wiki structure.

Inference engine for the project wiki. Scans source files (skills, hooks, agents, ADRs, codebase) against existing wiki pages, identifies undocumented content, and generates PENDING suggestion files in _suggestions/ for human review. Assigns HIGH/MEDIUM/LOW confidence based on evidence strength.

Use when you have a spec or requirements for a multi-step task, before touching code

Create, review, audit, and list Architectural Decision Records for any software project. Trigger on: "create an ADR", "document this decision", "ADR for...", "what ADRs exist", "review this ADR", "update INDEX.md", architectural trade-offs, or design pivots affecting multiple layers or files. Project-agnostic -- works with any tech stack. Backed by Karpathy principles: think before deciding, simplest sufficient ADR, surgical scope.

Audit Claude Code skills for visibility flags, deterministic vs non-deterministic steps, and composability opportunities. Reads .claude/skills/ (or a user-specified path), produces a punch list per skill, then shows proposed rewrites with a changelog. Trigger on: "audit my skills", "review my skill files", "which skills auto-fire?", "find duplicated logic in my skills", "should any skills be internal-only?", or any request to review, improve, or rationalize a set of SKILL.md files. Never modifies any file -- proposes changes and waits for approval.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Set up and operate an LLM-maintained personal knowledge base wiki. Use when building a persistent, compounding knowledge base from source documents -- articles, papers, notes, transcripts, or any source material.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Apply Karpathy coding discipline to any task: think before coding, simplicity first, surgical changes only, goal-driven execution with verifiable success criteria. Invoke before any non-trivial implementation. Use /karpathy plan <task> to produce a verifiable step plan. Use /karpathy review to audit recent work. Auto-triggers when user asks to plan an approach, requests a step-by-step breakdown, or when the assistant is about to start a multi-file or multi-step change.

Convert Claude's persisted memory into a structured high-level outline and save it to the project Obsidian vault. Use to archive and organize accumulated session knowledge as a navigable vault note.

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

Track project phase lifecycle: status snapshots, transitions, and ADR impact analysis. Trigger on: "what phase are we in?", "is phase X unblocked?", "did ADR-### move any phase?", "give me a status snapshot", "what's next?", "what's blocked?", "phase status", creating or editing phase documents, or comparing phase state across plan revisions. Project-agnostic -- binds to any project with a Phase Registry. Backed by Karpathy principles: surface state truthfully, no silent assumptions.

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` -- or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

Use when executing implementation plans with independent tasks in the current session