Clarify ambiguous issue requirements via Socratic questioning for Linear or Jira specs.
npx skills add https://github.com/MediTracer/mobius --skill define-meditracer
Please help me install this Agent Skill. Skill: define Source: https://github.com/MediTracer/mobius/tree/main/.opencode/skills/define Command: npx skills add https://github.com/MediTracer/mobius --skill define-meditracer
Clear, unambiguous issue specs are essential for reliable execution. This skill guides users through Socratic questioning to eliminate ambiguity, ensuring Linear or Jira issues have well-defined acceptance criteria and relationships.
Start by describing the issue you want to create, then let the Socratic process guide you to a well-defined spec.
High-intent search queries and answers about installing and using this skill.
Clarify ambiguous Linear or Jira issue requirements through automated Socratic questioning that surfaces edge cases and dependencies to produce precise, verifiable issue specs. The process guides you interactively to eliminate unclear acceptance criteria before ticket creation.
Socratic questioning for issue definition is a guided process that uncovers missing acceptance criteria and relationships by systematically challenging ambiguous requirements. It transforms vague requests into structured Linear or Jira issue specs ready for CLI creation.
Yes, you can use local mode to write issue specs to the project-local .mobius directory for offline or staged creation. This generates structured issue context including titles, descriptions, and relationships without requiring immediate backend tracker connectivity.
Generate acceptance criteria and dependencies for Jira or Linear issues by describing your initial issue concept and letting the Socratic process identify edge cases. The workflow outputs verifiable, well-scoped specs with defined relationships ready for approval.
Yes, the define skill supports both Linear and Jira backend workflows for issue spec generation. It operates across both trackers and the local workflow, generating acceptance criteria, relationships, and optional local-mode artifacts as needed.
The best way to turn vague feature requests into ready-to-approve Linear issues is through Socratic questioning that systematically eliminates ambiguity. This produces structured issue context with titles, descriptions, labels, and verifiable acceptance criteria for CLI creation.
HellKaiser45Convert raw notes and error logs into structured GitHub Markdown issues.
MediTracerCreate pull requests from feature branches using conventional commit format.
tomzxRead a GitHub issue and apply relevant existing labels.
ZaxbyHubParse GitHub issue URLs into resolution specs with root cause hypotheses.
