capstone-toolkit

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".