Development Workflows
From ticket to tested PR.
Three structured workflows that discover, analyze, implement, test, and deliver — with every decision traced and every phase verified. Pick one directly, or let the Smart Classifier choose for you.
$ /sdet "Login button returns 500" --pr
No active workflows. Classifying...
Classification: bug-fix (confidence: high)
Reason: "returns 500" + "error" signals
Executing /bug-fix "Login button returns 500" --pr
INTAKE ............ done
REPRODUCE ......... done
RECALL ............ done
CODE_TRACE ........ done
DIAGNOSIS ......... done
FIX ............... runningThe difference in numbers
A typical 3-story-point bug: investigate, fix, test, PR. Here's what changes.
Fix cycle
dev + test + PR
Phases executed
enforced, never skipped
Test creation
unit + E2E written by agent
PR with summary
commit, push, PR via --pr
| Activity | Without framework | With framework |
|---|---|---|
| Root cause analysis | Ad-hoc grep + guesswork, ~4–8 hrs | 6 structured discovery phases, ~10 min |
| Test creation | Dev writes tests manually, ~2–4 hrs, often skipped | TEST_GEN auto-writes unit + E2E tests (Category A), 0 manual effort |
| Regression testing | "I ran the tests locally" — maybe | BASELINE → VERIFY → BLAST_RADIUS — always, both layers |
| Impact assessment | Reviewer catches surprises in PR, after the fact | BLAST_RADIUS_MAP runs before any code changes |
| Traceability | Jira comment: "fixed", 0 evidence trail | 16 linked documents from intake to close |
| Knowledge retention | Stays in dev's head, lost on context switch | LEARN phase writes to KNOWLEDGE_BASE.md |
| PR creation | Write commit msg + PR description, ~30 min | CLOSE phase auto-commits + raises PR, 0 min |
Three workflows. One command each.
Each workflow is a complete state machine — from ticket to tested PR. Pick the one that matches your task, or let the Smart Classifier choose for you.
Bug-Fix
~16 phases
Something is broken. Reproduce it, trace the root cause, fix it with red-green testing, verify with blast-radius regression.
/bug-fix PROJ-123 "Login 500 error"Enhance
~17 phases
Change working behavior. Map the existing feature, design the change, implement with feature-flag gating where needed.
/feature-enhance PROJ-456 "Add dark mode"Feature
~20+ phases
Build something new. Architecture-first design, sliced delivery, per-slice testing, integration verification, all behind feature flags.
/feature-build PROJ-789 "Implement SSO"Comparison
| Aspect | Bug-Fix | Enhance | Feature |
|---|---|---|---|
| When to use | Something is broken | Change working behavior | Build something new |
| Starting state | Known broken behavior | Known working behavior | Nothing exists |
| Discovery goal | Find what’s wrong | Map what exists to change | Map surroundings + deps |
| Ticket gate | 6 required checks | 6 required checks | 8 required + 5 recommended + linked story maturity |
| Figma phase | No | Yes | Yes |
| API survey | No | No | Yes |
| Dependency gate | No | No | Yes |
| Per-slice looping | No | No | Yes |
| Integration phase | No | No | Yes |
| Analysis phase | DIAGNOSIS | DESIGN | ARCHITECTURE |
| Plan phase | FIX_PLAN | ENHANCE_PLAN | SLICE_PLAN |
| Implement phase | FIX | IMPLEMENT | IMPLEMENT (per-slice) |
| Phase count | ~16 | ~17 | ~20+ |
| --pr auto-PR | Yes | Yes | Yes |
| Terminal signal | BUG_FIXED | ENHANCEMENT_SHIPPED | FEATURE_SHIPPED |
Pipeline Overview
From zero to PR in four steps
Copy the framework
Drop the .claude folder into your repo root. It contains the generator command and all workflow templates.
cp -r .claude /path/to/your-repo/.claudeGenerate workflows
The generator scans your repo — language, test runner, build tools, Jira, feature flags — and produces tailored workflow files.
/generate-development-workflowsRun a workflow
Describe your task with /sdet and it auto-classifies. Or pick /bug-fix, /feature-enhance, or /feature-build directly.
/sdet "Login button returns 500"Ship a PR
The CLOSE phase posts results to Jira, creates a QE Review sub-task, and with --pr auto-commits and raises a pull request.
/bug-fix PROJ-123 "Fix login error" --prCommand Reference
All development workflows support these flags. Combine them with any invocation format.
| Flag | Purpose | Prerequisite |
|---|---|---|
| --pr | Auto-commit and raise a pull request at CLOSE phase | None — can be added at any time |
| --jira-check | Run INTAKE + TICKET_GATE only — print readiness report, then stop | Jira ticket ID required |
| --qe-review | Run TEST_INVENTORY only — audit test coverage without starting full workflow | Existing state through REQUIREMENTS (discovery done) |
| --dev-verify | Execute the full QE verification gauntlet: BASELINE → TEST_GEN → VERIFY → BLAST_RADIUS_RUN → CLOSE → LEARN | Existing state through FIX/IMPLEMENT (code changes exist) |
| --pr-only | Create commit + PR from a completed workflow (runs only the CLOSE auto-PR step) | CLOSE_REPORT.md must exist (workflow reached CLOSE) |
Usage Examples
# Audit test coverage after discovery is complete
/bug-fix --qe-review
/feature-enhance --qe-review
# Re-run the full QE verification after implementation
/bug-fix --dev-verify
/feature-build --dev-verify
# Combine with --pr to auto-ship after verification passes
/feature-enhance --dev-verify --pr
# Create a PR from a completed workflow (no --pr needed upfront)
/bug-fix --pr-only
/feature-build --pr-only
# Via the smart classifier
/sdet PROJ-123 --qe-review
/sdet PROJ-123 --dev-verify
/sdet PROJ-123 --pr-only