Fully standalone autonomous task execution with aimi-native agents. Direct tasks.json generation, guided brainstorming, multi-agent review, iterative execution with parallel story support via dependency graphs and worktree+team orchestration.
Plugin aimi-engineering from marketplace aimi-marketplace in aimi-so/aimi-engineering-plugin. Commands read from the repo's manifest — yesterday.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
agent-browseragent-native-architectureaimi-design-handoffandrew-kane-gem-writerarchitecture-foundationbrainstormcreate-agent-skillsdhh-rails-styledspy-rubyevery-style-editorfile-todosforgefrontend-designgit-worktreego-conventionsnestjs-conventionsnextjs-tanstack-conventionsrclonereact-best-practicesreact-native-skillsresolve-pr-parallelrust-conventionsstory-executortask-plannertypescript-node-conventions/aimi-engineering:brainstormExplore ideas through guided brainstorming with batched questions and codebase research
/aimi-engineering:deepenEnrich tasks.json stories with research insights
/aimi-engineering:design:auditTechnical quality audit for frontend interfaces — accessibility (a11y), performance, theming, responsive design, and anti-pattern detection. Dedicated home for WCAG/a11y checks. Use when you need a systematic, code-level quality report before release.
/aimi-engineering:design:craftBuild a feature with high-quality UX and UI through a structured process: shape the design, land the visual direction, build real production code, then inspect and improve in-browser until the result meets a high-end studio bar. Use when you have a confirmed design brief and are ready to implement,
/aimi-engineering:design:critiqueDesign critique for frontend interfaces — visual hierarchy, information architecture, anti-patterns, and Nielsen's heuristics scoring. Use when you want a design director's honest assessment of a UI.
/aimi-engineering:design:polishFinal-pass polish for frontend interfaces — catches the small details that separate good work from great work. Use after a feature is functionally complete and you want to align it to the design system, fix visual inconsistencies, and bring everything to a consistent quality level.
/aimi-engineering:design:shapeShape the UX and UI for a feature before any code is written. Produces a confirmed design brief. Use when starting a new UI surface, planning a feature's visual direction, or preparing context for /aimi:design:craft. Trigger phrases: design brief, shape this feature, ux planning, ui planning, design
/aimi-engineering:executeExecute all pending stories autonomously with wave-based parallelism
/aimi-engineering:initPrime the global CLI path cache so all /aimi:* commands resolve instantly without the Layer 2 glob
/aimi-engineering:nextExecute the next pending story from tasks.json
/aimi-engineering:open-prOpen a pull request with title and description derived from git commits and diff; --merge merges an existing pull request on that branch
/aimi-engineering:planGenerate tasks.json directly from a feature description
/aimi-engineering:references:business-spec-authoring/aimi-engineering:references:cli-path-resolution/aimi-engineering:references:container-execution/aimi-engineering:references:context-budget/aimi-engineering:references:dependency-setup/aimi-engineering:references:execute:console-error-attribution/aimi-engineering:references:execute:multi-repo-handling/aimi-engineering:references:execute:paired-split-branches-and-worktrees/aimi-engineering:references:execute:paired-split-dev-server-and-spawn/aimi-engineering:references:execute:paired-split-merge-and-continue/aimi-engineering:references:execute:phase-completion-creates-verification/aimi-engineering:references:execute:phase-completion-handoff-and-mark/aimi-engineering:references:execute:phase-completion-next-phase/aimi-engineering:references:execute:phase-completion-offer-pull-request/aimi-engineering:references:execute:phase-completion-pending-count/aimi-engineering:references:execute:phase-completion-visual-gate/aimi-engineering:references:execute:release-claim-on-abort/aimi-engineering:references:execute:resuming-and-error-recovery/aimi-engineering:references:execute:step-0-5-archival-check/aimi-engineering:references:execute:step-0-7-visual-follow-prompt/aimi-engineering:references:execute:step-0-9-aggregated-completion/aimi-engineering:references:execute:step-0-9-split-detection/aimi-engineering:references:execute:step-0-9-split-flow/aimi-engineering:references:execute:step-0-9-split-waves/aimi-engineering:references:execute:step-1-5-branch-freshness/aimi-engineering:references:execute:step-1-6-branch-base-selection/aimi-engineering:references:execute:step-1-7-claim-the-phase/aimi-engineering:references:execute:step-1-7-detect-split/aimi-engineering:references:execute:step-1-7-dev-server-and-notes/aimi-engineering:references:execute:step-1-7-per-group-containers/aimi-engineering:references:execute:step-1-7-phase-container/aimi-engineering:references:execute:step-1-execution-mode/aimi-engineering:references:execute:step-1-initialize-session/aimi-engineering:references:execute:step-2-flat-container/aimi-engineering:references:execute:step-2-main-repo-branch-setup/aimi-engineering:references:execute:step-2-per-project-branch-setup/aimi-engineering:references:execute:step-3-1-3-2-worktree-and-concurrency/aimi-engineering:references:execute:step-3-3-guidelines-and-dev-server/aimi-engineering:references:execute:step-3-3-open-visual-follow/aimi-engineering:references:execute:step-3-check-pending/aimi-engineering:references:execute:step-4-finalize/aimi-engineering:references:execute:step-4-post-loop-cleanup/aimi-engineering:references:execute:step-4-wave-execution-loop/aimi-engineering:references:execute:step-5-completion/aimi-engineering:references:execute:step-5-deadlock/aimi-engineering:references:execute:visual-follow-lifecycle/aimi-engineering:references:execution-mode/aimi-engineering:references:forge-contract/aimi-engineering:references:foundation-signals/aimi-engineering:references:interactivity/aimi-engineering:references:plan:error-handling/aimi-engineering:references:plan:phase-0-brainstorm-reuse/aimi-engineering:references:plan:phase-0-bundle-prototype-and-spec/aimi-engineering:references:plan:phase-0-design-bundle-detection/aimi-engineering:references:plan:phase-0-issue-confirmation/aimi-engineering:references:plan:phase-0-open-questions-gate/aimi-engineering:references:plan:phase-0-roadmap-materialization/aimi-engineering:references:plan:phase-0-roadmap-mode-detection/aimi-engineering:references:plan:phase-0-rolling-wave-absent-phase/aimi-engineering:references:plan:phase-0-rolling-wave-bare-and-gates/aimi-engineering:references:plan:phase-0-rolling-wave-select/aimi-engineering:references:plan:phase-0-scope-context-classification/aimi-engineering:references:plan:phase-0-scope-detection/aimi-engineering:references:plan:phase-1-5b-external-research/aimi-engineering:references:plan:phase-1-6-research-consolidation/aimi-engineering:references:plan:phase-1-7-research-ingestion/aimi-engineering:references:plan:phase-1-7b-prior-planning-gaps/aimi-engineering:references:plan:phase-1-7c-design-decisions/aimi-engineering:references:plan:phase-1-8-open-questions-and-scope-gates/aimi-engineering:references:plan:phase-1-9-architect-spawn/aimi-engineering:references:plan:phase-1-9-decision-and-recording/aimi-engineering:references:plan:phase-1-9-foundation-conditions/aimi-engineering:references:plan:phase-1-bundle-researcher/aimi-engineering:references:plan:phase-1-landing-check/aimi-engineering:references:plan:phase-1-local-research/aimi-engineering:references:plan:phase-2-4-codebase-cross-check/aimi-engineering:references:plan:phase-2-5-spec-flow-gap-gate/aimi-engineering:references:plan:phase-3a-3b-setup-and-outline/aimi-engineering:references:plan:phase-3c-outline-gate/aimi-engineering:references:plan:phase-3d-context-files/aimi-engineering:references:plan:phase-3d-expander-prompt/aimi-engineering:references:plan:phase-3d-prep-blocks/aimi-engineering:references:plan:phase-3d-prototype-blocks/aimi-engineering:references:plan:phase-3d-tree-guard/aimi-engineering:references:plan:phase-3d-validate-retry/aimi-engineering:references:plan:phase-3d5-audit-apply-gate/aimi-engineering:references:plan:phase-3d5-audit-spawn/aimi-engineering:references:plan:phase-3e-story-merge/aimi-engineering:references:plan:phase-4-checklist/aimi-engineering:references:plan:phase-4-metadata-context/aimi-engineering:references:plan:phase-4-metadata-identity/aimi-engineering:references:plan:phase-4-response-shape/aimi-engineering:references:plan:phase-4-schema-v33/aimi-engineering:references:plan:phase-45-validation/aimi-engineering:references:plan:step-0-environment-setup/aimi-engineering:references:plan:step-46-5-report/aimi-engineering:references:publish-confirmation/aimi-engineering:references:sanitization/aimi-engineering:references:scope-contexts/aimi-engineering:references:spec-section-contract/aimi-engineering:references:topic-slug/aimi-engineering:references:ui-signals/aimi-engineering:references:user-communication/aimi-engineering:references:verify-probe-policy/aimi-engineering:references:visual-variants/aimi-engineering:review/aimi-engineering:setup-models/aimi-engineering:status/aimi-engineering:validate-bugcontext7connects to: https://mcp.context7.com/mcp
${CLAUDE_PLUGIN_ROOT}/hooks/auto-approve-cli.sh
${CLAUDE_PLUGIN_ROOT}/hooks/pre-bash-dispatcher.py
${CLAUDE_PLUGIN_ROOT}/hooks/guard-runtime-state.py
${CLAUDE_PLUGIN_ROOT}/hooks/guard-tasks-presence.py
${CLAUDE_PLUGIN_ROOT}/hooks/context-size-hint.py
${CLAUDE_PLUGIN_ROOT}/hooks/inspect-session.py
The official monday.com plugin for Claude Cowork. Manage boards, items, docs, and forms across work management, CRM, dev, service, and campaigns. Full read and write access via OAuth.
5 skills · 1 MCP server
AI-supervised issue tracker for coding workflows
1 skill · 1 agent · hooks
Persistent project planning files with lifecycle hooks that inject selected plan context. Automatic recovery uses project files only. Explicit catchup modes may read same-project local session records to emit aggregate counts or bounded nonce-framed excerpts. Optional gated mode can request continuation on capable hosts and never runs commands declared in Markdown. No network upload path. Installs across 60+ agents.
6 skills · 13 commands · hooks
当用户希望将任务交给员工或协作者并跟进结果时，结合本地人员资料选择负责人，写清要求、协商工期、提供帮助并验收汇报；有飞书 CLI 时派单、读取回填和回复，缺少工具或权限时交付可转发文字。支持事件队列与可配置 Agent 接入，不承担招聘、绩效排名或惩罚。
1 skill
Ship faster with AI-powered development workflows. Automates code review, test generation, documentation, and task breakdown. Context-aware agents understand your codebase and enforce your team's standards.
12 skills · 6 commands · 7 agents · hooks
Persistent project management inside your AI coding tool. PAPI turns a plan into a cycle of scoped tasks, hands each one to your agent with a build spec, records what actually happened, and keeps every decision alive across sessions — so a new session resumes where the last one stopped instead of starting from nothing. Connects to the hosted PAPI server over OAuth; nothing runs locally.
14 skills · 1 MCP server
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.