accelerator

Plugin accelerator from marketplace atomic-innovation in atomicinnovation/accelerator. Commands read from the repo's manifest — today.

Skills (69)

• browser-executor

  Resolves the absolute path of the Playwright executor (run.sh)

• configure

  View, create, or edit Accelerator plugin configuration. Manage document templates.

• init

  Prepare a repository with the directories and gitignore entries

• migrate

  Apply pending Accelerator meta-directory migrations to bring a repo into line with the latest plugin schema. Destructive by default but guarded — refuses to run on a dirty working tree and prints a one-line preview per pending migration before applying.

• my-lens-lens
• paths

  Resolves all configured document-discovery paths for the current

• create-adr

  Interactively create an architecture decision record (ADR). Use

• extract-adrs

  Extract architecture decision records from existing meta documents

• review-adr

  Review an architecture decision record for quality and

• analyse-design-gaps

  Compare two design inventories produced by inventory-design and emit

• inventory-design

  Generate a structured design inventory for a frontend source —

• describe-pr

  Generate a comprehensive pull request description following the

• respond-to-pr

  Respond to pull request review feedback interactively, working

• review-pr

  Review a pull request through multiple quality lenses and present a

• attach-jira-issue

  Use this skill only when the user explicitly invokes /attach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Shows a preview of what will be uploaded and req

• comment-jira-issue

  Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new comment), list (fetch all co

• create-jira-issue

  Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional field

• init-jira

  Set up the Jira Cloud integration for this project. Verifies credentials against a real Jira Cloud tenant, discovers the tenant's custom-field catalogue and project list, and persists the results under `<paths.integrations>/jira/` (default `.accelerator/state/integrations/jira/`) as team-shared, ver

• search-jira-issues

  Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe J

• show-jira-issue

  Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks an

• transition-jira-issue

  Use this skill only when the user explicitly invokes /transition-jira-issue to move a Jira issue through its workflow by state name. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and target state name (case-inse

• update-jira-issue

  Use this skill only when the user explicitly invokes /update-jira-issue to modify an existing Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and at least one mutating flag (summary, body, priority, as

• attach-linear-issue

  Use this skill only when the user explicitly invokes /attach-linear-issue to attach a link or a binary file to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Link mode registers an external URL; binary mode

• comment-linear-issue

  Use this skill only when the user explicitly invokes /comment-linear-issue to add a Markdown comment to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows the comment preview, requires explicit confirma

• create-linear-issue

  Use this skill only when the user explicitly invokes /create-linear-issue to create a new Linear issue from a local work-item file. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It reads the work item's title and Markdown body, show

• init-linear

  Set up the Linear integration for this project. Verifies a Linear personal API key against the real Linear GraphQL API, lets you pick one team, and persists that team plus its WorkflowState catalogue under `<paths.integrations>/linear/` (default `.accelerator/state/integrations/linear/`). `catalogue

• search-linear-issues

  Use this skill whenever the user wants to search, list, or filter Linear issues — by state, assignee, label, or free text — even if they say 'find', 'show me', 'what's open', 'list my issues', or similar phrasing rather than 'search Linear'. Composes a Linear IssueFilter from structured flags, execu

• show-linear-issue

  Use this skill when the user asks about a specific Linear issue by identifier (e.g. BLA-123, ENG-456) — for viewing the description, state, assignee, or comments. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' an identifier, or asks any dir

• transition-linear-issue

  Use this skill only when the user explicitly invokes /transition-linear-issue to move an existing Linear issue to a different workflow state. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. The target state name is resolved to its UUI

• update-linear-issue

  Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows a payload

• create-note

  Interactively capture a short-form note. Use when jotting down

• create-plan

  Create detailed implementation plans through interactive, iterative

• implement-plan

  Execute an approved implementation plan from the configured plans

• review-plan

  Review an implementation plan through multiple quality lenses and

• stress-test-plan

  Interactively stress-test an implementation plan by grilling the user

• validate-plan

  Validate that an implementation plan was correctly executed by

• research-codebase

  Conduct comprehensive codebase research by spawning parallel

• research-issue

  Investigate production issues and bugs through hypothesis-driven

• architecture-lens

  Architecture review lens for evaluating structural integrity,

• clarity

  Work-item review lens for evaluating unambiguous communication —

• code-quality-lens

  Code quality review lens for evaluating design principles, error

• compatibility-lens

  Compatibility review lens for evaluating API contract stability,

• completeness

  Work-item review lens for evaluating structural and informational

• correctness-lens

  Correctness review lens for evaluating logical validity, boundary

• database-lens

  Database review lens for evaluating migration safety, schema

• dependency

  Work-item review lens for evaluating explicit capture of blockers,

• documentation-lens

  Documentation review lens for evaluating documentation

• performance-lens

  Performance review lens for evaluating algorithmic efficiency,

• portability-lens

  Portability review lens for evaluating environment independence,

• safety-lens

  Safety review lens for evaluating data loss prevention,

• scope

  Work-item review lens for evaluating sizing, decomposition, and

• security-lens

  Security review lens for evaluating threats, vulnerabilities, and

• standards-lens

  Standards compliance review lens for evaluating project conventions,

• test-coverage-lens

  Test coverage review lens for evaluating testing strategy adequacy,

• testability

  Work-item review lens for evaluating whether Acceptance Criteria and

• usability-lens

  Usability review lens for evaluating developer experience, API

• plan-review-output-format

  Output format specification for plan review agents. Defines the

• pr-review-output-format

  Output format specification for PR review agents. Defines the JSON

• work-item-review-output-format

  Output format specification for work-item review agents. Defines the

• commit

  Create VCS commits for session changes. Use when the user wants to

• visualise

  Open the accelerator meta visualiser. Launches the companion-window server in the background and returns a URL. Subcommands stop and status manage the running server.

• create-work-item

  Interactively create a well-formed work item. Use when capturing a

• extract-work-items

  Extract work items in batch from existing documents (specs, PRDs,

• list-work-items

  List and filter work items from the configured work directory.

• refine-work-item

  Interactively refine a work item by decomposing it into children,

• review-work-item

  Review a work item through multiple quality lenses and

• stress-test-work-item

  Interactively stress-test a work item by grilling the user

• sync-work-items

  Reconcile local work items in meta/work/ with the active remote

• update-work-item

  Update fields (status, priority, tags, parent, etc.) of an

Subagents (9)

• browser-analyser

  Analyses a focused set of screens in a running web application via

• browser-locator

  Locates routes, screens, and DOM-level component presence in a

• codebase-analyser

  Analyses codebase implementation details. Call the codebase-analyser agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)

• codebase-locator

  Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.

• codebase-pattern-finder

  codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the locatio

• documents-analyser

  The research equivalent of documents-analyser. Use this subagent_type when wanting to deep dive on a research topic. Not commonly needed otherwise.

• documents-locator

  Discovers relevant documents in meta/ directory (We use this

• reviewer

  Generic review agent that evaluates code or plans through a

• web-search-researcher

  Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagent_type today to find any and all answers to your questions! It will research deeply to figure

Hooks (4)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/vcs-detect.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/config-detect.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/migrate-discoverability.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/vcs-guard.sh