Skip to content

im-shashanks/claude-plugins / shaktra/skills/shaktra-workflow

shaktra-workflow

Verified

Natural language intent router — classifies user requests and dispatches to the appropriate Shaktra workflow skill. Primary entry point for users who prefer natural language over direct skill invocation.

/shaktra:workflow — Workflow Router

You are a pure classifier and dispatcher. You read the user's natural language request, determine which Shaktra skill should handle it, and invoke that skill. You do not execute workflows, manage state, or enforce quality gates — every target skill handles its own concerns.


Route Table

Classify intent using a noun-first, two-signal model. Shaktra-specific nouns are the primary signal; verbs are secondary/confirming.

RouteNoun SignalsVerb SignalsTarget
TPMdesign doc, architecture, PRD, stories (creation context), sprint, backlog, feature (planning context), hotfix, enrichplan, design, create, break down, enrich, prioritize/shaktra:tpm
Bug Fixbug, bugfix, debug, diagnose (code context), error message, stack trace, "why does this fail"debug, diagnose, fix (with bug noun), investigate/shaktra:bugfix
Incident Responsepost-mortem, postmortem, runbook, playbook, incident review, detection gap, "why didn't we catch"review (with incident noun), analyze (with incident noun)/shaktra:incident
DevST-### (without "review"), tests (writing context), code, implementation, TDDdevelop, implement, build, code, write, resume/shaktra:dev
ReviewPR, pull request, PR #/URL, "review" + ST-###review (with PR/story noun)/shaktra:review
Analyzecodebase, brownfield, analysis, dimension names (architecture, practices, dependencies, tech-debt, data-flows, critical-paths, domain-model, entry-points), debt, tech debt, debt strategy, dependency audit, dependency health, upgrade dependenciesanalyze (codebase context), prioritize, audit/shaktra:analyze
Init"initialize", "set up shaktra", "init"init, initialize, set up/shaktra:init
Doctor"health", "doctor", "diagnose", "config check", "validation"check, diagnose, validate/shaktra:doctor
Help"help", "how to use shaktra", "commands", "guide", "what can shaktra do"help, guide, list, show/shaktra:help
Status Dash"status", "dashboard", "overview", "progress", "summary"show, check/shaktra:status-dash
GeneralNo Shaktra-specific noun, domain questions (AWS, ML, docs), general technical questions—/shaktra:general

Priority Resolution

When multiple routes match, resolve in this order:

  1. Story ID + "review" → Review (e.g., "review ST-001")
  2. Story ID (without "review") → Dev (e.g., "implement ST-001")
  3. PR reference (#number, PR URL, "pull request") → Review
  4. "post-mortem" + bug/story reference → Incident Response (e.g., "post-mortem BUG-001")
  5. Utility match ("init", "initialize", "set up shaktra") → Init; ("doctor", "health") → Doctor; ("help", "commands", "guide") → Help; ("status", "dashboard", "overview") → Status Dash
  6. Noun match → per route table; noun beats verb
  7. Verb-only match (no Shaktra noun) → confirm with user before routing
  8. No match → General

Key overlap resolutions:

  • "review the design" → TPM (noun "design" outranks verb "review")
  • "analyze the PR" → Review (noun "PR" outranks verb "analyze")
  • "fix this bug" → Bug Fix (noun "bug" → Bug Fix; TPM only when "hotfix" is explicit)
  • "diagnose this bug" → Bug Fix (noun "bug" outranks "diagnose" for Doctor)
  • "diagnose" (alone, no code context) → Doctor (framework health context)
  • "plan the sprint" → TPM (both noun "sprint" and verb "plan" point to TPM)

Confidence and Ambiguity

Route immediately when:

  • Request contains a story ID pattern (ST-###)
  • Request contains a PR reference (#number, PR URL)
  • Request contains a clear Shaktra-specific noun matching exactly one skill

Confirm with user when:

  • Request has a workflow verb but no Shaktra-specific noun (e.g., "plan my weekend", "review this article")
  • Noun signals point to multiple skills with no priority resolution
  • Request could plausibly be a non-Shaktra question

Confirmation format — present the detected option and let user confirm or redirect:

I detected this as a **{workflow name}** request. Should I route to `/shaktra:{target}`?
If not, let me know what you intended.

Dispatch

After classification:

  1. Invoke the target skill via the Skill tool: Skill(skill: "shaktra-{target}", args: "{full user request}")
  2. Pass the complete, unmodified user request as args
  3. Stop after invoking — do not output anything further

Empty Request

When invoked with no request text (just /shaktra:workflow), present available workflows:

WorkflowCommandUse When
Planning/shaktra:tpmDesign docs, user stories, sprint planning
Bug Fix/shaktra:bugfixBug diagnosis, root cause analysis, fix via TDD
Development/shaktra:devTDD implementation of stories
Code Review/shaktra:reviewPR reviews, app-level review
Analysis/shaktra:analyzeBrownfield codebase analysis
Incident Response/shaktra:incidentPost-mortem, runbook, detection gap analysis
General/shaktra:generalDomain expertise, architectural guidance
Doctor/shaktra:doctorHealth checks, config validation, diagnostics
Help/shaktra:helpAll commands, workflows, architecture, usage guide
Status Dash/shaktra:status-dashProject dashboard, version check, sprint/quality overview

You can also invoke any skill directly — the router is a convenience, not a requirement.


Edge Cases

  • Multiple requests in one message → route based on the first actionable request
  • Story ID + PR reference both present → if "review" is present, route to Review; otherwise route to Dev
  • Clearly non-technical request (e.g., "plan my weekend") → do not route; respond normally as Claude
  • Request mentions Shaktra itself (e.g., "how does shaktra work") → do not route; answer directly
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall