aimsise

audit

Comprehensive multi-agent code audit that delegates to the code-reviewer and security-scanner sub-agents. Always runs security-scanner; set only_security_scan=true to restrict to a security-only review. Use when (1) verifying changes before shipping, (2) running review feedback inside the /impl Generator-Evaluator loop, or (3) reviewing a topic branch with no active ticket directory. Triggers on "audit changes", "review the diff", "code review", "security review", "/audit". Chain-invoked by /impl Step 17 and /ship review-gate; disable-model-invocation: false is intentional because callers reference this skill by name.

autopilot

Consume a pre-built ticket list (split-plan.md under .simple-workflow/backlog/product_backlog/{parent-slug}/) and drive the per-ticket /scout -> /impl -> /ship pipeline in topological order with policy-based autonomous decision making at each gate. Use when: (1) the user explicitly invokes /autopilot with a parent-slug; (2) another skill chains to /autopilot via the Skill tool after /brief and /create-ticket have populated a split-plan; (3) a resumable autopilot-state.yaml exists and the user re-runs /autopilot to continue from the last checkpoint. Triggers on "autopilot", "run the autopilot", "/autopilot <slug>", "continue the autopilot run", "drive scout impl ship pipeline".

brief

Conducts a structured Socratic interview that gathers requirements, then writes a brief and an autopilot policy file for a new feature or task. Use when (1) a user starts /brief with a feature description, (2) requirements are unclear and need iterative Q&A, or (3) downstream skills (/create-ticket, /autopilot) need a structured brief artifact. Triggers on "/brief", "draft a brief", "start a new feature brief", "feature scoping interview".

create-ticket

Do not auto-invoke. Only invoke when called by name. Use when (1) user types `/create-ticket`, (2) user provides description / `brief=<path>` / `findings=<path>` asking for a structured backlog ticket, or (3) sibling skill delegates ticket creation (single or N>=1 via decomposer). Triggers on "create a ticket", "/create-ticket", "draft a ticket".

impl

Do not auto-invoke. Only invoke when called by name. Implements the latest plan via Generator -> AC Evaluator -> Code Quality Reviewer loop. Use when (1) /scout or /plan2doc produced a plan and user calls `/impl`, (2) /autopilot delegates the per-ticket impl step, or (3) an explicit plan path is passed. Triggers on "/impl", "implement the plan", "generator-evaluator loop".

investigate

Investigates codebase topics by spawning the researcher subagent and writing structured findings to disk. Use when (1) the user runs `/investigate <topic>` directly to research a question, (2) `/scout` delegates the research phase of a ticket workflow via the Skill tool, or (3) a ticket directory needs an `investigation.md` artifact at `.simple-workflow/backlog/active/{ticket-dir}/investigation.md`. Default output directory is `.simple-workflow/docs/research/` when no ticket is bound. Triggers on "/investigate", "research the code", "investigate <topic>", "find references", "explore the codebase".

plan2doc

Creates an implementation plan by spawning the planner subagent with a size-routed model (sonnet for Size S, opus for M/L/XL) and writing the plan to disk. Use when (1) the user runs `/plan2doc <feature>` directly to draft a plan for a ticket workflow, (2) `/scout` delegates the plan step of a ticket workflow via the Skill tool, or (3) the user requests a plan for a feature outside any ticket workflow (output lands in `.simple-workflow/docs/plans/{feature}.md`). When a paired `ticket.md` exists, the generated `plan.md` carries a verbatim copy of the ticket's `## Acceptance Criteria` (AC SSoT discipline). Triggers on "/plan2doc", "write a plan", "plan the feature", "create an implementation plan", "design the implementation".

Code & Development Listed

refactor

Plans and executes a refactoring with safety checks by delegating to the planner and code-reviewer agents, then iterating implementation + review up to three rounds. Use when (1) the user runs `/refactor {target}` directly to refactor a specific function, file, or pattern, (2) refactoring is invoked inside a ticket workflow with `ticket-dir={dir-name}` so the review artifact lands at `{ticket-dir}/quality-refactor-{n}.md`, or (3) the user wants the refactor protected by a `backup/pre-refactor-{timestamp}` branch and a bounded review loop. Use only when the user explicitly asks to refactor code. Triggers on "/refactor", "refactor code", "restructure", "extract method", "rename", "clean up".

scout

Investigates the codebase and produces an implementation plan by delegating to `/investigate` (researcher subagent) and `/plan2doc` (planner subagent), then emits a `## [SW-CHECKPOINT]` block at end-of-skill. Use when (1) the user runs `/scout` directly on a topic to research and plan it outside any ticket workflow, (2) the user runs `/scout` on an active or product-backlog ticket so the resulting `investigation.md` and `plan.md` land in `.simple-workflow/backlog/active/{ticket-dir}/` and the ticket's `phase-state.yaml` advances `phases.scout` from `pending` to `completed`, or (3) `/autopilot` chain-calls the scout phase of a ticket-driven pipeline via the Skill tool. Triggers on "/scout", "/scout <topic>", "scout the codebase", "investigate and plan", "research and plan", "kick off a ticket", "scout this feature".

Code & Development Listed

ship

Ships completed work by committing staged changes, moving any bound ticket to `.simple-workflow/backlog/done/`, delegating knowledge-base extraction to `/tune` via the Skill tool, pushing the branch, creating a GitHub PR, and optionally squash-merging it. Use when (1) the user runs `/ship` directly to commit-and-PR the current branch outside any ticket workflow, (2) the user runs `/ship` on an active ticket so the ticket directory moves from `.simple-workflow/backlog/active/` to `.simple-workflow/backlog/done/`, the ticket's `phase-state.yaml` advances `phases.ship` from `pending` to `completed`, and the PR body carries the canonical `Audit Summary:` line plus every `### Warning:` heading from the latest `audit-round-N.md`, or (3) `/autopilot` chain-calls the ship phase of a ticket-driven pipeline via the Skill tool. Triggers on "/ship", "/ship merge=true", "/ship [target-branch]", "ship the changes", "commit and PR", "create pull request", "squash merge", "complete ticket".

tune

Analyzes evaluation logs (eval-round, quality-round, security-scan, audit-round, autopilot-log) by spawning the tune-analyzer subagent and maintains the project knowledge base under `.simple-workflow/kb/` (entries.yaml, index.yaml, candidates.yaml) with confidence-based three-tier promotion (Tier 1 >= 0.8 auto-promote, Tier 2 0.5-0.8 propose, Tier 3 < 0.5 accumulate). Use when (1) the user runs `/tune TICKET-DIR` to mine one ticket's logs, (2) the user runs `/tune all` to mine every ticket under `.simple-workflow/backlog/done/` and `active/`, or (3) `/ship` Phase 1 step 6 chain-calls `/tune` via the Skill tool after moving a ticket to `done/` so the next `/impl` Generator receives updated `index.yaml` pattern hints. Caps candidates at 30 with a 90-day TTL and entries at 50. Triggers on "/tune", "tune the knowledge base", "extract patterns", "analyze evaluation logs", "update the kb", "promote candidates", "knowledge base extraction", "mine evaluation logs".

catchup

Recovers branch state and recommends the next development action after a context reset. Activates when (1) starting a fresh session on an existing branch with unknown progress, (2) resuming after `/compact` or `/clear` drops in-flight state, or (3) the operator is unsure which phase (investigate / plan / implement / test / review / commit) to run next. Reads `phase-state.yaml`, compact-state snapshots, session logs, and artifact directories to detect the current phase and print an exact command sequence. Triggers on "catchup", "what's next", "resume work", "recover context", "next recommended action", "phase detection".