Discovers and invokes Nexa skills. Use when starting a session or to identify which skill is appropriate for the task at hand. This is the orchestrator skill which governs how all Nexa skills are discovered and invoked.
Orchestrates the full bugfix pipeline for a BUG-XXX or GitHub issue: an isolated tester reproduces the bug and updates the issue, a senior-dev agent writes a root-cause fix plan while a business-analyst agent links the affected requirement(s) in parallel, then the fix is implemented and gated on Definition of Done. Use when the user asks to "fix this bug", "resolve BUG-XXX", "run the bugfix pipeline", pastes a GitHub issue link and asks to fix it, or mentions an end-to-end bug resolution workflow.
Creates structured change request documents for intentional modifications to already-implemented use cases. Use when the user asks to "create a change request", "log a CR", "document a change", or describes a stakeholder-requested modification to existing behavior (e.g., renaming a field, changing validation rules, restructuring data). A change request always references exactly one use case and describes only the delta — the original use case remains immutable.
Creates structured bug report documents with reproduction steps, expected vs actual behavior, and severity classification. Use when the user asks to "report a bug", "file a bug", "document a defect", "log an issue", or mentions a bug, defect, regression, or unexpected behavior that needs to be tracked.
Runs a comprehensive implementation audit for a delivered use case. Checks Definition of Done, i18n completeness and correctness, error message i18n, accessibility, visual fidelity against the design, and loading/error states. Run after /deliver-use-case or before /sprint-complete for a quality deep-dive. Results are advisory — Critical and Major findings should be fixed; Minor findings are observations.
Lead Requirements Engineer that systematically elaborates all use cases through structured analysis, probing questions, and iterative refinement. Processes use cases in thematic clusters, applies CRUD matrix analysis, actor-goal completeness, exception path probing, MoSCoW prioritization, and traceability checks. Spawns a Product Owner sub-agent to answer clarification questions — only genuinely ambiguous decisions reach the human. Updates requirements, entity model, and use case diagram as living documents. Use when the user asks to "engineer requirements", "elaborate use cases", "analyze use cases", "validate use case completeness", "deep-dive on requirements", "prioritize requirements", or mentions requirements engineering, use case elaboration, MoSCoW, or completeness analysis.
Selects a subset of use cases for a sprint, refines requirements, evolves the entity model and use case diagram, generates specs and designs, and produces a sprint readiness report. Treats requirements, entity model, and use case diagram as living documents that evolve per sprint while protecting delivered use cases as immutable. Use when the user asks to "prepare a sprint", "scope a sprint", "refine for sprint", "get use cases ready for delivery", "sprint planning", or mentions sprint preparation, sprint scoping, or delivery readiness.
Completes the current sprint by validating all use cases are delivered, running an E2E regression gate, closing GitHub issues, generating a sprint summary, updating the sprints overview dashboard, archiving the sprint folder, and creating a pull request from the sprint branch to main. The PR body contains the sprint report. Use when the user asks to "complete the sprint", "close the sprint", "finish the sprint", "wrap up the sprint", or mentions sprint completion, sprint close, or sprint demo preparation.