kelsi-andrewss

Generate interactive HTML diagrams (flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, etc.) using Mermaid.js. Opens the result in the browser. Use when the user says "/diagram", "draw a flowchart", "make a diagram", "show me a flow", "sequence diagram", "class diagram", "state diagram", or any request for a visual diagram.

Graph-node skill: reads .ship-manifest.json (or story/epic IDs), launches one background agent per story to write plans/*.md files, applies critique checklist, updates DB with plan_file paths. Artifact-chain-aware version of /draft-plan. Consumes manifest from /plan-stories, produces plans/*.md for /env-preflight.

Spec-driven feature decomposition: accepts a FeatureSpec JSON (product, pattern, entity, fields, permissions, integrations, UI) and decomposes it into dependency-ordered stages using deterministic pattern DAGs. Creates stories via PM tools and writes .ship-manifest.json for downstream /draft-plans and /run-stories consumption. Use when the user says "/factory spec.json", "/factory --pattern crud-ui <inline JSON>", or "/factory --dry-run spec.json".

Merge a story worktree branch into its dev branch, push, clean up the worktree and branches, and mark the story done. Use when the user says "/merge-worktree", "/merge-worktree story-NNN", or "merge worktree".

Execute stories in parallel (where safe) using background agents, each working in an isolated git worktree branched from a shared dev branch. Handles dependency ordering, write-file conflict detection, and reports results. Use when the user says "/run-stories", "/run-stories story-NNN", "/run-stories epic-NNN", or any combination of story and epic IDs.

Bridge between presearch briefings (or inline args) and the /draft-plans skill. Parses inputs, dispatches the planner agent to create an epic and stories in the DB, and writes .ship-manifest.json for downstream consumption. Three invocation modes: briefing path, inline title+items, or resume an existing epic. Also handles execute mode for existing plan files (bypasses planner, creates DB entries directly). Use when the user says "/plan-stories presearch/topic.md", "/plan-stories \"Title\" 1. Feature 2. Feature", or "/plan-stories epic-NNN".

Universal entry point for all code changes — from 1-file fixes to multi-story epics. Auto-classifies scope and routes internally (quickfix for <=5 files, full pipeline otherwise). Never skip /ship — it handles everything.

Generate a UI component library via Gemini. Creates reusable components with clean interfaces that ui-coder agents import instead of generating per-story. Use /gen-library before /ship for projects with UI work.

Unified dual-engine audit: runs Gemini large-context analysis followed by Claude critique, synthesizing both into a scored report with per-finding acceptance criteria. Use when the user says "/audit", "audit the codebase", "audit story-NNN", or "audit <path>". Replaces both old /audit and /gemini-audit. Supports --claude-only and --gemini-only for single-engine backward compat. Supports scoping to files, directories, story diffs, or time ranges. Section filters, scoring, and all existing flags preserved.

Spec-gated merge: validates branch strategy, runs build/test/lint gates, walks acceptance criteria from the spec file, launches a reviewer on the diff, and only merges when all gates pass. Prevents regression with post-merge test runs. Enforces feature → dev → main flow. Use when the user says "/merge", "/merge <branch>", "/merge --to-main", or "/merge --dry-run".

Project introspection for implementation planning. Reads the codebase, queries recorded decisions and OpenMemory, identifies existing patterns, constraints, and testable assertions. NO web research — that's /research's job. Scout answers "what does THIS project require?" not "what exists in the world?" Reads .clarify-<slug>.json and/or .research-<slug>.json if provided. Writes presearch/.scout-<slug>.json with findings, constraints, patterns, and testable assertions. Bootstrap mode (--bootstrap <path>) scans an unfamiliar repo and generates CLAUDE.md, decisions.sql, and .claude/refs/ convention artifacts. Use when the user says "/scout <topic>", "/scout --clarify presearch/.clarify-foo.json", "/scout --research presearch/.research-foo.json", "/scout --deep <topic>", or "/scout --bootstrap /path/to/repo".

Interactive spec builder: takes a product name + natural language description and produces a full feature spec document (markdown) with machine-readable FeatureSpec JSON. Covers objective, user stories, requirements, acceptance criteria, constraints, integration points, out of scope, AI boundaries, and the JSON extract for /factory. Use when the user says "/spec <product> <description>", "/spec --edit path/to/spec.md", or "/spec --validate path/to/spec.md".

Open the charts dashboard and today's key-prompts file for the current project. Use when the user says "open charts", "view tracking", "show dashboard", or "/view-tracking".

Comprehensive implementation planning for the Claude sub-agent. Use when a complex task requires multi-file changes, architectural analysis, or systematic execution. Triggers when the user asks for a plan, strategy, or implementation roadmap.