ShiftLeft

Packaged slash command workflows for Cursor and Claude Code. Groom, refine, validate, and hand off tickets — before the first line of code is written.

ShiftLeft is a human-in-the-loop agent — it reasons over your tickets, surfaces gaps, and structures decisions, but never advances without a human sign-off. The agent does the analysis. The team owns the decisions.

The problem

Tickets enter sprints half-defined. Engineers hit ambiguity mid-build. Work pauses while the team re-aligns on things that could have been resolved before the first line of code.

How it works

Four slash commands, run in order:

| Command | Who runs it | What it produces | |---|---|---| | /groom PROJ-123 | EM | Clarification questions with risk levels — answered async | | /refine PROJ-123 | EM | A versioned, implementation-ready spec | | /validate PROJ-123 | Lead / QA | Key risks + shift-left test scenarios | | /handoff PROJ-123 | EM | Final engineering alignment doc |

Each stage writes a markdown artifact to ~/.shiftleft/<workspace>/. The artifact is the source of truth — not the chat.

Get started

Cursor:

npx @katpadi/shiftleft cursor

Claude Code:

npx @katpadi/shiftleft claude

Then restart your editor and type /groom PROJ-123.

What you get

• Blockers caught at /groom, not mid-sprint
• A spec that tracks its own version and change history
• QA-ready risk and test scenario probes before a ticket hits the board
• One clean handoff doc attached to the Jira ticket

Requirements

• Cursor or Claude Code

Providing ticket content:

• Paste the ticket text directly into chat — no integrations needed
• Or provide a Jira ID/URL — requires Atlassian MCP configured separately

See IMPLEMENTATION.md for artifact storage, slug resolution, CLI options, and editor rule details.
See DESIGN_DECISIONS.md for design decisions and common questions about how the devkit works.