mbensch

Manage JIRA tickets using the Atlassian MCP tools (preferred) or Atlassian CLI (acli) as fallback. Use when the user asks to view, edit, comment on, create, search, or transition JIRA tickets. Handles authentication, field discovery, custom fields (team, sprint), and output formatting.

CARS project-specific configuration for the carscommerce.atlassian.net org. Activated automatically by /jira-create when the user is working in the CARS project. Provides work hierarchy, issue type names, team field setup, and UUID resolution instructions specific to carscommerce.

Create a well-structured Jira Bug with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Create a well-structured Jira Epic with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Create a well-structured Jira Initiative with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions and MCP-based ticket creation.

Create a well-structured Jira Objective with S.M.A.R.T criteria, key results, and milestones. Invoked internally by the /jira-create command. Objectives are the highest level of the work hierarchy, sitting above Initiatives, Epics, and Stories.

Create a well-structured Jira Story with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Remove signs of AI-generated writing from text to make it sound more natural and human-written. Invoked internally by the /jira-create command to improve tone and clarity of Jira ticket content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

Records architectural and implementation decisions. Use when a significant technical decision is made, a spec is modified, or an approach changes during implementation. Creates numbered decision records in .factory/decisions/.

Generates structured requirements using EARS (Easy Approach to Requirements Syntax) notation. Use when the user is planning a feature, entering spec mode, or asking for requirements. Produces user stories with testable acceptance criteria.

Technology stack constraints and approved libraries. Auto-loaded when Droid is making technology choices, adding dependencies, or proposing architectural changes. Defines what frameworks, libraries, and patterns are allowed.

Guardrails for debugging and troubleshooting. Auto-loaded when Droid encounters errors, test failures, or build issues. Prevents context drift and tech stack swaps during error recovery.

Bootstrap any software project from idea to autonomous multi-agent development. Guides you through PRD creation, technical discovery, implementation planning, dev environment setup, and infrastructure scaffolding. All state is tracked in beads. Re-invoke at any time to resume. Use when starting a new project from scratch.