Spec-driven development toolkit: structured specs, spec-gated merges, decision memory, and code audits. Keeps capstone projects aligned and regression-free.
npx claudepluginhub kelsi-andrewss/capstone-toolkit --plugin capstoneUnified 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".
Lightweight spec-driven development plugin for Claude Code. Keeps capstone projects aligned with structured specs, prevents regressions with gated merges, and maintains shared decisions across the team.
| Skill | Description |
|---|---|
/spec | Interactive spec builder: natural language description to full feature spec with acceptance criteria and machine-readable FeatureSpec JSON |
/merge | Spec-gated merge: validates branch strategy (feature → dev → main), runs build/test/lint gates, walks acceptance criteria from the spec, reviews the diff, and catches regressions with post-merge tests |
/scout --bootstrap | One-time repo onboarding: scans an unfamiliar codebase and generates CLAUDE.md (conventions) + decisions.sql (architectural decisions) so every teammate's Claude understands the project the same way |
/audit | Code audit with scored report and per-finding acceptance criteria. Use --claude-only for zero external dependencies, or dual-engine mode (Gemini + Claude) for deeper analysis |
Persists project decisions ("we use tRPC, not REST — because X") to SQLite with a portable SQL dump (decisions.sql) committed to git. Prevents the same architectural debate from happening four times.
Tools exposed:
record_project_decision -- record a decision with file scope patternsquery_project_decisions -- search by text query and/or file patternsget_decision -- look up a single decision by IDquery_decisions_by_domain -- filter active decisions by domainsync_decision_store -- force rebuild from SQL dumpclaude --plugin-dir ./capstone-toolkit
/plugin install kelsi-andrewss/capstone-toolkit
pip install mcp) -- required for the decisions MCP serverpip install fastembed) -- optional, enables semantic search in decision memory. Without it, keyword search (FTS5) still works./scout --bootstrap /path/to/repo (one-time: onboard the codebase)
|
v
/spec <product> <description> (write the contract)
|
v
implement on feature branch
|
v
/merge (feature → dev, spec-gated)
|
v
/merge --to-main (dev → main, promotion gate)
Use /audit at any point to review code quality.
The merge skill enforces:
feature/xyz ──→ dev ──→ main
│ │ │
/merge /merge never
(spec-gated) --to-main direct
dev with full gates: build, test, lint, spec acceptance criteria, diff reviewdev merges to main as a promotion gate (build + test + regression check)main are blocked — all work flows through devDecisions are stored in two forms:
decisions.sql -- SQL dump committed to git. Text-based, diffable, mergeable. Source of truth.decisions.db -- Local SQLite rebuilt from the dump on demand. Gitignored.After git pull, the local DB auto-rebuilds if the dump changed. No manual sync needed.
MIT
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Share bugs, ideas, or general feedback.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Use this agent when you need expert assistance with React Native development tasks including code analysis, component creation, debugging, performance optimization, or architectural decisions. Examples: <example>Context: User is working on a React Native app and needs help with a navigation issue. user: 'My stack navigator isn't working properly when I try to navigate between screens' assistant: 'Let me use the react-native-dev agent to analyze your navigation setup and provide a solution' <commentary>Since this is a React Native specific issue, use the react-native-dev agent to provide expert guidance on navigation problems.</commentary></example> <example>Context: User wants to create a new component that follows the existing app structure. user: 'I need to create a custom button component that matches our app's design system' assistant: 'I'll use the react-native-dev agent to create a button component that aligns with your existing codebase structure and design patterns' <commentary>The user needs React Native component development that should follow existing patterns, so use the react-native-dev agent.</commentary></example>