Smart Classifier

Describe your task, provide a Jira ticket, or both. /sdet detects active workflows, classifies your input, and delegates to the right workflow.

bash

/sdet "Login button returns 500"       # text classification
/sdet PROJ-123                         # Jira classification (when enabled)
/sdet PROJ-123 "extra context" --pr    # both, with auto-PR
/sdet PROJ-123 --jira-check            # validate ticket readiness without starting a workflow
/sdet PROJ-123 --qe-review             # audit test coverage (requires discovery done)
/sdet PROJ-123 --qe-run                # run full QE verification gauntlet (requires code changes)
/sdet PROJ-123 --pr-only               # create commit + PR from a completed workflow

Flow Diagram

Active Workflow Detection

Before classifying, /sdet checks all three state files to find active workflows.

Scenario	Behavior
1 active + no new input	Auto-resume the active workflow
1 active + new description/ticket	Ask: treat as guidance for active workflow, or start new?
0 active	Proceed to classification
Multiple active	Show all, ask which to resume or whether to start new

Classification Signals

/sdet uses two classification paths. Jira path analyzes issue type, labels, and description fields. Text path analyzes keyword signals in the description. Both produce the same confidence levels.

Routes to	Jira Signals	Text Signals
/bug-fix	Bug/Defect type, repro steps, "bug" label	"broken", "error", "crash", "not working", "failing", "regression"
/feature-enhance	Improvement/Enhancement/Task type, "improve" label	"change", "modify", "update", "improve", "optimize", "refactor"
/feature-build	Story/Epic/Feature type, user stories, "feature" label	"new", "build", "create", "implement", "add new", "introduce"

Confidence Levels

Level	Jira Path	Text Path	Behavior
High	Issue type directly maps	3+ keywords from one category	Auto-recommend
Medium	2+ signals point to one	2+ keywords point to one	Recommend with reasoning
Low	Signals split across workflows	Keywords split across categories	Present top 2, ask user

Unified Companion Commands

These companions auto-detect the active workflow so you don't need to remember which prefix to use.

Command	Purpose
/sdet-status	Show active workflow status, phase, blockers, and documents
/sdet-guide	Inject guidance into the active workflow's HUMAN_GUIDANCE.md
/sdet-retry	Re-run a specific phase in the active workflow
/sdet-unblock	Resolve a blocker and continue the active workflow

Key Processes

Active Workflow Detection

Checks BUG_FIX_STATE.md, ENHANCE_STATE.md, and FEATURE_STATE.md for active phases before classifying.

Dual Classification

Jira path uses issue type + labels + description fields. Text path uses keyword matching. Both produce the same confidence-based UX.

Setup Gate

Before delegating, ensures workflow directories, knowledge stores (KNOWLEDGE_BASE.md, CODEBASE_INSIGHTS.md, TOOL_RETRO.md), and HUMAN_GUIDANCE.md exist. Idempotent.

--pr Passthrough

Add --pr to /sdet and it passes through to the delegated workflow. The CLOSE phase will auto-commit and raise a pull request.

--jira-check

Add --jira-check to validate a ticket's readiness without starting a workflow. Works on any entry point: /sdet, /bug-fix, /feature-enhance, or /feature-build. Runs the workflow-specific TICKET_GATE checklist, reports a readiness summary, drafts concrete suggested updates for each gap, and offers to write them back to the Jira ticket.

--qe-review

Add --qe-review to audit test coverage without running the full workflow. Runs TEST_INVENTORY only and prints a coverage report. Requires an existing workflow state through REQUIREMENTS (discovery phases must be complete).

--qe-run

Add --qe-run to execute the full QE verification gauntlet: BASELINE → TEST_GEN → VERIFY → BLAST_RADIUS_RUN → CLOSE → LEARN. For feature-build, includes per-slice verification and integration. Requires code changes to exist (FIX.md or IMPLEMENT.md).

--pr-only

Add --pr-only to create a commit and PR from a completed workflow. Runs only the CLOSE phase's auto-PR step (selective git staging, safety check, commit, gh pr create). Requires CLOSE_REPORT.md to exist (workflow must have reached CLOSE).