atl

Plugin atl from marketplace atl in isukharev/atl. Commands read from the repo's manifest — 1 month ago.

Skills (18)

• atl-develop

  Implement or review changes in the ATL repository with the correct architecture owner, generated-tree boundary, risk-classified verification, and privacy checks. Use for ATL code, documentation, tests, build tooling, refactors, or bug fixes. Do not use merely to operate the installed ATL CLI against

• atl-land-change

  Carry an ATL repository change from a shaped issue through linked branch, draft PR, integrated review, hosted CI, authorized merge, main synchronization, and cleanup. Use when opening, reviewing, checking, merging, or recovering an ATL PR. Do not use for local exploration that is not entering the is

• atl-live-validate

  Validate ATL behavior against configured Jira, Confluence, GitHub, or GitLab backends while preserving privacy, request bounds, write authority, owned-fixture scope, and ambiguous-outcome safety. Use for live integration, smoke, compatibility, VPN/connectivity, or fixture checks. Do not use for synt

• atl-private-benchmark-bootstrap

  Bootstrap a private ATL Jira or Confluence benchmark dataset for a new maintainer from a fresh clone with owner-only storage, explicit provider/backend authority, offline validation, and primary/holdout design. Use for private benchmark onboarding or private case authoring. Do not use for public syn

• atl-resume-work

  Reconstruct and resume ATL repository work after context compaction, interruption, handoff, a fresh session, or uncertain branch state. Use when remembered progress, authority, tests, issues, PRs, worktrees, or dirty-file ownership may be stale. Do not use for routine implementation when current sta

• report-helper

  Prepare an earlier synthetic report from local fixtures.

• report-helper

  Prepare a synthetic report from local fixtures.

• atl

  Coordinate atl local mirrors across Jira and Confluence. USE WHEN orienting to atl, maintaining or recovering an existing mirror, or combining both services. DO NOT USE WHEN setup/onboarding, one service, a focused workflow, or codebase-only work is primary.

• confluence

  Read or change Confluence pages, comments, tables, attachments, trees, and native CSF with atl. USE WHEN the outcome is a direct Confluence operation. DO NOT USE WHEN cross-service search, Jira, meeting-task, spec-to-backlog, setup/onboarding, or codebase work is primary.

• jira

  Read or change Jira issues, fields, history, boards, sprints, Structure, and exports with atl. USE WHEN the outcome is a direct Jira operation. DO NOT USE WHEN cross-service search, reporting, dashboards, triage, meeting/spec workflows, Confluence, setup/onboarding, or codebase work is primary.

• meeting-tasks

  Turn meeting notes into reviewed Jira task proposals with atl. USE WHEN capturing meeting or retro action items as assigned issues. DO NOT USE WHEN the source is a specification, only a prose summary is wanted, or the task is an ordinary Jira operation.

• onboarding

  Build a reviewed private atl workflow profile from approved Jira/Confluence samples. USE WHEN the user explicitly asks to onboard, personalize atl, or refresh saved preferences. DO NOT USE WHEN handling ordinary service, search, report, or setup work; explicit-only.

• search-knowledge

  Answer from qualified Jira and Confluence evidence with atl. USE WHEN organizational knowledge is unknown or split across both services. DO NOT USE WHEN one exact resource is known, the task is a report/dashboard, or the answer belongs in the codebase.

• setup

  Install and configure atl authentication, backends, and mirror defaults. USE WHEN the user explicitly requests install, authentication, setup repair, or {{atl.setup_cmd}}. DO NOT USE WHEN handling normal Jira, Confluence, search, reporting, or mirror work; explicit-only.

• spec-to-backlog

  Convert a specification into a reviewed Jira epic and backlog with atl. USE WHEN decomposing requirements, RFCs, or designs into linked Jira work. DO NOT USE WHEN the source is meeting notes, only a summary is wanted, or the task is a direct service operation.

• sprint-dashboard

  Build a visual read-only Jira sprint or board dashboard with atl. USE WHEN the user wants a standup view, WIP picture, or sprint snapshot. DO NOT USE WHEN the output is a narrative report, raw Jira list, or codebase dashboard.

• status-report

  Draft an audience-oriented Jira status report with atl. USE WHEN the user wants a weekly/daily progress narrative, blocker summary, or period report. DO NOT USE WHEN the output is a visual dashboard, direct Jira query, knowledge search, or codebase summary.

• triage-issue

  Triage a bug against Jira with atl before proposing a ticket. USE WHEN an error or stack trace comes with duplicate, prior-fix, or file-a-bug intent. DO NOT USE WHEN debugging code only, inspecting a known issue, or creating an ordinary task.

MCP servers (1)

• atl

  runs: atl mcp serve --plugin-interface-contract=1 --plugin-product-version=0.9.0

Similar plugins