
Deep codebase initialisation with hierarchical AGENTS.md documentation and updating of AGENTS.md documentation.
Socratic deep interview with mathematical ambiguity gating before autonomous execution. Use when the user has a vague idea and wants thorough requirements gathering, says "interview me" or "don't assume", or the task is too complex to jump straight to code. Do NOT use when the user has a specific request with file paths and acceptance criteria, already has a plan file, or says "just do it".
Prepares a Linear issue for another agent: interviews only when needed, updates the description with behavior-first context, and stops—never implements the ticket itself. Use when refining handoff for CODE-* issues, syncing product intent to Linear, or when the user says "interview me about this ticket" / "update Linear for an implementer".
Initialise comprehensive hierarchical AGENTS.md documentation across the entire codebase.
Show staged and committed changes compared to origin/main.
Show staged changes compared to origin/main.
Create a comprehensive AI context handoff document for long-running sessions.
Generate a holistic product vision from Linear tickets. Pulls backlog, to-do, and in-progress tickets and synthesises them into a status-agnostic overview. Use when starting a new feature to understand the bigger picture, onboarding to the project, or when AI needs context on long-term goals. Supports refreshing existing masterplans with latest data.
Audit a repository's Cursor configuration or evaluate whether a specific artefact (rule, skill, command, subagent) is correctly placed. Use when optimising the repo for Cursor, improving indexing, adding or assessing rules/skills, or deciding where information should live.
# Code Review Instructions ## Introduction You are a senior software engineer. ## Exploring the changes Run `git --no-pager diff origin/main...HEAD` to identify the differences between this branch and the main branch. Perform any other necessary git diffs to explore the changes made in this branch. ## Rules: - You absolutely must not edit any of the code. - Investigate any potential issue you find, to validate whether it actually is an issue. ## Code Review Checklist (internal) Work thro
Iterative planning consensus loop. Orchestrates Planner, Architect, and Critic agents in rounds until the plan is approved or max iterations reached. Use for complex tasks that need a validated plan before implementation.
Show all changes compared to origin/main.