enterprise

Explore unfamiliar code with Spock's guidance. User-led exploration of a codebase target with reconnaissance suggestions, dependency analysis, and iterative Q&A.

Plan an implementation before executing. Spock performs codebase reconnaissance, gathers requirements, and produces a structured plan with tasks, dependencies, and file boundaries that engage can execute.

Generate documentation for a codebase target. Spock confirms the parameters, then dispatches the Ship's Computer to analyze code and produce READMEs or API references.

Execute an implementation plan. Spock coordinates Builder (Scotty) and Validator (McCoy) in a 2-station pipeline -- implement, review, fix, repeat. Requires a plan file from /enterprise:chart.

Generate stakeholder-facing reports from the Captain's Log. Compile standup updates, sprint reviews, or PR descriptions from recorded events.

View the Captain's Log -- session activity, token telemetry, and event history. Spock reads the JSONL log, filters by event type, and renders a human-friendly timeline with session totals.

Pull requirements from Jira or GitHub and convert them into a mission briefing that feeds into /enterprise:chart. Starfleet Command integration.

Analyze code for refactoring opportunities. Scotty's engineering station examines complexity, duplication, and coupling, then presents a prioritized improvement plan.

Run a code review on a codebase target. Spock routes to Dr. McCoy's medical station, where the Ship's Computer performs diagnostics and presents findings.

Three specialized agents form the build-validate pipeline. The Ship's Computer analyzes, the Builder implements, and the Validator reviews.

Scotty -- the Builder. Implements code changes per task instructions. Follows file boundaries, uses knowledge skills for context, and reports changes made. PostToolUse hooks run biome and tsc after writes.

Ship's Computer processing core. Analyzes codebase targets and generates reports. Receives operational protocols via computer-operations skill (preloaded) and task-specific instructions via dynamic skill injection in the prompt. Uses neutral, factual voice from Star Trek TOS.

Dr. McCoy -- the Validator. Reviews code changes for correctness, edge cases, and convention violations that linters miss. Read-only -- cannot modify files. Outputs PASS or FAIL with detailed reasoning.

Knowledge skill for API contracts and endpoint patterns. Injected into Builder and Validator agents during engage to enforce consistent API design, error handling, and request/response schemas. Not user-invocable.

Knowledge skill for project conventions and coding standards. Injected into Builder and Validator agents during engage to enforce consistent style, naming, and structure. Not user-invocable.

Knowledge skill for SideQuest core utilities. Injected into Builder and Validator agents during engage to provide context about available utilities, patterns, and anti-patterns. Not user-invocable.

Knowledge skill for testing patterns and best practices. Injected into Builder and Validator agents during engage to enforce test quality, mock hygiene, and resource cleanup. Not user-invocable.

Ship's Computer operational protocols. Voice rules, budget enforcement, telemetry contract, report format, and operational constraints. Preloaded into every Computer CPU via skills frontmatter.

API reference generation program. Injected dynamically into Computer CPUs by the dispatching station. Defines analysis approach, export extraction, and output template for API reference documentation.

Code review program. Injected dynamically into Computer CPUs by the medical station. Defines analysis approach, priority read order, check categories, and output template for code review reports.

README generation program. Injected dynamically into Computer CPUs by the dispatching station. Defines analysis approach, priority read order, and output template for README documentation following community best practices.

Refactoring analysis program. Injected into Ship's Computer CPUs by the engineering station for code improvement recommendations. Analyzes complexity, duplication, and coupling to produce a prioritized refactoring plan.

Security scanning program (stub). Will be injected into Computer CPUs by the medical station for vulnerability assessment.

Mr. Scott's engineering station. Refactoring analysis and code improvement. Scotty takes over the conversation -- his own voice, confirmation, reconnaissance, dispatch, and presentation.

Dr. McCoy's medical station. Code review and diagnostics. McCoy takes over the conversation -- his own voice, confirmation, reconnaissance, dispatch, and presentation.

Spock from Star Trek, speaking fully in character. Addresses the user as "Captain", never uses contractions, speaks with Vulcan precision and logic. Handles documentation, planning, and code analysis assignments. Greets the Captain in Spock's voice before doing anything else. Not for codebase exploration, code review routing, or implementation.

1 hook across 1 event