atomicinnovation

@atomicinnovation source repo

68 skills
0 followers
9 hours ago last updated

▌
Commit · atomicinnovation
Create VCS commits for session changes. Use when the user wants to commit their work with well-structured, atomic commits.

0
installs
▌
Init · atomicinnovation
Prepare a repository with the directories and gitignore entries that Accelerator skills expect. Safe to run repeatedly.

0
installs
▌
Paths · atomicinnovation
Resolves all configured document-discovery paths for the current project. Preloaded by agent definitions that need config-driven directory locations; not intended for direct user invocation.

0
installs
▌
Migrate · atomicinnovation
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.

0
installs
▌
Configure · atomicinnovation
View, create, or edit Accelerator plugin configuration. Manage document templates.

0
installs
▌
Review Pr · atomicinnovation
Review a pull request through multiple quality lenses and present a compiled analysis with inline comments. Use when the user wants a thorough PR review.

0
installs
▌
Create Note · atomicinnovation
Interactively capture a short-form note. Use when jotting down an observation, insight, or strategy snippet as a short-form note in meta/notes/ — e.g. "make a note of this", "jot this down", "capture a note".

0
installs
▌
Describe Pr · atomicinnovation
Generate a comprehensive pull request description following the repository's standard template. Use when the user wants to create or update a PR description.

0
installs
▌
Create Adr · atomicinnovation
Interactively create an architecture decision record (ADR). Use when the user wants to document an architectural decision, technology choice, or significant design decision. Guides through context gathering, options analysis, and consequence documentation.

0
installs
▌
Review Adr · atomicinnovation
Review an architecture decision record for quality and completeness, then accept, reject, or suggest revisions. Enforces ADR immutability — only proposed ADRs can be modified, accepted ADRs can only transition to superseded or deprecated. Use when a proposed ADR is ready for review, or when an accepted ADR needs to be deprecated.

0
installs
▌
Respond To Pr · atomicinnovation
Respond to pull request review feedback interactively, working through each item with verification and code changes. Use when the user wants to address PR review comments.

0
installs
▌
Create Plan · atomicinnovation
Create detailed implementation plans through interactive, iterative collaboration. Use when the user needs to plan a feature, refactoring, or task.

0
installs
▌
Review Plan · atomicinnovation
Review an implementation plan through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a plan before implementation.

0
installs
▌
List Work Items · atomicinnovation
List and filter work items from the configured work directory. Use when discovering what work items exist, filtering by status/kind/priority/parent/tag, or viewing the work item hierarchy.

0
installs
▌
Sync Work Items · atomicinnovation
Reconcile local work items in meta/work/ with the active remote tracker named by work.integration. Use when the user wants to sync, push, or pull work items to or from Jira or Linear, preview what a sync would change, or reconcile divergent local and remote state.

0
installs
▌
Create Work Item · atomicinnovation bundle
Interactively create a well-formed work item. Use when capturing a feature, bug, task, spike, or epic as a structured work item in meta/work/.

0
installs
▌
Refine Work Item · atomicinnovation bundle
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. Use after a work item has been drafted and before planning begins.

0
installs
▌
Review Work Item · atomicinnovation bundle
Review a work item through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a work item before implementation or escalation.

0
installs
▌
Update Work Item · atomicinnovation bundle
Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed.

0
installs
▌
Extract Adrs · atomicinnovation
Extract architecture decision records from existing meta documents (research, plans). Scans documents for implicit or explicit architectural decisions and converts selected ones into formal ADRs. Use when decisions are buried in research or planning documents and need to be captured formally.

0
installs
▌
Validate Plan · atomicinnovation
Validate that an implementation plan was correctly executed by verifying success criteria and identifying deviations. Use after implementing a plan to verify correctness.

0
installs
▌
Conduct Spike · atomicinnovation
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. Use when a work item or brief poses open questions that must be resolved before planning or implementation can proceed with confidence.

0
installs
▌
Inventory Design · atomicinnovation bundle
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. Use when you need to capture a snapshot of a current or target design surface before running analyse-design-gaps. Produces a dated artifact directory with an inventory.md and screenshots/. Re-running for the same source-id supersedes the prior snapshot without losing it.

0
installs
▌
Implement Plan · atomicinnovation
Execute an approved implementation plan from the configured plans directory. Use when the user wants to implement a plan phase by phase with verification.

0
installs
▌
Research Issue · atomicinnovation
Investigate production issues and bugs through hypothesis-driven debugging. Accepts stacktraces, logs, error messages, or vague behavioral descriptions and produces a root cause analysis.

0
installs
▌
Visualise · atomicinnovation
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.

0
installs
▌
Extract Work Items · atomicinnovation bundle
Extract work items in batch from existing documents (specs, PRDs, research, plans, meeting notes, design docs). Use whenever the user wants to capture, pull out, or convert requirements, work items, user stories, bug reports, or actionable tasks from existing files into structured work items in meta/work/ — even if they don't say "extract" explicitly.

0
installs
▌
Scope · atomicinnovation bundle
Work-item review lens for evaluating sizing, decomposition, and orthogonality of requirements. Used by review orchestrators — not invoked directly.

0
installs
▌
Stress Test Plan · atomicinnovation
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.

0
installs
▌
Safety Lens · atomicinnovation
Safety review lens for evaluating data loss prevention, operational safety, and protective mechanisms against accidental harm. Used by review orchestrators — not invoked directly.

0
installs
▌
Analyse Design Gaps · atomicinnovation bundle
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. Use after running inventory-design for both a current and target design surface. The resulting gap artefact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.

0
installs
▌
Research Codebase · atomicinnovation
Conduct comprehensive codebase research by spawning parallel subagents and synthesising findings into a research document. Use when the user needs to deeply understand a codebase area or answer technical questions.

0
installs
▌
Clarity · atomicinnovation bundle
Work-item review lens for evaluating unambiguous communication — referent clarity, internal consistency, jargon handling, and actor/outcome identification. Used by review orchestrators — not invoked directly.

0
installs
▌
Stress Test Work Item · atomicinnovation bundle
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.

0
installs
▌
Init Jira · atomicinnovation
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, version-controlled JSON caches. Idempotent: safe to re-run after credential or project changes.

0
installs
▌
Database Lens · atomicinnovation
Database review lens for evaluating migration safety, schema design, query correctness, and data integrity. Used by review orchestrators — not invoked directly.

0
installs
▌
Security Lens · atomicinnovation
Security review lens for evaluating threats, vulnerabilities, and missing protections. Used by review orchestrators — not invoked directly.

0
installs
▌
Standards Lens · atomicinnovation
Standards compliance review lens for evaluating project conventions, API standards, and accessibility. Used by review orchestrators — not invoked directly.

0
installs
▌
Usability Lens · atomicinnovation
Usability review lens for evaluating developer experience, API ergonomics, configuration complexity, and onboarding. Used by review orchestrators — not invoked directly.

0
installs
▌
Dependency · atomicinnovation bundle
Work-item review lens for evaluating explicit capture of blockers, consumers, external systems, and ordering. Used by review orchestrators — not invoked directly.

0
installs
▌
Correctness Lens · atomicinnovation
Correctness review lens for evaluating logical validity, boundary conditions, invariant preservation, concurrency correctness, and state management. Used by review orchestrators — not invoked directly.

0
installs
▌
Performance Lens · atomicinnovation
Performance review lens for evaluating algorithmic efficiency, resource usage, and concurrency efficiency. Used by review orchestrators — not invoked directly.

0
installs
▌
Portability Lens · atomicinnovation
Portability review lens for evaluating environment independence, deployment flexibility, and vendor lock-in avoidance. Used by review orchestrators — not invoked directly.

0
installs
▌
Testability · atomicinnovation bundle
Work-item review lens for evaluating whether Acceptance Criteria and requirements admit a concrete verification strategy — each criterion must be specific, measurable, and verifiable. Used by review orchestrators — not invoked directly.

0
installs
▌
Init Linear · atomicinnovation
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.json` is team-shared and version-controlled; `viewer.json` is per-developer and gitignored. Idempotent: safe to re-run after credential or team changes.

0
installs
▌
Architecture Lens · atomicinnovation
Architecture review lens for evaluating structural integrity, coupling, cohesion, and evolutionary fitness. Used by review orchestrators — not invoked directly.

0
installs
▌
Code Quality Lens · atomicinnovation
Code quality review lens for evaluating design principles, error handling, complexity, testability, and maintainability. Used by review orchestrators — not invoked directly.

0
installs
▌
Completeness · atomicinnovation bundle
Work-item review lens for evaluating structural and informational completeness — section presence, content density, kind-appropriate content, and frontmatter integrity. Used by review orchestrators — not invoked directly.

0
installs
▌
Compatibility Lens · atomicinnovation
Compatibility review lens for evaluating API contract stability, cross-platform support, protocol compliance, and dependency management. Used by review orchestrators — not invoked directly.

0
installs
▌
Documentation Lens · atomicinnovation
Documentation review lens for evaluating documentation completeness, accuracy, and audience-appropriateness. Used by review orchestrators — not invoked directly.

0
installs
▌
Test Coverage Lens · atomicinnovation
Test coverage review lens for evaluating testing strategy adequacy, test quality, and test architecture. Used by review orchestrators — not invoked directly.

0
installs
▌
Show Jira Issue · atomicinnovation bundle
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 any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

0
installs
▌
Attach Jira Issue · atomicinnovation
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. Previews what will be uploaded and requires explicit confirmation before POSTing.

0
installs
▌
Create Jira Issue · atomicinnovation bundle
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 fields (assignee, reporter, priority, labels, components, parent, custom fields). Previews the resolved intent, requires explicit confirmation, then POSTs to Jira and returns the new issue key.

0
installs
▌
Update Jira Issue · atomicinnovation bundle
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, assignee, reporter, parent, labels, components, custom fields). Previews the resolved intent with set-vs-update semantics, requires explicit confirmation, then PUTs to Jira.

0
installs
▌
Comment Jira Issue · atomicinnovation bundle
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 comments with pagination), edit (update an existing comment), delete (remove a comment — irreversible). Write subcommands preview the resolved intent and require explicit confirmation before calling the API.

0
installs
▌
Search Jira Issues · atomicinnovation bundle
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 JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.

0
installs
▌
Show Linear Issue · atomicinnovation
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 direct question about an issue they reference. Do NOT trigger when an identifier appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

0
installs
▌
Transition Jira Issue · atomicinnovation
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-insensitive). Previews the resolved transition and requires explicit confirmation before posting.

0
installs
▌
Attach Linear Issue · atomicinnovation
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 uploads a local file via Linear's pre-signed URL flow and registers the resulting asset. Shows a preview, requires explicit confirmation, then attaches.

0
installs
▌
Create Linear Issue · atomicinnovation
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, shows a payload preview, requires explicit confirmation, then creates the issue and writes the remote-allocated identifier (e.g. BLA-123) back into the file's external_id frontmatter field.

0
installs
▌
Update Linear Issue · atomicinnovation
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 preview, requires explicit confirmation, then applies the update.

0
installs
▌
Comment Linear Issue · atomicinnovation
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 confirmation, then posts the comment.

0
installs
▌
Search Linear Issues · atomicinnovation
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, executes a cursor-paginated search scoped to the configured team, and renders a summary table of the results. Prefer this skill over raw GraphQL whenever the user's intent maps to a structured flag.

0
installs
▌
Transition Linear Issue · atomicinnovation
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 UUID from the cached catalogue (no live lookup). Shows a preview, requires explicit confirmation, then applies the transition.

0
installs
▌
Pr Review Output Format · atomicinnovation
Output format specification for PR review agents. Defines the JSON schema, field reference, severity emoji prefixes, and comment body format for PR reviews.

0
installs
▌
Plan Review Output Format · atomicinnovation
Output format specification for plan review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for plan reviews.

0
installs
▌
Work Item Review Output Format · atomicinnovation
Output format specification for work-item review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for work-item reviews. Used by review orchestrators — not invoked directly.

0
installs

68 published skills