القائمة
User-facing entry point to start sprint delivery. Verifies sprint preparation is complete, creates the sprint branch, then delegates to /sprint-deliver for autonomous execution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | sprint-kickoff |
| description | User-facing entry point to start sprint delivery. Verifies sprint preparation is complete, creates the sprint branch, then delegates to /sprint-deliver for autonomous execution. |
| user_invocable | true |
| arguments | none |
Provides the user-facing "kick off the sprint" command. Performs a quick readiness
check, creates the sprint branch, confirms with the user, then hands off to
/sprint-deliver for autonomous delivery of all use cases.
Read and follow ${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md.
docs/sprints/next-sprint/ exists.
/sprint-prepare to start a sprint."docs/sprints/next-sprint/readiness-report.md.
/sprint-prepare first."docs/sprints/:
sprint-1/, sprint-2/, etc.Present a brief summary to the user:
Ensure the working tree is clean:
git status --porcelain
If there are uncommitted changes, ask the user to commit or stash them before proceeding.
Verify local main is up-to-date with the remote:
git fetch origin main
git diff main..origin/main --stat
If there are differences, stop:
Local
mainis behindorigin/main. Sprint preparation artifacts may not be on this branch. Rungit pull origin mainfirst, or verify that/sprint-preparewas completed (Phase 9 commits and pushes all preparation artifacts tomain).
Create and checkout the sprint branch from main:
git checkout -b sprint-<N>
Push the branch to remote:
git push -u origin sprint-<N>
Confirm the branch was created:
Sprint branch
sprint-<N>created and pushed.All delivery work will happen on this branch. At sprint completion, a PR will be created to merge into
main.
Ask user for confirmation to proceed with delivery:
Ready to kick off Sprint N?
- Branch:
sprint-<N>(checked out)- Scope: [N use cases]
- Delivery order: [list UC IDs]
Proceed with delivery?
If confirmed, invoke /sprint-deliver.
/sprint-kickoff is the interactive entry point — it summarizes, creates the branch, and confirms.
/sprint-deliver is the autonomous engine — it executes the delivery pipeline.
Users can call either directly:
/sprint-kickoff — when starting a sprint (recommended)/sprint-deliver — when resuming or re-running without the branch creation / confirmation stepDiscovers 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.