All skills

Generated from each skill’s SKILL.md at build time.

config

configure — View, create, or edit Accelerator plugin configuration.
init — Prepare a repository with the directories and gitignore entries that Accelerator skills expect.
migrate — Apply pending Accelerator meta-directory migrations to bring a repo into line with the latest plugin schema.

decisions

create-adr — Interactively create an architecture decision record (ADR).
extract-adrs — Extract architecture decision records from existing meta documents (research, plans).
review-adr — Review an architecture decision record for quality and completeness, then accept, reject, or suggest revisions.

design

analyse-design-gaps — Compare two design inventories produced by inventory-design and emit a structured gap artefact whose prose paragraphs satisfy the extract-work-items cue-phrase contract.
inventory-design — Generate a structured design inventory for a frontend source — tokens, components, screens, and features — by crawling it with code analysis, live Playwright inspection, or both.

github

describe-pr — Generate a comprehensive pull request description following the repository’s standard template.
respond-to-pr — Respond to pull request review feedback interactively, working through each item with verification and code changes.
review-pr — Review a pull request through multiple quality lenses and present a compiled analysis with inline comments.

integrations/jira

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.
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.
create-jira-issue — Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue.
init-jira — Set up the Jira Cloud integration for this project.
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’.
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.
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.
update-jira-issue — Use this skill only when the user explicitly invokes /update-jira-issue to modify an existing Jira issue.

integrations/linear

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.
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.
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.
init-linear — Set up the Linear integration for this project.
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’.
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.
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.
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).

notes

create-note — Interactively capture a short-form note.

planning

create-plan — Create detailed implementation plans through interactive, iterative collaboration.
implement-plan — Execute an approved implementation plan from the configured plans directory.
review-plan — Review an implementation plan through multiple quality lenses and collaboratively iterate based on findings.
stress-test-plan — Interactively stress-test an implementation plan by grilling the user on decisions, edge cases, and assumptions to find issues, inconsistencies, and gaps before implementation begins.
validate-plan — Validate that an implementation plan was correctly executed by verifying success criteria and identifying deviations.

research

conduct-spike — Interactively conduct a time-boxed spike — collaboratively reduce uncertainty through discussion mixed with agent-driven research (and small throwaway prototypes where a question is empirical), then record the outcome on the spike’s work item.
research-codebase — Conduct comprehensive codebase research by spawning parallel subagents and synthesising findings into a research document.
research-issue — Investigate production issues and bugs through hypothesis-driven debugging.

vcs

commit — Create VCS commits for session changes.

visualisation

visualise — Open the accelerator meta visualiser.

work

create-work-item — Interactively create a well-formed work item.
extract-work-items — Extract work items in batch from existing documents (specs, PRDs, research, plans, meeting notes, design docs).
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, enriching it with codebase context, sharpening its acceptance criteria, sizing it, or linking it to dependencies.
review-work-item — Review a work item through multiple quality lenses and collaboratively iterate based on findings.
stress-test-work-item — Interactively stress-test a work item by grilling the user on scope, assumptions, acceptance criteria, edge cases, and dependencies to surface issues, gaps, and flawed assumptions before implementation is planned.
sync-work-items — Reconcile local work items in meta/work/ with the active remote tracker named by work.integration.
update-work-item — Update fields (status, priority, tags, parent, etc.) of an existing work item.

Internal

architecture-lens — Architecture review lens for evaluating structural integrity, coupling, cohesion, and evolutionary fitness.
browser-executor — Resolves the absolute path of the Playwright executor (run.sh) for browser agents.
clarity — Work-item review lens for evaluating unambiguous communication — referent clarity, internal consistency, jargon handling, and actor/outcome identification.
code-quality-lens — Code quality review lens for evaluating design principles, error handling, complexity, testability, and maintainability.
compatibility-lens — Compatibility review lens for evaluating API contract stability, cross-platform support, protocol compliance, and dependency management.
completeness — Work-item review lens for evaluating structural and informational completeness — section presence, content density, kind-appropriate content, and frontmatter integrity.
correctness-lens — Correctness review lens for evaluating logical validity, boundary conditions, invariant preservation, concurrency correctness, and state management.
database-lens — Database review lens for evaluating migration safety, schema design, query correctness, and data integrity.
dependency — Work-item review lens for evaluating explicit capture of blockers, consumers, external systems, and ordering.
documentation-lens — Documentation review lens for evaluating documentation completeness, accuracy, and audience-appropriateness.
paths — Resolves all configured document-discovery paths for the current project.
performance-lens — Performance review lens for evaluating algorithmic efficiency, resource usage, and concurrency efficiency.
plan-review-output-format — Output format specification for plan review agents.
portability-lens — Portability review lens for evaluating environment independence, deployment flexibility, and vendor lock-in avoidance.
pr-review-output-format — Output format specification for PR review agents.
safety-lens — Safety review lens for evaluating data loss prevention, operational safety, and protective mechanisms against accidental harm.
scope — Work-item review lens for evaluating sizing, decomposition, and orthogonality of requirements.
security-lens — Security review lens for evaluating threats, vulnerabilities, and missing protections.
standards-lens — Standards compliance review lens for evaluating project conventions, API standards, and accessibility.
test-coverage-lens — Test coverage review lens for evaluating testing strategy adequacy, test quality, and test architecture.
testability — Work-item review lens for evaluating whether Acceptance Criteria and requirements admit a concrete verification strategy — each criterion must be specific, measurable, and verifiable.
usability-lens — Usability review lens for evaluating developer experience, API ergonomics, configuration complexity, and onboarding.
work-item-review-output-format — Output format specification for work-item review agents.